Does this mean at the remote wall switch or with OH? If it works both in OH and at the remote switch it is likely the rule? Are you sure your Astro is correct? Also how far north do you live (maybe no sunset?)
In DSL I have for my outside light
Channel “astro:sun:home:set#event” triggered START
If the OH widget is not working, switch the zwave to Debug via the UI and try an operation.
If I press the wall switch (physically), the state of the widget gets updated in OH.
I wanted to trigger the lights by using the OH GUI, independently from the rule set with the Astro binding. I checked the values both sunset and sunrise and both were updated with today’s values.
This is what I got when I used the widget to try to operate the lights remotely with OH GUI.
19:56:29.570 [DEBUG] [internal.profiles.ProfileCallbackImpl] - Delegating command 'ON' for item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' to handler for channel 'zwave:device:*********:node3:switch_binary'
19:56:29.573 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' predicted to become ON
19:56:29.582 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
19:56:29.586 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' changed from OFF to ON
19:56:42.089 [INFO ] [openhab.event.ThingStatusInfoEvent ] - Thing 'zwave:device:*********:node3' updated: OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
19:56:42.095 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:*********:node3' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
19:56:42.099 [INFO ] [openhab.event.ThingStatusInfoEvent ] - Thing 'zwave:device:*********:node3' updated: OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
19:56:42.968 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' received command OFF
19:56:42.969 [DEBUG] [internal.profiles.ProfileCallbackImpl] - Delegating command 'OFF' for item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' to handler for channel 'zwave:device:*********:node3:switch_binary'
19:56:42.972 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' predicted to become ON
19:57:27.480 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' received command OFF
19:57:27.481 [DEBUG] [internal.profiles.ProfileCallbackImpl] - Delegating command 'OFF' for item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' to handler for channel 'zwave:device:*********:node3:switch_binary'
19:57:27.484 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' predicted to become ON
19:57:28.495 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' received command OFF
19:57:28.496 [DEBUG] [internal.profiles.ProfileCallbackImpl] - Delegating command 'OFF' for item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' to handler for channel 'zwave:device:*********:node3:switch_binary'
19:57:28.500 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' predicted to become ON
19:57:56.712 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' received command OFF
19:57:56.713 [DEBUG] [internal.profiles.ProfileCallbackImpl] - Delegating command 'OFF' for item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' to handler for channel 'zwave:device:*********:node3:switch_binary'
19:57:56.717 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' predicted to become ON
This is what I got when I triggered the power switch from the OH GUI. I made 2 or 3 attempts from the GUI.
I have noticed the
OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
even though the channel link is reported as ONLINE in the GUI.
I then tried operating the switch on the wall physically. Pressed to switch the lights on, waited a 1 or 2 seconds, then switched off.
The log file then got flodded with these…
20:01:14.994 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
20:01:15.030 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
20:01:15.085 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
20:01:15.107 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
20:01:15.127 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
20:01:15.169 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
20:01:15.220 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
20:01:15.577 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to ON
20:01:48.462 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to OFF
20:01:48.469 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to OFF
20:01:48.571 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to OFF
20:01:48.612 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to OFF
20:01:48.638 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to OFF
20:01:48.669 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to OFF
20:01:48.687 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Switch' shall update to OFF
20:03:58.152 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Electric_meter_watts' shall update to 0
20:03:58.164 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Electric_meter_watts' shall update to 0
20:03:58.172 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Electric_meter_watts' shall update to 0
20:03:58.179 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Electric_meter_watts' shall update to 0
20:03:58.211 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Electric_meter_watts' shall update to 0
20:03:58.220 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Electric_meter_watts' shall update to 0
20:03:58.254 [INFO ] [openhab.event.ItemStateEvent ] - Item 'ZWave_Heatit_ZM_Relay_Single_Relay_16A_Outdoor_Lights_Electric_meter_watts' shall update to 0
So the log I’m interested in seeing while doing the test on the UI is the zwave debug. All the logs you set to Debug can be set back to INFO as they are not diagnostic for this.
That said there does appear to be a communication issue. If you have five lines on the Node3 UI page you could try the Heal and or the reinitialize options to see if that helps
If you don’t have five lines the device did not initialize after an OH restart and there could be something else wrong.
Edit: with the debug file you could check out the log viewer here and look for RED messages (not the TX, that is okay to be RED. Z-Wave Log Viewer (opensmarthouse.org)
I tried to check the Z-Wave Binding with the circle to change the log level, but did not find it. Could you please confirm which menus I have to click to get to it?
TBH I do not recall when that was added to OH UI. It should be Settings, go to the right side of the page, Addons, Zwave (should be a list of all your addons), then click on zwave and change to log level as needed.
If you do not have that, you have to SSH into karaf (openhab-cli console) and use log:set debug org.openhab.binding.zwave
Yes it is normal for the device to briefly go offline during a HEAL.
Glad you found it. It is even easier to find in OH4.1.
Anyway prior to the OFFLINE, I see 3 tries to turn the light on and they all timed out due to the device not acknowledging the message so there is some communication problem. Not sure what since the HEAL seemed to work (HEAL deletes all the old routes between the controller and the device, then reestablishes them.)
You could try the reinitialize option on the UI (if you are back to 5 lines) while in debug. It will be a large file, but the viewer will color code (REINITIALIZE reinterviews the device like during inclusion). My guess (and it is only that) is something is amiss SWITCH_BINARY command class.
Also can you post the XML for Node 3 when you get a chance. It is in the userdata/zwave folder (/var/lib/openhab/zwave)
