Z-wave Sensors not updating

jfridolf · January 29, 2019, 10:05am

Hi all,

I have a Aeotec ZW090 Z-Stick Gen5 EU connected to my Raspberry Pi running Hassbian with Home Assistant installed.

I then also have a Telldus TZWP-102 Plug-in Switch connected to an outlet and then some devices there.

The problem that I quite recently ran into, is that the sensors are no longer updating.
It used to work, but now it only updates the values if I reboot the Raspberry or restart the Home Assistant.

The switch function still works, I can turn on and off the outlet, but I cannot read the values IRL.

I have checked on Aeotecs webpage to see if there are any firmware updates, but there are none.

Any tips or ideas?
I have looked around here on the forum, but either my search parameters are bad or I simply not finding the right solution

Thanks in advance.

finity · January 29, 2019, 4:32pm

do the devices show up as updating in the ozw log?

jfridolf · January 29, 2019, 7:12pm

The log seems kinda empty compared to what I was expected… It has 400 lines, but it only covers 18 seconds of action.

In the log I cannot find: update, aeotec or telldus

finity · January 29, 2019, 7:53pm

check the OZW_log.txt for entries for the Node number of the devices and see if you see any activity for them.

zaneclaes · September 3, 2019, 1:09am

I’m also experiencing this problem across all z-wave devices. If I use “lock.clear_usercode” for my Yale lock (for example) the code is successfully cleared as tested with the physical device, but home-assistant will not reflect any changes until after rebooting. Calls to “lock.get_usercode” and such still report the (now invalid) code. Here is the contents of the OZW log after executing the clear command:

