Add, saved, published - didn’t fix it
Then swapped a device back to dimmer then back to your handler just in case and that didn’t fix it either.
Interestingly…the devices perform the actions I set when they were dimmer devices In the scene. So even after I made the. The wd200 device and it says “unknown action” - when I run the scene the light turn on and dim to the level I set.
So at least I have a workaround…but more than happy to debug this if it helps fix a bug in the handler…
I just created a virtual device using that handler and it’s working as expected with Scenes and Automations using the Android app.
When I first tried to create a new Automations in the iOS app only 1 of my devices was listed and I saw the same “unknown action” message in the Automation I created earlier using the dimmer.
That phone has been powered off for a while so I left it open on the dashboard screen for a little while and when I checked Automations it showed most of my devices. I then left it on the dashboard screen a little longer and I was able to see all my devices in Automations and that “unknown action” message was gone.
Long story short, this is most likely a caching issue for custom handlers and leaving the mobile app open on the dashboard screen might solve it.
It couldn’t hurt to toggle the dimmer from the dashboard screen while waiting.
Yea - I just went back into the iOS app and it’s now working when it wasn’t before. Strange behavior but it works once I waited a while
Thanks for your help!
Open Live logging, remove // from the log.trace line at the bottom of the code, execute the automation that turns the light on or off and if the light changed, but the status in ST didn’t then post the live logging results.
Any idea what is going to happen to this device when things switch to edge?
Apparently Homeseer is working on it. See the answer on Homeseer forum.
Hopefuly they release it in time for the edge big bang!
4 more days left in the year and still no response…