Issue reading states of Z-Wave switches

christheradioguy · June 28, 2017, 2:09pm

Just as an additional update to my polling issue; When I go to the ‘ZWave’ tab in the WebGUI and slect the node and press ‘refresh’ the switch is correctly polled and the proper state shows up on the main page, is there any way to automate this process? I would assume that the Z-Wave polling schedule would take care of this, would it not?

lmamakos · June 29, 2017, 2:03am

All three have companion switches connected. I noticed tonight that more than one switch seems to be unreliable like this. two of the switches were on, and the state wasn’t reflected in HASS. I suppose I’ll have to set up polling to capture the state of the switches.

Like @christheradioguy, I notice if I perform a “refresh” operation, the current state is updated.

lmamakos · June 29, 2017, 1:23pm

Curiously, operating the companion switch doesn’t seem to update the state in HASS, at least not reliably from the limited testing I did. I suppose I will just have to arrange to poll these things to get a reliable reflection of their state… haven’t been successful with that yet.

lmamakos · June 29, 2017, 1:29pm

I wonder if my problem with polling and refreshing the value is that I have “switches” and not “lights”?

From Z-Wave - Home Assistant

refresh_value (Optional): Enable refreshing of the node value. Only the light component uses this. Defaults to False.

christheradioguy · June 29, 2017, 3:16pm

For what it’s worth I managed to come up with a hacky solution to update the state of the switches. I added an entry to my crontab to run a CURL command to use the API to call the refresh_node command. Here’s the CURL command if anyone’s interested:

curl -X POST -H “Content-Type: application/json” -d ‘{“node_id”: “3”}’ https://localhost:8123/api/services/zwave/refresh_node -k

rise and repeat for each node. Seems to work for dimmers (lights) as well as switches.

lmamakos · June 30, 2017, 12:34am

@christheradioguy, I did something similar to what you suggested, but inside of HASS. I created a script that does:

rescan_zwave:
  alias: Refresh zwave
  sequence:
    - alias: refresh zwave 6
      service: zwave.refresh_node
      data:
        node_id: 6
    - alias: refresh zwave 7
      service: zwave.refresh_node
      data:
        node_id: 7
    - alias: refresh zwave 8
      service: zwave.refresh_node
      data:
        node_id: 8

and then wrote an automation to call it every 5 minutes:

- alias: zwave refresher
  trigger:
    - platform: time
      minutes: "/5"
      seconds: 00
  action:
    - service: script.rescan_zwave

This seems crude, yet unsatisfying. There appears to be some sort of refresh capability inside of HASS, but I’ve not been able to make it work. I didn’t investigate if there was a way to do all of the zwave devices as I don’t want to bang on my zwave door lock since it’s battery powered. I’ve had no problem getting state change messages from it since day 1.

jwelter · June 30, 2017, 11:03am

Ack. These sorts of tricks are horrible! And will cause scalability issues as you grow your zwave networks.

christheradioguy · June 30, 2017, 4:21pm

I realize this, but not sure what other options I have… It’s kinda important to know the states of my switches and HomeAssistant doesn’t seem to read the state of the switch when set to poll via the ZWave options.

Ovbiously going forward I can ensure I buy 100% compatible ZWave switches, but not sure what I can do with my existing 3 switches.

Open to better solutions…

christheradioguy · June 30, 2017, 4:23pm

Same boat here, all my other ZWave devices (lock, thermostats) all update their state automatically. Just these damn switches and dimmers which are a pain.

jwelter · June 30, 2017, 6:15pm

Did you set polling_interval for these 3 switches? By default polling_interval is 0 so they won’t poll.

lmamakos · July 1, 2017, 12:23am

I don’t seem to be able to get polling to work. I tried setting this up on the zwave configuration tab, which results in stuff getting put in the config/zwave_device_config.yaml file like:

lock.schlage_be469nxcen_touchscreen_deadbolt_locked_2_0:
  ignored: false
  polling_intensity: 0
zwave.lr_inner_lights:
  ignored: false
  polling_intensity: 1
switch.lr_inner_lights_switch:
  ignored: false
  polling_intensity: 1
zwave.lr_center_lights:
  ignored: false
  polling_intensity: 1
zwave.lr_outer_lights:
  ignored: false
  polling_intensity: 1
switch.lr_center_lights_switch:
  ignored: false
  polling_intensity: 1
switch.lr_outer_lights_switch:
  ignored: false
  polling_intensity: 1

