search

zachowj / hass-node-red

Companion Component for node-red-contrib-home-assistant-websocket to help integrate Node-RED with Home Assistant Core
MIT License
443 stars 180 forks source link

after upgrade to 3.01 device trigger stopped working in nodered #218

Closed kgiedrius closed 6 months ago

kgiedrius commented 9 months ago

I use zigbee2mqtt and device trigger node in nodered to trigger state changes from zigbee devices. After upgrading to 3.0.1 - this node do not react at all. Downgraded to 2.x version and everything works again

zachowj commented 9 months ago

Are you running node-red-contrib-home-assistant-websocket 0.57+?

https://github.com/zachowj/hass-node-red/releases/tag/v3.0.0

kgiedrius commented 9 months ago

issue with this one: https://github.com/zachowj/hass-node-red/releases/tag/v3.0.1 With nodered 14.5.0

where to check: node-red-contrib-home-assistant-websocket ?

zachowj commented 9 months ago

Under manage palette in Node-RED

image

kgiedrius commented 9 months ago
image
MJHeijster commented 9 months ago

Not sure if this is related. I have 0.57.2 for the websocket node. I noticed that the "trigger: state" doesn't let me check the current state of a helper of type input_boolean against a boolean: image If I match it against a string "on", it works. image

It also explains why in my case, some stopped working while others (where I had it set to "on") happily work.

GoSpursGoNL commented 9 months ago
image

So then you first need to upgrade that module, then update this custom integration in HACS, then stop Node-Red, restart HA, and start Node-Red. For me, that solved the problem.

github-actions[bot] commented 6 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.