16
Users / Re: Adding zwave lights
« on: October 23, 2018, 02:41:39 pm »
That's it!
I have the same, the lights are controlled by the parent ZWave device here.
Here is a paste of one of my lights in Wizard > Devices > Lights
(some dimmer)
Device #: 170
Device Template #: 38
Controlled by: ZWave
In the LMCE web admin and the top menu Automation > Advanced ZWave will show more info.
Sometimes in the past I have had to delete all those devices you pasted after messing around to force re-reading, then remove the usb stick and rebooted. you will have to add everything again but if things go crazy that is a sure fire way to start over after resetting all the devices but only do that as a last resort. Things work for me here now so I haven't done that for a while, sometimes it takes some time for Zwave settings to stick I think I just had to keep trying until I got it working.
Edit: if you want lots of info you can also do this
tail -f /var/log/pluto/${your_parent_ZWave_device_number}_ZWave.log
Or connect to the screen session that is running for the device; screen -ls
that can be of great help in finding problems.
I have the same, the lights are controlled by the parent ZWave device here.
Here is a paste of one of my lights in Wizard > Devices > Lights
(some dimmer)
Device #: 170
Device Template #: 38
Controlled by: ZWave
In the LMCE web admin and the top menu Automation > Advanced ZWave will show more info.
Sometimes in the past I have had to delete all those devices you pasted after messing around to force re-reading, then remove the usb stick and rebooted. you will have to add everything again but if things go crazy that is a sure fire way to start over after resetting all the devices but only do that as a last resort. Things work for me here now so I haven't done that for a while, sometimes it takes some time for Zwave settings to stick I think I just had to keep trying until I got it working.
Edit: if you want lots of info you can also do this
tail -f /var/log/pluto/${your_parent_ZWave_device_number}_ZWave.log
Or connect to the screen session that is running for the device; screen -ls
that can be of great help in finding problems.