And I set

 polling_interval: 30000

in configuration.yaml, but didn’t see evidence of polling in OWZ_Log.txt. Then I did the script and automation to poke at it, and I see all the activity. I would like to think that the polling would be lighter weight than the “refresh_node” operation which seems to do multiple pokes the devices, at least based on what I see in the (ever growing!) OWZ_Log.txt file.

I tried adding a customize: section to the zwave: configuration as I saw suggested elsewhere here and putting the polling_intensity stuff in there, but that wasn’t accepted.

ghowell24 · July 26, 2017, 9:52pm

Here is what I have, works perfectly and I can see the polling data in OZW_log.txt every 30 seconds only for the nodes requested. Not sure if this matters or not, but I am running 0.49

zwave:
  usb_path: /dev/ttyACM0
  config_path: /srv/homeassistant/src/open-zwave-control-panel/config
  network_key: "*******************************"
  new_entity_ids: true
  polling_interval: 30000
  device_config:
    switch.porch_light_switch:
      polling_intensity: 1
    switch.garage_light_switch:
      polling_intensity: 1

christheradioguy · July 31, 2017, 7:23pm

Thanks for the suggestion, I did not have polling_intensitity set in the configuration.yamal file, rather I was setting in via the ZWave control panel in the GUI I’ll give this a try and see if it makes a difference.

WaXHeLL · August 4, 2017, 6:10pm

@christheradioguy The Leviton switches should support instant status (even the non ZWP ones) without polling. I have some ancient ones that have support for it (Leviton calls it “hail”). Maybe one of the configuration values in the switch got inadvertently set to a different mode?

50m3rer0 · August 13, 2017, 6:57pm

where would you check for these values, on HA zwave control panel or OZW?

WaXHeLL · August 13, 2017, 8:42pm

It gets passed from ozw to HA so both control panels should be able to detect it. There is a parameter section in HA that allows you to configure the parameters.

This is all assuming that OZW has a fully detailed XML file for your device. If there is no detailed XML file, neither will know what parameter does what.

christheradioguy · August 13, 2017, 9:47pm

I’ll have a look through the switch’s manual for anything called ‘hail’ but it doesn’t ring a bell.

Joe_Saiko · September 7, 2017, 4:03pm

OZW is passing status on a manual switch event. It’s not getting handled by HA.

DEBUG:libopenzwave:notif_callback : new notification
DEBUG:libopenzwave:notif_callback : Notification type : 26, nodeId : 2
DEBUG:libopenzwave:notif_callback : call callback context
DEBUG:openzwave:zwcallback args=[{‘notificationType’: ‘Notification’, ‘notificationCode’: 1, ‘homeId’: 25503801, ‘nodeId’: 2}]
DEBUG:openzwave:Z-Wave Notification : {‘notificationType’: ‘Notification’, ‘notificationCode’: 1, ‘homeId’: 25503801, ‘nodeId’: 2}
DEBUG:libopenzwave:notif_callback : end
DEBUG:libopenzwave:notif_callback : new notification
DEBUG:libopenzwave:notif_callback : Notification type : 22, nodeId : 2
DEBUG:libopenzwave:notif_callback : call callback context
DEBUG:openzwave:zwcallback args=[{‘notificationType’: ‘NodeQueriesComplete’, ‘homeId’: 25503801, ‘nodeId’: 2}]
DEBUG:openzwave:Z-Wave Notification NodeQueriesComplete : {‘notificationType’: ‘NodeQueriesComplete’, ‘homeId’: 25503801, ‘nodeId’: 2}
DEBUG:openzwave:Z-Wave Notification Node : home_id: [0x01852839] id: [2] name: [] model: [Unknown: type=1c02, id=0334]
DEBUG:libopenzwave:notif_callback : end

Joe_Saiko · September 7, 2017, 5:13pm

I made some slight progress. I added the following XML file to OZW config.

github.com

OpenZWave/open-zwave/blob/master/config/leviton/dz15s.xml

<!--
Leviton Switch DZ15S 
http://products.z-wavealliance.org/products/1957
--><Product Revision="4" xmlns="https://github.com/OpenZWave/open-zwave">
  <MetaData>
    <MetaDataItem name="OzwInfoPage">http://www.openzwave.com/device-database/001D:0001:3401</MetaDataItem>
    <MetaDataItem name="ProductPic">images/leviton/dz15s.png</MetaDataItem>
    <MetaDataItem id="0001" name="ZWProductPage" type="3401">https://products.z-wavealliance.org/products/1957/</MetaDataItem>
    <MetaDataItem name="ExclusionDescription">When removing a device from a Z-Wave® network best practice is to use the exclusion command found in the Z-Wave® controller.
