I’m not sure when but probably after the upgrade to v12 of the integration things stopped working, I don’t have that many automations so I didn’t realize something is wrong until I tried to use the button to switch on the light and it didn’t work, I logged in to HASS and when I clicked on NodeRed and I got fallowing message:
Add-on is not running. Please start it first
I get to configuration, clicked start and I got this
Safe mode is not working, configuration is minimal, I removed items npm_packages but didn’t work too. NodeRed integration logs are empty, supervisor logs showing the same error and nothing more
I’m running it on RPi3 and I’m kinda out of ideas what to do about it.
This node-red update is missing the stop timer node.
If you have used this node nothing work anymore in node-red.
Restoring the backup also does not work and you get an error.
I have the same problem and I’m definitely not satisfied about nodes suddenly removed because they are declared as “low usage/installs anst of them have not been maintained for years”. I’m using “starttimer”, “stop timer” and “looptimer” many places in my Node-Red setup and I have been using these nodes for years and this morning nothing is working anymore
I am sorry to have this unpolite reaction, but please don’t remove nodes like that. What about a description of how to build the nodes with “modern nodes” please please please. It seems I’m now looking into a weekend struggling with Node-Red (%&#¤%#”!”#¤%%&%)…
The following Node-RED where previously built-in, and have been removed:
node-red-contrib-alexa-home-skill
node-red-contrib-looptimer
node-red-contrib-statistics
node-red-contrib-stoptimer
node-red-contrib-timecheck
node-red-contrib-traffic
node-red-node-msgpack
node-red-node-sentiment
They have been removed because of their low usage/installs and most of them have not been maintained for years now. If you like to keep any of those, you can add/install them again yourself.
but you can just add them yourself if needed under addon configuration: