A couple things to try. Make sure that the switch has your z-wave hub node id in association group 1. Also, you might want to try to do a network heal.
Also - general heads up. If you are using the alpha/beta zwave-mqtt integration which is destined to become the new HA support for zwave at some point there was an error in the 1.6 config files for the LZW-30SN where it was trying to use old static scene labels for things. I diagnosed/reported the error and it is fixed in the config as of today. The correct scene labels are now the standard “Scene 1” etc rather than the “Top Button Pressed” ones. There was also an issue where using this switch with the bad config file could cause cache corruption in the open zwave daemon that has also been addressed. If you are on the standard zwave integration this should not have impacted you as you are still using the old OZW 1.4 configurations.
I already have z wave USB stick as my lifeline association. I will try heal network.
This might be the reason. I recently moved to zwave2mqtt docker container and I guess it is using this old 1.6 zwave config which will have the bug. I will try using the latest config files and see if it resolves the issue.
The fix is just to delete the section on Command Class 91 that you will see at the end of the old 1.6 LZW-30SN.xml file in the config directory (in case the new version isn’t easy to pull). Also, keep an eye on the new zwave_mqtt integration as that will eventually be the “official” one and looks like it should be pretty good. (It is currently available as a custom component via HACS).
i verified few things
- Inovelli switch does have a lifeline association and its associated with the zwave stick.
- Did heal network. No effect.
I spent sometime on @kevink suggestion. But i see this behavior both in lzw30 and lzw30-sn switches. So i felt its not related. but i still went ahead and updated my zwave config and removed Command Class 91. Still its not helping.
Have you played around with config parameter 4 (Association Behavior)? I haven’t really tested all the values, but it sounds like it might be able to cause the symptoms you are describing.
Parameter 4: When should the switch send commands to associated devices?
| Value | Meaning |
|---|---|
| 01 | local |
| 02 | 3way |
| 03 | 3way & local |
| 04 | z-wave hub |
| 05 | z-wave hub & local |
| 06 | z-wave hub & 3-way |
| 07 | z-wave hub & local & 3way |
| 08 | timer |
| 09 | timer & local |
| 10 | timer & 3-way |
| 11 | timer & 3-way &; local |
| 12 | timer & z-wave hub |
| 13 | timer & z-wave hub & local |
| 14 | timer & z-wave hub & 3-way |
| 15 | all |
Default = 15
Also, after you edited your LZW-30SN.xml file, did you run the “refresh node info” and click the button to refresh the config values in Zwave2MQTT?
I tried to change the Association Behavior to 04 and it still did not work. So i decided to do a factory reset of one of the lwz-30 switch. After reset, i added the device back to my zwave2mqtt and to my surprise it started working. I am now seeing the below update in the zwave logs and the status get notified to the controller. I also see the updated status in zwave2mqtt UI.
zwave2mqtt | 2020-03-15 00:14:27.541 Detail, Node008, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x08, 0x03, 0x25, 0x03, 0x00, 0xdf
zwave2mqtt | 2020-03-15 00:14:27.541 Detail,
zwave2mqtt | 2020-03-15 00:14:27.541 Info, Node008, Received SwitchBinary report from node 8: level=Off
zwave2mqtt | 2020-03-15 00:14:27.541 Detail, Node008, Refreshed Value: old value=true, new value=false, type=bool
zwave2mqtt | 2020-03-15 00:14:27.542 Detail, Node008, Changes to this value are not verified
zwave2mqtt | 2020-03-15 00:14:27.542 Detail, Node008, Notification: ValueChanged CC: COMMAND_CLASS_SWITCH_BINARY Instance: 1 Index: 0
zwave2mqtt | 2020-03-15T00:14:27.543Z z2m:Zwave zwave node 8: changed: 37-1-0:Switch:true -> false
I was happy and tried doing it on other devices. I have a total of 5 inovelli switches. It worked for 1 more and for rest of the 3 devices no matter how many times i try to do a factory reset and add it back, it does not send updates to controller.
Do you think it will be a hardware problem? Any other suggestions?
Thanks for all the help till now.
Thanks,
Palanivelrajan B
If you havent set up many automations yet, you could always try a factory reset on your z-stick. When I first switched from OZW 1.4 to 1.6, I would occasionally run into issues where my z-stick would crash (lights would stop blinking on the stick and it wouldnt respond to any zwave commands for a few minutes). I excluded all devices, reset the z-stick and then re-included, and havent had any issues since.
Of course, if you have a bunch of devices and automations already set up, that might end up being a lot of work to recreate.
I also recommend checking your LZW-30.xml file, to make sure openzwave didnt rename it or revert it back. OZW 1.6 has the ability to automatically download config file updates, so if you modified your files, it be getting reverted back every time you refresh node info or re-include a device.
i was very desperate so i did a hard reset of my zwave stick also , still not working. 
. For the devices that is not working, i did multiple factory resets. Still no luck.
Let me go ahead and disable auto update of zwave config files and give it a shot. Config files for lzw-30 did not change recently right? its only lzw-30-sn that had some changes is understanding.
Hi there, I don’t believe it is a bug in the firmware. It is something that has been working well for a lot of people. I’m really not sure where to go next. Association group 1 (lifeline) is the only requirement for the status report to be sent to the controller when changed at the wall. When association group 1 is set correctly, the switch will send a SwitchBasicReport to the controller to notify it.
The only other thing I can think of is if the devices are on the range of the z-wave network maybe the signal is not making it. Kind of unlikely for multiple switches though.
You may want to try to include the devices in ‘non-secure’ mode. There is less network traffic and less of a load on your controller when you do this.
Man, don’t give up on me. I add these devices in non-secure mode. So that’s most likely not a problem.
If I try to turn on the device from zwave2mqtt it turns the light on and off. No problem. So that atleast proves that it’s within range and it honors the signal from the controller. When I toggle the switch in the wall , that’s when the updates does not come to the controller. But the actual light toggles.
Anything else u want me to try ?
By the way - when you fixed the xml file did you also explicitly delete the ozw cache file? That file persists across restarts of ozw and can cause issues if it is corrupted. If you haven’t done so, I suggest shutting down the ozwdaemon, specifically deleting the cache file (name something like ozwcache???.xml and found where ever you have ozw config files - i.e. the one you fixed), then restarting the ozwdaemon. Just another thought.
When you turn on the device from zwave2mqtt, does your OZW_Log.txt file show that the device is responding?
Also, did you change the Protection config parameter from within Zwave2mqtt for any reason?
I did a full hard reset of my zwave controller and started adding the switches again. I have 3 switches in the living room and all of them are working. They are reporting status properly .
I have 2 in my bedroom. They work sometimes and sometimes does not work.
1 things changed since I did a reset. I had some dead nodes in my network. That all are gone now. Check my network pic.
If u see, the bedroom light is not connected to the controller directly. Do u think that has something to do ?
When I did a full reset, I also took the latest version of zwave2mqtt. This is now using openzwave version 1.6.1061. This has the latest xml file of innoveli switches. So I am now confident that I have the right configuration.
I am not giving up. 
The fact that 3 out of the 5 switches are working, i decided to start all over again. This time i took my controller close to the 2 non working switches and added them first. I wanted to
- eliminate signal issues
- make sure both the switches connect directly to the controller.
Still did not work. Then i started closely looking at ozw logs. I noticed something strange and wanted to discuss this with u.When the device is added to the zwave network it fires a series of command. One of them is ProtectionCmd_Get. When node2 and node3 registers with the controller it sends ProtectionCmd_Get and it gets a timeout msg. Logs shown below.
2020-03-23 00:21:10.380 Info, Node002, Sending (Query) message (Callback ID=0x1d, Expected Reply=0x04) - ProtectionCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x75, 0x02, 0x25, 0x1d, 0xaa
2020-03-23 00:21:10.380 Info, Node002, Encrypted Flag is 0
2020-03-23 00:21:10.388 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-03-23 00:21:10.389 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2020-03-23 00:21:10.404 Detail, Node002, Received: 0x01, 0x07, 0x00, 0x13, 0x1d, 0x00, 0x00, 0x02, 0xf4
2020-03-23 00:21:10.404 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x1d received (expected 0x1d)
2020-03-23 00:21:10.404 Info, Node002, Request RTT 23 Average Request RTT 23
2020-03-23 00:21:10.404 Detail, Node002, Expected callbackId was received
2020-03-23 00:21:20.381 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s). Command: "ProtectionCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x75, 0x02, 0x25, 0x1d, 0xaa"
2020-03-23 00:21:20.381 Detail, Node002, Removing current message
2020-03-23 00:21:20.381 Detail, Node002, Notification: Notification - TimeOut
2020-03-23 00:21:20.381 Detail, Node002, Query Stage Complete (Session)
2020-03-23 00:21:20.381 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2020-03-23 00:21:20.381 Detail, Node002, QueryStage_Dynamic
2020-03-23 00:21:20.381 Detail, Node002, Queuing (Send) SwitchBinaryCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x25, 0x02, 0x25, 0x1e, 0xf9
2020-03-23 00:21:20.382 Detail, Node002, Queuing (Query) Query Stage Complete (Dynamic)
When working switch registers i get a success response. Check the below logs.
2020-03-23 00:45:45.836 Info, Node004, Sending (Query) message (Callback ID=0x50, Expected Reply=0x04) - ProtectionCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x75, 0x02, 0x25, 0x50, 0xe1
2020-03-23 00:45:45.836 Info, Node004, Encrypted Flag is 0
2020-03-23 00:45:45.846 Detail, Node004, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-03-23 00:45:45.846 Detail, Node004, ZW_SEND_DATA delivered to Z-Wave stack
2020-03-23 00:45:45.860 Detail, Node004, Received: 0x01, 0x07, 0x00, 0x13, 0x50, 0x00, 0x00, 0x02, 0xb9
2020-03-23 00:45:45.860 Detail, Node004, ZW_SEND_DATA Request with callback ID 0x50 received (expected 0x50)
2020-03-23 00:45:45.860 Info, Node004, Request RTT 24 Average Request RTT 23
2020-03-23 00:45:45.860 Detail, Node004, Expected callbackId was received
2020-03-23 00:45:45.877 Detail, Node004, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x04, 0x04, 0x75, 0x03, 0x00, 0x00, 0x87
2020-03-23 00:45:45.878 Detail,
2020-03-23 00:45:45.878 Info, Node004, Response RTT 41 Average Response RTT 40
2020-03-23 00:45:45.878 Info, Node004, Received a Protection report: Unprotected
2020-03-23 00:45:45.878 Detail, Node004, Initial read of value
2020-03-23 00:45:45.878 Detail, Node004, Expected reply and command class was received
2020-03-23 00:45:45.878 Detail, Node004, Message transaction complete
Does this ring any bells?
i am having the exact same issue. i replied to another thread with users having this issues here: LZW31-SN Dimmer, Manual turn on no state reporting - #5 by smos08 - Sorting Category - Inovelli Community
this is my first zwave device as well as inovelli switch. using zwave2mqtt every other sensor works fine and i can even see the power change but it does not update the status in HA. i can control from HA without issue. here are my debug logs when adding a device and manually toggling from the switch, you can see the power usage change but nothing coming from the state change
2020-04-12T20:00:46.678Z z2m:Zwave Success zwave api call addNode true
2020-04-12T20:00:46.680Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: ‘AddDevice Starting’ }
2020-04-12T20:00:46.681Z z2m:Zwave controller command { nodeid: 0, state: 4, errcode: 0, help: ‘AddDevice Waiting’ }
2020-04-12T20:00:59.620Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: ‘AddDevice InProgress’ }
2020-04-12T20:00:59.809Z z2m:Zwave controller command { nodeid: 4, state: 6, errcode: 0, help: ‘AddDevice InProgress’ }
2020-04-12T20:01:00.123Z z2m:Zwave controller command { nodeid: 4, state: 6, errcode: 0, help: ‘AddDevice InProgress’ }
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 0 (COMMAND_CLASS_NO_OPERATION)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 114 (COMMAND_CLASS_MANUFACTURER_SPECIFIC)
2020-04-12T20:01:00.180Z z2m:Zwave Node added 4
2020-04-12T20:01:00.180Z z2m:Zwave ValueAdded: 4-94-1-0 ZWave+ Version
2020-04-12T20:01:00.181Z z2m:Zwave ValueAdded: 4-94-1-1 InstallerIcon
2020-04-12T20:01:00.182Z z2m:Zwave ValueAdded: 4-94-1-2 UserIcon
2020-04-12T20:01:00.182Z z2m:Zwave ValueAdded: 4-38-1-0 Level
2020-04-12T20:01:00.183Z z2m:Zwave ValueAdded: 4-38-1-1 Bright
2020-04-12T20:01:00.183Z z2m:Zwave ValueAdded: 4-38-1-2 Dim
2020-04-12T20:01:00.184Z z2m:Zwave ValueAdded: 4-38-1-3 Ignore Start Level
2020-04-12T20:01:00.184Z z2m:Zwave ValueAdded: 4-38-1-4 Start Level
2020-04-12T20:01:00.185Z z2m:Zwave ValueAdded: 4-134-1-0 Library Version
2020-04-12T20:01:00.186Z z2m:Zwave ValueAdded: 4-134-1-1 Protocol Version
2020-04-12T20:01:00.186Z z2m:Zwave ValueAdded: 4-134-1-2 Application Version
2020-04-12T20:01:00.187Z z2m:Zwave ValueAdded: 4-115-1-0 Powerlevel
2020-04-12T20:01:00.187Z z2m:Zwave ValueAdded: 4-115-1-1 Timeout
2020-04-12T20:01:00.188Z z2m:Zwave ValueAdded: 4-115-1-2 Set Powerlevel
2020-04-12T20:01:00.188Z z2m:Zwave ValueAdded: 4-115-1-3 Test Node
2020-04-12T20:01:00.189Z z2m:Zwave ValueAdded: 4-115-1-4 Test Powerlevel
2020-04-12T20:01:00.189Z z2m:Zwave ValueAdded: 4-115-1-5 Frame Count
2020-04-12T20:01:00.190Z z2m:Zwave ValueAdded: 4-115-1-6 Test
2020-04-12T20:01:00.190Z z2m:Zwave ValueAdded: 4-115-1-7 Report
2020-04-12T20:01:00.191Z z2m:Zwave ValueAdded: 4-115-1-8 Test Status
2020-04-12T20:01:00.192Z z2m:Zwave ValueAdded: 4-115-1-9 Acked Frames
2020-04-12T20:01:00.192Z z2m:Zwave ValueAdded: 4-152-1-0 Secured
2020-04-12T20:01:00.193Z z2m:Zwave ValueAdded: 4-91-1-256 Scene Count
2020-04-12T20:01:00.193Z z2m:Zwave ValueAdded: 4-91-1-257 Scene Reset Timeout
2020-04-12T20:01:00.195Z z2m:Zwave ValueAdded: 4-117-1-0 Protection
2020-04-12T20:01:00.196Z z2m:Zwave controller command { nodeid: 4, state: 7, errcode: 0, help: ‘AddDevice Completed’ }
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 94 (COMMAND_CLASS_ZWAVEPLUS_INFO)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 38 (COMMAND_CLASS_SWITCH_MULTILEVEL)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 112 (COMMAND_CLASS_CONFIGURATION)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 133 (COMMAND_CLASS_ASSOCIATION)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 134 (COMMAND_CLASS_VERSION)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 90 (COMMAND_CLASS_DEVICE_RESET_LOCALLY)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 115 (COMMAND_CLASS_POWERLEVEL)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 50 (COMMAND_CLASS_METER)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 152 (COMMAND_CLASS_SECURITY)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 91 (COMMAND_CLASS_CENTRAL_SCENE)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 117 (COMMAND_CLASS_PROTECTION)
OpenZWave Warning, Localization::SetupCommandClass: Localization Warning: No Entry for CommandClass - CC: 34 (COMMAND_CLASS_APPLICATION_STATUS)
2020-04-12T20:01:00.209Z z2m:Zwave Notification from node 4: Notification - NoOperation (2)
2020-04-12T20:01:00.210Z z2m:Zwave ValueAdded: 4-114-1-0 Loaded Config Revision
2020-04-12T20:01:00.210Z z2m:Zwave ValueAdded: 4-114-1-1 Config File Revision
2020-04-12T20:01:00.211Z z2m:Zwave ValueAdded: 4-114-1-2 Latest Available Config File Revision
2020-04-12T20:01:00.211Z z2m:Zwave ValueAdded: 4-114-1-3 Device ID
2020-04-12T20:01:00.212Z z2m:Zwave ValueAdded: 4-114-1-4 Serial Number
2020-04-12T20:01:00.260Z z2m:Zwave ValueAdded: 4-112-1-1 Dimming Speed
2020-04-12T20:01:00.261Z z2m:Zwave ValueAdded: 4-112-1-2 Dimming Speed (From Switch)
2020-04-12T20:01:00.261Z z2m:Zwave ValueAdded: 4-112-1-3 Ramp Rate
2020-04-12T20:01:00.262Z z2m:Zwave ValueAdded: 4-112-1-4 Ramp Rate (From Switch)
2020-04-12T20:01:00.262Z z2m:Zwave ValueAdded: 4-112-1-5 Minimum Level
2020-04-12T20:01:00.263Z z2m:Zwave ValueAdded: 4-112-1-6 Maximum Level
2020-04-12T20:01:00.263Z z2m:Zwave ValueAdded: 4-112-1-7 Invert Switch
2020-04-12T20:01:00.263Z z2m:Zwave ValueAdded: 4-112-1-8 Auto Off Timer
2020-04-12T20:01:00.264Z z2m:Zwave ValueAdded: 4-112-1-9 Default Level (Local)
2020-04-12T20:01:00.265Z z2m:Zwave ValueAdded: 4-112-1-10 Default Level (Z-Wave)
2020-04-12T20:01:00.265Z z2m:Zwave ValueAdded: 4-112-1-11 State After Power Restored
2020-04-12T20:01:00.266Z z2m:Zwave ValueAdded: 4-112-1-12 Association Behavior
2020-04-12T20:01:00.266Z z2m:Zwave ValueAdded: 4-112-1-13 LED Indicator Color
2020-04-12T20:01:00.267Z z2m:Zwave ValueAdded: 4-112-1-14 LED Strip Intensity
2020-04-12T20:01:00.267Z z2m:Zwave ValueAdded: 4-112-1-15 LED Strip Intensity (When OFF)
2020-04-12T20:01:00.268Z z2m:Zwave ValueAdded: 4-112-1-16 LED Strip Effect
2020-04-12T20:01:00.268Z z2m:Zwave ValueAdded: 4-112-1-17 LED Strip Timeout
2020-04-12T20:01:00.269Z z2m:Zwave ValueAdded: 4-112-1-18 Active Power Reports
2020-04-12T20:01:00.269Z z2m:Zwave ValueAdded: 4-112-1-19 Periodic Power & Energy Reports
2020-04-12T20:01:00.269Z z2m:Zwave ValueAdded: 4-112-1-20 Energy Reports
2020-04-12T20:01:00.270Z z2m:Zwave ValueAdded: 4-112-1-21 AC Power Type
2020-04-12T20:01:00.270Z z2m:Zwave ValueAdded: 4-112-1-22 Switch Type
2020-04-12T20:01:00.271Z z2m:Zwave ValueAdded: 4-91-1-0 Scene Count
2020-04-12T20:01:00.271Z z2m:Zwave ValueAdded: 4-91-1-2 Top Button Scene
2020-04-12T20:01:00.271Z z2m:Zwave ValueAdded: 4-91-1-1 Bottom Button Scene
2020-04-12T20:01:00.272Z z2m:Zwave ValueAdded: 4-91-1-3 Config Button Scene
OpenZWave Warning, Node004, Zwave+ Node Type (0x00) - NOT FOUND. No Mandatory Command Classes Loaded:
OpenZWave Warning, Node004, Zwave+ Device Type (0x0600) - NOT FOUND. No Mandatory Command Classes Loaded:
OpenZWave Warning, Node004, ZWave+ Role Type (0x05) - NOT FOUND. No Mandatory Command Classes Loaded:
2020-04-12T20:01:10.306Z z2m:Zwave Notification from node 4: Notification - TimeOut (1)
OpenZWave Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s). Command: “SecurityCmd_SupportedGet (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x98, 0x02, 0x25, 0x37, 0x6b”
2020-04-12T20:01:10.497Z z2m:Zwave node 4 AVAILABLE: Inovelli - LZW31-SN Dimmer Red Series (Unknown)
2020-04-12T20:01:10.543Z z2m:Zwave ValueAdded: 4-50-1-0 Electric - kWh
2020-04-12T20:01:10.546Z z2m:Zwave ValueAdded: 4-50-1-2 Electric - W
2020-04-12T20:01:10.548Z z2m:Zwave ValueAdded: 4-50-1-256 Exporting
2020-04-12T20:01:10.548Z z2m:Zwave ValueAdded: 4-50-1-257 Reset
OpenZWave Warning, Node004, CommandClass COMMAND_CLASS_CENTRAL_SCENE HandlerMsg Returned False
OpenZWave Warning, CheckCompletedNodeQueries m_allNodesQueried=1 m_awakeNodesQueried=1
2020-04-12T20:01:11.344Z z2m:Zwave node 4 ready: Inovelli - LZW31-SN Dimmer Red Series (Unknown)
2020-04-12T20:02:46.949Z z2m:Zwave zwave node 4: changed: 50-1-0:Electric - kWh:0.049 → 0.055
2020-04-12T20:02:46.953Z z2m:Zwave zwave node 4: changed: 50-1-256:Exporting:false → false
2020-04-12T20:04:02.950Z z2m:Zwave zwave node 4: changed: 50-1-2:Electric - W:209 → 0
2020-04-12T20:04:02.954Z z2m:Zwave zwave node 4: changed: 50-1-256:Exporting:false → false
2020-04-12T20:05:26.048Z z2m:Zwave zwave node 4: changed: 50-1-2:Electric - W:0 → 211.8
2020-04-12T20:05:26.051Z z2m:Zwave zwave node 4: changed: 50-1-256:Exporting:false → false
2020-04-12T20:07:20.805Z z2m:Zwave zwave node 4: changed: 50-1-0:Electric - kWh:0.055 → 0.066
2020-04-12T20:07:20.808Z z2m:Zwave zwave node 4: changed: 50-1-256:Exporting:false → false
in a previous attempt to fix this issue i did see “duplicate scene notification …dropping” in the OZW_Log.txt but i am not seeing that since my reset of everything.
has anyone found a solution? i’m moving into a new house and was about to go crazy on inovelli switches but may go back to lutron if i can’t get them working.