I don’t understand why people are obsessed about percentages for a modern washing machine.
Modern washing machines are adjusting their end time during the program run, as they take care about the weight of the load, the water turbidity (assuming how dirty the clothes are), how much water they absorb, etc. My machine just changed the end time and now it is 50 minutes shorter than how it suggested in the beginning. That percentage calculation is just prone to error.
(And I did not mention if you choose to change the number of spin cycles on the machine, meanwhile the program is running, as some models support that option. Or you pause the program to add more stuff in, if you have a machine with an AddWash door.)
What an annoying and over-complicated set-up just to get some Samsung dryer visibility in HA
What are people doing with the bearer-token? Seems it needs re-generating every 24 hrs which takes away some of the “automation” factor.
How about smarthings-cli? it seems to maintain a login and doesn’t ask for bearer tokens. I guess the same setup could be achieved with command-line sensor instead of rest sensor? Would there be any limitations with that?
any idea for where to look up the dryerCycle (or washerCycle) codes?
I worked out that “course_1F” is the same as “Mixed Load” but want to be able to display as the dryer or the smart things app display the cycle. Must be looked up somehow.
Just fyi - Home Assistant developers are in touch with SmartThings and actively working on a new integration (currently planned to launch in the Home Assistant 2025.3 branch). That should hopefully resolve the 24-hour token issue (it won’t use the PATs at all, and will substitute an oAuth integration for them).
Great, I bet this “active work” will break all the workarounds…
I knocked up a rest proxy to the smartthings-cli to bypass the hassle of having to renew app keys.
Does anyone know the endpoint to get proper energy consumption data?
the powerConsumptioReport is almost useless…
Sorry I can’t help with your powerconsumption question, I only own a Samsung SmartThings oven – it’s literally the only device I have attached to SmartThings; I don’t intend to buy anything else that’s exclusively tied to SmartThings (or any proprietary cloud device in general, if at all possible).
These changes only impact newly issued PATs. As of now we’re not making any changes to existing PATs. We know that of the 40k or so PATs in active use, a number of those are being used for critical integrations for users’ locations such as the 20k or so being used for HomeAssistant. We don’t want to break that functionality and before we would consider making any changes to existing PATs, we’d want to have a paved path to keep our users’ locations functioning reliably.
For now, I’m keeping my long lived PATs ( I have a couple) safely stored in a password manager so I can use them for similar purposes as you - I have a few Home Assistant REST commands to control my oven, since that isn’t yet offered by the native HA integration. I’m hopeful it may be added in the future and have provided my device configs and commands to the developer working on the integration.