2019-09-03 01:07:33.054 Info, Node008, Value::Set - COMMAND_CLASS_USER_CODE - Code 2: - 2 - 1 - 0x00 0x00 0x00 0x00
2019-09-03 01:07:33.054 Detail, Node008, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_USER_CODE
2019-09-03 01:07:33.054 Detail, Node008, Queuing (Send) UserCodeCmd_Set (Node=8): 0x01, 0x0f, 0x00, 0x13, 0x08, 0x08, 0x63, 0x01, 0x02, 0x01, 0x00, 0x00, 0x00, 0x00, 0x25, 0x57, 0xf0
2019-09-03 01:07:33.054 Detail, Node008, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_USER_CODE
2019-09-03 01:07:33.054 Detail, Node008, Queuing (Send) UserCodeCmd_Get (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x63, 0x02, 0x02, 0x25, 0x58, 0xf3
2019-09-03 01:07:33.054 Detail, 
2019-09-03 01:07:33.054 Info, Node008, Processing (Send) Nonce Request message (Callback ID=0x57, Expected Reply=0x13)
2019-09-03 01:07:33.054 Info, Node008, Sending (Send) message (Callback ID=0x57, Expected Reply=0x13) - Nonce_Get(UserCodeCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x98, 0x40, 0x05, 0x02:
2019-09-03 01:07:33.059 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-03 01:07:33.059 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-09-03 01:07:34.497 Detail, Node008,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xeb
2019-09-03 01:07:34.497 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2019-09-03 01:07:34.497 Info, Node008, Request RTT 1443 Average Request RTT 1131
2019-09-03 01:07:34.582 Detail, Node008,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x08, 0x0a, 0x98, 0x80, 0x83, 0x4b, 0x41, 0xe8, 0x3a, 0x0e, 0x6a, 0xd9, 0x17
2019-09-03 01:07:34.582 Info, Node008, Received SecurityCmd_NonceReport from node 8
2019-09-03 01:07:34.582 Info, Node008, Sending (Send) message (Callback ID=0x59, Expected Reply=0x13) - UserCodeCmd_Set (Node=8): 0x01, 0x0f, 0x00, 0x13, 0x08, 0x08, 0x63, 0x01, 0x02, 0x01, 0x00, 0x00, 0x00, 0x00, 0x25, 0x59, 0xfe
2019-09-03 01:07:34.591 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-03 01:07:34.591 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-09-03 01:07:34.750 Detail, Node008,   Received: 0x01, 0x05, 0x00, 0x13, 0x59, 0x00, 0xb0
2019-09-03 01:07:34.750 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x59 received (expected 0x59)
2019-09-03 01:07:34.750 Info, Node008, Request RTT 1696 Average Request RTT 1413
2019-09-03 01:07:34.750 Detail,   Expected callbackId was received
2019-09-03 01:07:34.750 Detail,   Expected reply was received
2019-09-03 01:07:34.750 Detail,   Message transaction complete
2019-09-03 01:07:34.750 Detail, 
2019-09-03 01:07:34.750 Detail, Node008, Removing current message
2019-09-03 01:07:34.750 Detail, 
2019-09-03 01:07:34.750 Info, Node008, Processing (Send) Nonce Request message (Callback ID=0x58, Expected Reply=0x04)
2019-09-03 01:07:34.750 Info, Node008, Sending (Send) message (Callback ID=0x58, Expected Reply=0x04) - Nonce_Get(UserCodeCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x98, 0x40, 0x05, 0x02:
2019-09-03 01:07:34.757 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-03 01:07:34.757 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-09-03 01:07:34.830 Detail, Node008,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xeb
2019-09-03 01:07:34.830 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2019-09-03 01:07:34.830 Info, Node008, Request RTT 79 Average Request RTT 746
2019-09-03 01:07:34.912 Detail, Node008,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x08, 0x0a, 0x98, 0x80, 0xca, 0x4b, 0x70, 0x4b, 0x63, 0x97, 0xfe, 0x68, 0x29
2019-09-03 01:07:34.912 Info, Node008, Received SecurityCmd_NonceReport from node 8
2019-09-03 01:07:34.912 Info, Node008, Sending (Send) message (Callback ID=0x5a, Expected Reply=0x04) - UserCodeCmd_Get (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x63, 0x02, 0x02, 0x25, 0x5a, 0xf1
2019-09-03 01:07:34.921 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-03 01:07:34.921 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-09-03 01:07:35.038 Detail, Node008,   Received: 0x01, 0x05, 0x00, 0x13, 0x5a, 0x00, 0xb3
2019-09-03 01:07:35.038 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x5a received (expected 0x5a)
2019-09-03 01:07:35.038 Info, Node008, Request RTT 288 Average Request RTT 517
2019-09-03 01:07:35.038 Detail,   Expected callbackId was received
2019-09-03 01:07:35.734 Detail, Node008,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x08, 0x02, 0x98, 0x40, 0x21
2019-09-03 01:07:35.734 Info, Node008, Received SecurityCmd_NonceGet from node 8
2019-09-03 01:07:35.734 Info, NONCES: 0xa2, 0x92, 0xc2, 0x4b, 0x1c, 0xd0, 0x7e, 0x44
2019-09-03 01:07:35.734 Info, NONCES: 0x42, 0xd4, 0x24, 0x47, 0x4c, 0x66, 0x6f, 0x25
2019-09-03 01:07:35.734 Info, NONCES: 0x85, 0x29, 0xc1, 0x33, 0x32, 0xd3, 0xbf, 0x53
2019-09-03 01:07:35.734 Info, NONCES: 0xab, 0x93, 0x82, 0x06, 0xc1, 0x84, 0xca, 0x2d
2019-09-03 01:07:35.734 Info, NONCES: 0xa3, 0xab, 0x5e, 0xfb, 0x27, 0x30, 0x47, 0xbc
2019-09-03 01:07:35.734 Info, NONCES: 0x4d, 0xf0, 0xa7, 0x81, 0x7f, 0x44, 0x6a, 0x76
2019-09-03 01:07:35.734 Info, NONCES: 0x75, 0xf0, 0x72, 0xa0, 0xc3, 0xfa, 0x1f, 0xb4
2019-09-03 01:07:35.734 Info, NONCES: 0x7c, 0x0c, 0x36, 0x73, 0xf7, 0x8e, 0xf5, 0xb1
2019-09-03 01:07:35.734 Info, Node008, Sending (Send) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x08, 0x0a, 0x98, 0x80, 0xab, 0x93, 0x82, 0x06, 0xc1, 0x84, 0xca, 0x2d, 0x05, 0x01, 0xfd:
2019-09-03 01:07:35.741 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-03 01:07:35.741 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2019-09-03 01:07:35.872 Detail, Node008,   Received: 0x01, 0x05, 0x00, 0x13, 0x01, 0x00, 0xe8
2019-09-03 01:07:35.872 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2019-09-03 01:07:35.872 Info, Node008, Request RTT 1122 Average Request RTT 819
2019-09-03 01:07:35.962 Detail, Node008,   Received: 0x01, 0x24, 0x00, 0x04, 0x00, 0x08, 0x1e, 0x98, 0x81, 0x69, 0xf6, 0xf6, 0x81, 0x3c, 0x8f, 0xde, 0xd3, 0x27, 0xfa, 0xcb, 0xa4, 0x21, 0x9b, 0x5e, 0x3f, 0x98, 0xdd, 0x00, 0xab, 0x7f, 0x1f, 0x6e, 0x90, 0xf4, 0x3d, 0xf7, 0xfc, 0x5d
2019-09-03 01:07:35.962 Info, Raw: 0x98, 0x81, 0x69, 0xf6, 0xf6, 0x81, 0x3c, 0x8f, 0xde, 0xd3, 0x27, 0xfa, 0xcb, 0xa4, 0x21, 0x9b, 0x5e, 0x3f, 0x98, 0xdd, 0x00, 0xab, 0x7f, 0x1f, 0x6e, 0x90, 0xf4, 0x3d, 0xf7, 0xfc, 0x5d
2019-09-03 01:07:35.962 Detail, Node008, Decrypted Packet: 0x00, 0x71, 0x05, 0x71, 0x03, 0x00, 0xff, 0x06, 0x0f, 0x00, 0x00
2019-09-03 01:07:35.962 Detail, 
2019-09-03 01:07:35.962 Info, Node008, Response RTT 1212 Average Response RTT 1311
2019-09-03 01:07:35.962 Info, Node008, Received Alarm report: type=113, level=3, sensorSrcID=0, type:Access Control event:15, status=255
2019-09-03 01:07:35.962 Detail, Node008, Refreshed Value: old value=0, new value=113, type=byte
2019-09-03 01:07:35.962 Detail, Node008, Changes to this value are not verified
2019-09-03 01:07:35.962 Detail, Node008, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2019-09-03 01:07:35.962 Detail, Node008, Queuing (Send) DoorLockCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x62, 0x02, 0x25, 0x5b, 0xf1
2019-09-03 01:07:35.962 Detail, Node008, Refreshed Value: old value=0, new value=3, type=byte
2019-09-03 01:07:35.962 Detail, Node008, Changes to this value are not verified
2019-09-03 01:07:35.962 Detail, Node008, Refreshed Value: old value=0, new value=0, type=byte
2019-09-03 01:07:35.962 Detail, Node008, Changes to this value are not verified
2019-09-03 01:07:35.962 Detail, Node008, Refreshed Value: old value=1, new value=15, type=byte
2019-09-03 01:07:35.962 Detail, Node008, Changes to this value are not verified
2019-09-03 01:07:35.962 Detail, Node008, Notification: ValueChanged
2019-09-03 01:07:35.966 Detail, Node008, Notification: ValueChanged
2019-09-03 01:07:35.969 Detail, Node008, Notification: ValueChanged
2019-09-03 01:07:35.971 Detail, Node008, Notification: ValueChanged

kassai · March 22, 2020, 4:55pm

Did you ever find a solution to this?

I have the same issue with the zwave Aeotec ZW090 stick and and a floor heating from Heatit (Z-TRM2fx). After changing the temperature manually on the heater’s physical control panel, the update isn’t reflected in Home Assistant until I manually refresh the node entity.

Lorentz · June 19, 2020, 1:42pm

Same issue here. Did you find a solution?

jfridolf · June 22, 2020, 9:18am

I never found a solution for the problem unfortunately

n.e.m · September 8, 2020, 5:02am

I’m having the same problem with the latest version of Home Assistant. Anyone figure out why?

mirekmal · September 8, 2020, 6:33am

I faced the same with Fibaro Smart Implant. If inputs are configured as alarms, then I can instantly see the change in HA. However when inputs are configured as analog voltage sensors value stops to be updated. I overcome this with simple automation that runs every 10 seconds and calls zwave.refresh_node_value service. Not perfect solution, but does the job.

drmjuae · September 13, 2020, 6:17pm

Hi,
My first post

I have the same issue with all of my 45+ AeonLabs devices with the same setup as @jfridolf
When I switch On/Off through HA, it updates the GUI Web and App. However, if I switched it On/Off manually, it will never update unless I go to configuration > Integration > Z-wave Configure > Z-Wave Node Management > select that node and refresh it.

I also found out now that any manual trigger will not run any automation unless the node is refreshed.

I thought about refreshing all nodes every 5 minutes which is the only overkill solution for 45+ nodes!

Would you mind posting your solution step by step? I don’t know where to put those commands.

mirekmal · September 13, 2020, 8:43pm

@drmjuae here is the code I use for node value refreshment:

automation:
  - id: 'refreshing_car_sensor'
    alias: Refreshing Car Presence Sensor
    initial_state: True
    trigger:
      - platform: time_pattern
        seconds: '/10'                    # Refresh every 10 seconds
    condition: []
    action:
      - service: zwave.refresh_node_value
        data_template:
          node_id: 32                     # This is node ID of zwave device that is not refeeshing
          value_id: "72057594579796210"   # This is value ID of specific entity that does not refresh

Tricky part in code above is to find the value_id. You can make it by going to Developer Tools -> States and finding the entity that doest not refresh. Then valiue_id is one of entity’s attributes:

drmjuae · September 14, 2020, 1:34am

Awesome. Thank you very much @mirekmal .
Where should I post this code? yaml file?

mirekmal · September 14, 2020, 6:29am

Oh, sorry… it is automation, so you can put it wherever your automations are (in configuration.yaml - > automation section or in any package or include). Obviously depending on where the code goes it might require some tuning of indentation. I updated the code in previous post so you can copy/paste directly into configuration.yaml.

drmjuae · September 14, 2020, 12:44pm

@mirekmal This is working super nice

Appreciate your assistance

drmjuae · September 14, 2020, 3:02pm

If I use one automation it works fine. But when I add the second one, code editor stops me
I’m using configuration.yaml

Any idea

automation 1:		
	 - id: 'Office Lobby '	
	alias: Office Lobby	
	initial_state: True	
	trigger:	
		 - platform: time_pattern
		seconds: '/10'
	condition: []	
	action:	
	 - service: zwave.refresh_node_value	
	data_template:	
		node_id: 9
		value_id: 72057594193723392
automation 14:		
	 - id: 'Office Toilet Lights '	
	alias: Office Toilet Lights	
	initial_state: True	
	trigger:	
		 - platform: time_pattern
		seconds: '/10'
	condition: []	
	action:	
	 - service: zwave.refresh_node_value	
	data_template:	
		node_id: 8
		value_id: 72057594176946176

mirekmal · September 15, 2020, 7:08am

Instead of creating several automations (one per entity) you can list all of these entities in single automation in action part. Here is the real code I use to refresh 2 sensors:

automation:
  - id: 'refreshing_car_sensors'
    alias: Refreshing Car Presence Sensor
    initial_state: True
    trigger:
      - platform: time_pattern
        seconds: '/10'
    condition:
      - condition: state
        entity_id: input_boolean.zwave_active
        state: 'on'
    action:
      - service: zwave.refresh_node_value
        data_template:
          node_id: 32
          value_id: "72057594579796210"
      - service: zwave.refresh_node_value
        data_template:
          node_id: 32
          value_id: "144115188617724146"

Also in code you pasted here indentation is slightly off, so it might cause automation not to work…

drmjuae · September 15, 2020, 2:21pm

Thank you indentation is my worst part.
Yes, one for all is the best. I’m trying it now. but I see something new in the condition added/changed!

mirekmal · September 15, 2020, 4:17pm

Ah, yes… I created ‘sensor’ input_boolean.zwave_active that is turned on when zwave network initialization is complete. This way I’m not calling node refresh until network is up… just for sake of keeping log file free of unwanted clutter. If interested in here is the code:

input_boolean:
  zwave_active:
    name: Z-Wave Network Active
    initial: off
    icon: mdi:z-wave

# Set Z-Wave Network  flag to active
automation:
  - id: 'set_zwave_flag'
    alias: Set ZWave Flag
    initial_state: true
    trigger:
      platform: event
      event_type: zwave.network_ready
    action:
      - service: input_boolean.turn_on
        data_template:
          entity_id: input_boolean.zwave_active

drmjuae · September 15, 2020, 7:09pm

So clever work beautifully

Thank you so much @mirekmal