• Enter Programming Mode by holding the control button for 7 seconds, the Locator LED will turn amber.
• Follow directions in the Z-Wave® controller to enter exclusion mode.
• Tap the control button one time. The Locator LED will quickly flash green.
The Z-Wave® controller will exclude the Decora Smart device.
• The Z-Wave® controller will confirm successful exclusion from the network.</MetaDataItem>
    <MetaDataItem id="0001" name="Identifier" type="3401">DZ15S</MetaDataItem>
    <MetaDataItem name="Description">The wireless Leviton DZPA1 is a Z-Wave enabled plug-in outlet designed for use for most residential applications to control plug-in lamps, holiday lighting, or small appliances. The DZPA1 Plug-In Outlet is fully compatible with Z-Wave Plus certified controllers.  Offers manual control to turn loads on/off.  Manufacturer Parameters allow custom configuration via Z-Wave commands.  Rated for 5A LED and CFL bulbs, 1800W incandescent bulbs, 1800W Fluorescent, 15A Resistive, and 1/2 HP Motor.   These Z-Wave Plus devices support beaming, network wide inclusion, and over the air updates.  </MetaDataItem>
    <MetaDataItem name="InclusionDescription">Leviton Decora SmartTM Z-Wave® devices support two methods of inclusion.
When using a Z-Wave PlusTM certified controller choose Network Wide Inclusion.
Network Wide Inclusion:
Network Wide Inclusion allows your device to be added to the network using devices already in the network to assist with communication. Work your way from the closest devices to the controller outward.

This file has been truncated. show original

Now I am getting info from HA Core on an event but still no state change.

