forum

PZ1's solution seem neat and simple enough, although I don't quite understand the config ;). If that does not work for you an alternative is to create a virtual switch (Dummy Device) that is set to "ON" when it's 22.00 (on Schedule). Then in your logical rule, you also incorporate a check ...

I have a couple of Qubino flush 2 (ZMNHBD1) relays and can't understand how the switch status reporting is supposed to work. Pressing the button in the GUI shows in the log (greping only for commandClasses.37.data.level): Both - off [2016-03-08 20:56:23.557] [D] [zway] SETDATA devices.10.instances.0...

yepp, that's it. You probably haven't got the file, so just create it.

A search for Webif in the forums gives you the answer in the second hit

I've gone through all (?) "storage" files now and looks like I'm missing a last piece and one config reference that I haven't been able to find. I've changed all references in: automation/storage/configjson-06b2d3b23dce96e1619d2b53d6c947ec.json automation/storage/notifications-f37bd2f66651...

Really? That doesn't sound to good if the ZAutomation is the only alternative then?

Noooo, that's cheating - he wanted to use the ZAutomation API

Me too, although id seems like it takes approx one-two days longer for it to appear for the first time after a restart of the z-way server.

I had to re-include a device, and now it of course got a new id. Since I have some rules etc, I'd like it to be named as before the re-inclusion. So from the new "Routing Multilevel Sensor_16" I'd like it to go back to the old "Routing Multilevel Sensor_4". This of course goes fo...

Try to create the file, as PoltoS suggested then, e.g.: