Installed in a VM, got it, NR, MQTT, zigbee2MQTT up and running along with about 200+ devices, mainly zigbee2MQTT but with loads of others.
As far as I can tell, when I installed NR using the HASS Add Ons it installed with NR AND the HASS modules to support HASS Nodes. and it installed 0.62.2 of the node-red-contrib-home-assistant-websocket.
So did not upgrade anything, well knowingly
Since setting up NR evrytime I reboot HASS node-red-contrib-home-assistant-websocket uninstalls and a pile of integrations fail.
This is quite hard on new users, especially adding in the add ons to work with everything and that seems to demand a reboot with every on installed.
Makes for steep learning curve
This kinda stuff happens with all Home Automation hubs, Hubitat, Homey etc etc so not off put by it.
Certainly going around trying to find everywhere there is an autoupdate and disabling seems a prudent step right now
Well there I was thinking that any new install of Node-RED addon would upload the dependency version of WebSocket nodes. Clearly it must load the latest version, which currently causes a problem.
After quite a bit of searching I have found (stumbled upon) a way to downgrade nodes in the palette, and have I believe successfully tested this out.
I have a new Revolution Pi, on which I had recently upgraded Node-RED to v3.1.3, and I have therefore been able to upgrade the WebSocket nodes to the latest v0.62.2. This is all working nicely.
This must be one of those delightful features of browsers that causes so much trouble. I triple checked this last night before posting - my Windows PC and Chrome dutifully tries to save the file as
the (1) is because I already have a copy - and yes it does save it as .tgz which is the only format extension that NR appears to accept for upload.
The GitHub repository holds this as .zip, and as tar.gz and no amount of renaming worked for me yesterday, hence having to go to the npm registry and fiddle about there.
Anyway, if it works, I now know how to load a specific version of a node in stand alone NR on a Raspberry Pi, and how to load a specific version of a node in HASS NR addon.
Rolling back to websocket-0.59.0 saved our lives “for now”.
What is not clear to me is whether the home assistant node has actually been deprecated or whether it is an update problem.
Because in the first case I think it is enough to wait for future versions, in the second I suppose it is necessary to replace the functions …
This is an uncommon and temporary issue potentially affecting only anyone with Node-RED as an HA addon, using the HA WebSocket nodes.
IF you have Node-RED as an HA addon, AND you either manually update WebSocket nodes from the palette OR you make a new Node-RED addon installation
THEN you will pick up the latest version of the WebSocket that will not work with the current Node-RED version in the addon.
Solutions are:
don’t update manually (if you do, then above is a work-around to reverse this)
install the latest Node-RED addon, and then downgrade the installed version of WebSocket nodes to something that is compatible with the Node-RED in the addon
don’t use Node-RED as an addon, and update both Node-RED and the WebSocket nodes together
I can confirm that 0.62.2 works perfectly with Node-RED 3.1.3 as an off-HA install on a Raspberry Pi.
I updated to v 17.0.0 and my node red was not happy with an Unknown api-call service. After downgrading websocket to v 0.59.0 it was working correctly. I have verified that I am running Node-RED version: v3.1.3 but with websocket v 0.62.2 I have this issue. The procedure above using websocket v0.59.0 makes it work but I would really like to get v0.62.2 working and would love any help from the group here.
Do you know on which node it is happening specifically?
Have you tried turning off all you flows that are using the websocket, and re-enabling them one-at-a-time to pinpoint where on which flow it starts failing?
or is it that the websocket node is sending you an error on initialization and all your flows stop working?
