-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"default state" setting #3
Comments
could this be a choice in the device setting if the status should be kept as it is after power-up or that is should be turned OFF always? Some devices should not always be turned OFF after power-down (fridges, pumps). |
Not sure if I understand what you mean. By default, the Sonoff devices will be turned off after they powered up (at least the devices that I have). I'm proposing a device setting that would allow turning the device on automatically after it has powered up and has connected with Homey. Or do you mean that Homey should remember the state for each device ("off" or "on") and restore that state when a device is powered up? |
I think that we're talking about the same thing 😁 However, firmware 1.6.0 is going to be an issue: you won't be able to use my app with devices running the original 1.6.0 firmware (in that firmware ITEAD, the manufacturer of the Sonoff devices, has disabled the ability to pair with a different "cloud server", like Homey). There's not workaround yet, and it's unclear if there will ever be a workaround, as this will require support from the manufacturer. However, at the moment I'm working on supporting an alternative firmware for Sonoff devices, Sonoff-Tasmota. It won't be trivial to set up, as it requires opening up the device and flashing a new firmware, but at least it's an alternative to get the devices working with Homey again. |
When a device registers itself with Homey after powering up, Homey could make sure the device is switch on (because the device default is to be switched off after power up).
The text was updated successfully, but these errors were encountered: