Closed Anian-igor closed 1 year ago
I assume that this is as per the breaking change notes:-
Requires Home Assistant nodes version 0.57.0+
Which would be fine if Node-Red was showing there being a version 0.57 - but it doesn't, 0.56.1 is all there is (for me). So it just looks like a badly timed release to me - it should have been held back until 0.57 nodes were available.
I assume that this is as per the breaking change notes:-
Requires Home Assistant nodes version 0.57.0+
Which would be fine if Node-Red was showing there being a version 0.57 - but it doesn't, 0.56.1 is all there is (for me). So it just looks like a badly timed release to me - it should have been held back until 0.57 nodes were available.
Same, I don't see how to install nodes 0.57
I revert back to 2.2.0 Working well
They released a beta of 0.57 of node-red-contrib-home-assistant-websocket.
This should automatically install the beta version and for me everything seems to work. Don't forget to revert this after 0.57 has actually released to prevent getting beta version in the future.
Thanks - good to know - but...
I don't use NodeRed within HA - it's an independant Docker image...(as is HA itself)
Thanks - good to know - but...
I don't use NodeRed within HA - it's an independant Docker image...(as is HA itself)
Do you have access to the Node-RED configuration file itself? If so, my comment results in the following snippit in the configuration file:
npm_packages:
- node-red-contrib-home-assistant-websocket@beta
I do - although nothing that looks quite like you've posted -
but for now I'm not going to edit that - I'd rather it get released on the normal channel,
Thanks.
Version of the custom_component
3.0.0
Describe the bug
Device trigger stop working after upgrade to 3.0.0 I see trigger information in device logs but stopped working in node-red