DEBUG:libopenzwave:notif_callback : new notification
DEBUG:libopenzwave:notif_callback : Notification type : 26, nodeId : 2
DEBUG:libopenzwave:notif_callback : call callback context
DEBUG:openzwave:zwcallback args=[{‘notificationType’: ‘Notification’, ‘notificationCode’: 1, ‘nodeId’: 2, ‘homeId’: 25503801}]
DEBUG:openzwave:Z-Wave Notification : {‘notificationType’: ‘Notification’, ‘notificationCode’: 1, ‘nodeId’: 2, ‘homeId’: 25503801}
DEBUG:libopenzwave:notif_callback : end
DEBUG:libopenzwave:notif_callback : new notification
DEBUG:libopenzwave:notif_callback : Notification type : 22, nodeId : 2
DEBUG:libopenzwave:notif_callback : call callback context
DEBUG:openzwave:zwcallback args=[{‘notificationType’: ‘NodeQueriesComplete’, ‘nodeId’: 2, ‘homeId’: 25503801}]
DEBUG:openzwave:Z-Wave Notification NodeQueriesComplete : {‘notificationType’: ‘NodeQueriesComplete’, ‘nodeId’: 2, ‘homeId’: 25503801}
DEBUG:openzwave:Z-Wave Notification Node : home_id: [0x01852839] id: [2] name: [] model: [Unknown: type=1c02, id=0334]
DEBUG:libopenzwave:notif_callback : end
INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: entity_id=zwave.leviton_unknown_type1c02_id0334, new_state=<state zwave.leviton_unknown_type1c02_id0334=Ready; lastResponseRTT=24, averageRequestRTT=17, receivedCnt=9, manufacturer_name=Leviton, averageResponseRTT=24, friendly_name=Leviton Unknown: type=1c02, id=0334, product_name=Unknown: type=1c02, id=0334, new_entity_id=zwave.leviton_unknown_type1c02_id0334, node_id=2, is_ready=True, is_failed=False, receivedDups=0, retries=0, neighbors={1, 3}, query_stage=Complete, lastRequestRTT=17, receivedTS=2017-09-07 13:12:16:205 , node_name=Leviton Unknown: type=1c02, id=0334, sentTS=2017-09-07 13:12:16:180 , sentCnt=13, sentFailed=0, max_baud_rate=40000, is_info_received=True, is_awake=True, is_zwave_plus=False, old_entity_id=zwave.leviton_unknown_type1c02_id0334_2, receivedUnsolicited=0, capabilities={‘listening’, ‘routing’, ‘beaming’} @ 2017-09-07T13:06:51.641287-04:00>, old_state=<state zwave.leviton_unknown_type1c02_id0334=Ready; lastResponseRTT=25, averageRequestRTT=18, receivedCnt=8, manufacturer_name=Leviton, averageResponseRTT=25, friendly_name=Leviton Unknown: type=1c02, id=0334, product_name=Unknown: type=1c02, id=0334, new_entity_id=zwave.leviton_unknown_type1c02_id0334, node_id=2, is_ready=True, is_failed=False, receivedDups=0, retries=0, neighbors={1, 3}, query_stage=Complete, lastRequestRTT=18, receivedTS=2017-09-07 13:08:08:744 , node_name=Leviton Unknown: type=1c02, id=0334, sentTS=2017-09-07 13:08:08:719 , sentCnt=12, sentFailed=0, max_baud_rate=40000, is_info_received=True, is_awake=True, is_zwave_plus=False, old_entity_id=zwave.leviton_unknown_type1c02_id0334_2, receivedUnsolicited=0, capabilities={‘listening’, ‘routing’, ‘beaming’} @ 2017-09-07T13:06:51.641287-04:00>>
DEBUG:homeassistant.components.websocket_api:WS 1713408080: Sending {‘type’: ‘event’, ‘id’: 2, ‘event’: {‘time_fired’: datetime.datetime(2017, 9, 7, 17, 12, 26, 291645, tzinfo=), ‘event_type’: ‘state_changed’, ‘origin’: ‘LOCAL’, ‘data’: {‘entity_id’: ‘zwave.leviton_unknown_type1c02_id0334’, ‘old_state’: <state zwave.leviton_unknown_type1c02_id0334=Ready; lastResponseRTT=25, averageRequestRTT=18, receivedCnt=8, manufacturer_name=Leviton, averageResponseRTT=25, friendly_name=Leviton Unknown: type=1c02, id=0334, product_name=Unknown: type=1c02, id=0334, new_entity_id=zwave.leviton_unknown_type1c02_id0334, node_id=2, is_ready=True, is_failed=False, receivedDups=0, retries=0, neighbors={1, 3}, query_stage=Complete, lastRequestRTT=18, receivedTS=2017-09-07 13:08:08:744 , node_name=Leviton Unknown: type=1c02, id=0334, sentTS=2017-09-07 13:08:08:719 , sentCnt=12, sentFailed=0, max_baud_rate=40000, is_info_received=True, is_awake=True, is_zwave_plus=False, old_entity_id=zwave.leviton_unknown_type1c02_id0334_2, receivedUnsolicited=0, capabilities={‘listening’, ‘routing’, ‘beaming’} @ 2017-09-07T13:06:51.641287-04:00>, ‘new_state’: <state zwave.leviton_unknown_type1c02_id0334=Ready; lastResponseRTT=24, averageRequestRTT=17, receivedCnt=9, manufacturer_name=Leviton, averageResponseRTT=24, friendly_name=Leviton Unknown: type=1c02, id=0334, product_name=Unknown: type=1c02, id=0334, new_entity_id=zwave.leviton_unknown_type1c02_id0334, node_id=2, is_ready=True, is_failed=False, receivedDups=0, retries=0, neighbors={1, 3}, query_stage=Complete, lastRequestRTT=17, receivedTS=2017-09-07 13:12:16:205 , node_name=Leviton Unknown: type=1c02, id=0334, sentTS=2017-09-07 13:12:16:180 , sentCnt=13, sentFailed=0, max_baud_rate=40000, is_info_received=True, is_awake=True, is_zwave_plus=False, old_entity_id=zwave.leviton_unknown_type1c02_id0334_2, receivedUnsolicited=0, capabilities={‘listening’, ‘routing’, ‘beaming’} @ 2017-09-07T13:06:51.641287-04:00>}}}

kmwoley · April 10, 2018, 6:26am

I finally gave up trying to get polling to work by setting things in the zwave: settings - I solved things using the solution @lmamakos provided. Feels really, really hacky. But it works.

Anything obvious I’m not doing right here?

zwave:
  usb_path: /dev/ttyACM0
  network_key: !secret ZWAVE_KEY
  polling_interval: 60000
  # polling to fix the 3/4-way lights not refreshing
  # correctly when operated from their remotes
  device_config:
    light.tv_room_light:
      polling_intensity: 1
      refresh_value: true
    light.stairway_light:
      polling_intensity: 1
      refresh_value: true