Closed patrickjane closed 5 years ago
Just out of curiosity did you try to poll your device instead of refreshing every 15 minutes? That seems a bit extreme.
FWIW - I have about 100 zwave devices, I do not see this issue (using the Aeotec Zwave USB stick)
Just out of curiosity did you try to poll your device instead of refreshing every 15 minutes? That seems a bit extreme.
I am new to HA. Could you explain what you mean by this?
@patrickjane - I think @dshokouhi was suggesting that you use the zwave:
device_config:
feature that should trigger polling of the state instead of using the zwave.refresh_node
service call.
e.g.
zwave:
usb_path: /dev/ttyACM0
network_key: !secret ZWAVE_KEY
polling_interval: 30000
device_config:
light.tv_room_light:
polling_intensity: 1
refresh_value: true
@dshokouhi - I believe this using an automation to periodically trigger zwave.refresh_node
is a common work around for the built-in zwave polling not functioning correctly. For some reason, it doesn't appear to work for everyone.
See: https://community.home-assistant.io/t/z-wave-polling-questions-answered/2394/28 https://community.home-assistant.io/t/issue-reading-states-of-z-wave-switches/20497/15
Filed: https://github.com/home-assistant/home-assistant/issues/13801
I didn't know of the polling feature, I'll give it a shot. The 'workaround' doesn't work for me anyway. Thanks for the info.
Nope, does not work for me. The status of the heaters remains wrong/outdated.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
I got the same issue. If I refresh twice the node (even manually with Z-Wave Network Management) Home assistant seem to crash. I try to refresh my node because my heaters remains outdated.
Home Assistant : 0.79.3
@patrickjane I found a trick. Instead of refreshing the whole node (which leads to a HA crash) I refresh only one entity. E.g :
- id: Refresh-FGT-001
alias: Z Wave refresher
hide_entity: true
trigger:
- platform: time
minutes: "/15"
seconds: 00
action:
- service: zwave.refresh_entity
data:
entity_id: sensor.thermometer
- service: zwave.refresh_entity
data:
entity_id: climate.heater
I just came across this as a potential workaround as well. Unfortunately states are not updating out of the box, and polling doesn't seem to work either. Calling zwave.refresh_node
does seem to work for now, hopefully I won't run into the issues mentioned above where it will crash HA. Is the issue that leads to needing this workaround in the first place being investigated also? I'm happy to help by providing my findings/logs/etc.
@dison4linux You might want to check https://github.com/OpenZWave/open-zwave/issues/1638 and https://community.home-assistant.io/t/fibaro-heat-controller-temperature-battery-not-displaying-correctly/70842/13 then. This is where I reported issues with the fibaro heaters. I don't think that anyone is working on them, however.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!
I run Home Assistant 0.116.4 with Aeotec ZW090 Z-Stick Gen5. I have the same problem, i.e., Home Assistant crashes on calling zwave.refresh_node.
Home Assistant release (
hass --version
): 0.64.3Python release (
python3 --version
): Python 3.5.3Component/platform: script / Z-wave
Description of problem:
I have set up the below mentioned automation to have HA refresh the state of my fibaro Z-wave thermostats. Otherwise it would not refresh the operation mode; it would get stuck on whatever state it was (Heat or Off).
However, when the automation is enabled, it will crash HA constantly after executing the script for the second time (thus crashing every 30 mins with an automation which runs every 15mins).
The crash can be reproduced by calling the script twice manually.
Expected:
Problem-relevant
configuration.yaml
entries and steps to reproduce: Automation:Script:
OR
Heres two backtraces I captured with attached gdb:
https://gist.github.com/patrickjane/08e4e67ec6bbf931367acce49d799bb1
https://gist.github.com/patrickjane/3832e44ca33b23f74bf6bcbc17b588a8
Relevant log from /var/log/syslog:
Additional info:
Running on raspberry pi 3 with raspbian stretch. HA was installed using the manual installation method (https://home-assistant.io/docs/installation/raspberry-pi/).
Z-wave config:
I am using the Z-Wave.Me ZME_UZB1 USB Stick as z-wave controller.