You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Beginning somewhere around 0.108 and Node Red 6.20 (probably one before), event poll nodes that used to fire once on a change now fire twice on each change. Hass.io is running on a ubuntu linux HyperV VM.
To Reproduce
I am running in Hass.io with the supervisor installed add-on, and both current as of this date (4/20/2022) at 0.108.6 node red 6.20 supervisor 217.
I created a test flow with simply event poll node, checked "on change" but not "on connect", and set it to point to a light. I connected it to a debug node, deployed, then turned the light off. The result is two debugs with identical time stamps.
Expected behavior
Fire either on change (with that option checked) or when polled, but once each.
Screenshots
Change is firing twice.
The poll is firing only once (correctly).
This behavior is new, and started within the last couple weeks. I have observed it on three different integrations (and one as a light group) and have no reason to think it is integration specific. I see nothing unusual in any log. I have not found any instance that works properly.
The behavior is not cosmetic (i.e. just in the debug), it actually generates two flow entries which (in this case a voice notification) fire twice, so it is two actual initiations.
Example Flow
[{"id":"e3804376.748f1","type":"tab","label":"Flow 1","disabled":false,"info":""},{"id":"23f9e697.2c73ca","type":"poll-state","z":"e3804376.748f1","name":"Closet Light","server":"2c833ee2.02d5d2","version":1,"exposeToHomeAssistant":false,"haConfig":[{"property":"name","value":""},{"property":"icon","value":""}],"updateinterval":"60","updateIntervalUnits":"seconds","outputinitially":false,"outputonchanged":true,"entity_id":"light.cabinet_lights","state_type":"str","halt_if":"","halt_if_type":"str","halt_if_compare":"is","outputs":1,"x":190,"y":220,"wires":[["f006c154.96e85"]]},{"id":"f006c154.96e85","type":"debug","z":"e3804376.748f1","name":"Any state change","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":440,"y":220,"wires":[]},{"id":"2c833ee2.02d5d2","type":"server","z":"","name":"Home Assistant"}]
Environment (please complete the following information):
Node Red Version: 1.0.5 or 6.2.0 (not sure which this comes from)
Node.js Version: no idea, whatever is packaged with the hass.io supervisor-added add-on
NR Home Assistant Plugin Version: 6.2.0 (what shows up on add-in page on supervisor)
Is Node Red running in Docker: HA addon
Other (please complete the following information):
Have you searched previous issues for duplicates: Yes.
Additional context
Have not looked at the code.
It should only fire once.
(Note: Originally submitted to Hass.io addons #543 and Frank pointed me here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Beginning somewhere around 0.108 and Node Red 6.20 (probably one before), event poll nodes that used to fire once on a change now fire twice on each change. Hass.io is running on a ubuntu linux HyperV VM.
To Reproduce
I am running in Hass.io with the supervisor installed add-on, and both current as of this date (4/20/2022) at 0.108.6 node red 6.20 supervisor 217.
I created a test flow with simply event poll node, checked "on change" but not "on connect", and set it to point to a light. I connected it to a debug node, deployed, then turned the light off. The result is two debugs with identical time stamps.
Expected behavior
Fire either on change (with that option checked) or when polled, but once each.
Screenshots
Change is firing twice.
The poll is firing only once (correctly).
This behavior is new, and started within the last couple weeks. I have observed it on three different integrations (and one as a light group) and have no reason to think it is integration specific. I see nothing unusual in any log. I have not found any instance that works properly.
The behavior is not cosmetic (i.e. just in the debug), it actually generates two flow entries which (in this case a voice notification) fire twice, so it is two actual initiations.
Example Flow
Environment (please complete the following information):
Other (please complete the following information):
Additional context
Have not looked at the code.
It should only fire once.
(Note: Originally submitted to Hass.io addons #543 and Frank pointed me here.
The text was updated successfully, but these errors were encountered: