node-red-contrib-home-assistant
node-red-contrib-home-assistant copied to clipboard
AYapejian
Updates?
Is this project dead? If you are no longer maintaining the project, can you pass it along to someone who can? With the latest changes in Home Assistant there are a lot of weird issues popping up.
Totally agree. This add-in prevents me from updating Hassio until I have the days required to address the issues that result.
i moved to this fork. https://github.com/Spartan-II-117/node-red-contrib-home-assistant
seems like he is maintaining it and looking at updating to accommodate new auth system
i moved to this fork. https://github.com/Spartan-II-117/node-red-contrib-home-assistant
seems like he is maintaining it and looking at updating to accommodate new auth system
While this is an option, it means I have to do a separate install of that palette? Then I have to reconfigure all my flows?
Or do I have to install NOT using the node package manager? It's not clear what the future of THAT fork is either. It seems silly to have to uninstall this one, install a different fork, and then if they stop maintaining it, move to something else.
This one has become the standard project for home assistant integration. It seems more logical to pass the project on to someone who WILL maintain it so that those of us who have been using it for so long don't have to rip everything out and start over, or worry about what fork we need to use this week.
no need to, download the files from fork and copy over. flows didn't need to change for me
no need to, download the files from fork and copy over. flows didn't need to change for me
So for every update I have to go download all the files and copy them over? This is not a solution at all.
Just do a:
npm install https://github.com/Spartan-II-117/node-red-contrib-home-assistant.git
for the moment it is for this repository, he is looking to publish a new version once he has finished coding for the new auth system.
Just do a:
npm install https://github.com/Spartan-II-117/node-red-contrib-home-assistant.git
Interesting you thumbsdown my comment when it seriously is NOT a solution to the problem at hand.
So you suggest instead of using the palette manager BUILT INTO node-red, I have to resort to a command line inside my Docker environment?
Everything suggested so far is a WORKAROUND, and not a SOLUTION. If you don't agree, fine, but don't discredit the issue with your convoluted workarounds. Not everyone wants to manage their installations in this manor. I automate my systems (not just my home), and things like this change my workflow considerably.
How am I being an asshole?
Everyone is suggesting workarounds, and not actually addressing the issue at hand. I am asking for AYapejian to pass the torch, and everyone here is saying that I need to migrate all the things, and use processes that go against the normal configurations.
Sorry, I was just messin' with you. I meant the first part though. You're not wrong, the project likely should be handed over to someone that is able to spend more time on it - that's not a dig at the repo owner either. A lot of people do depend on this project, and ideally it should keep pace with HA releases. It should probably be maintained by HA devs to be honest.
It should probably be maintained by HA devs to be honest.
I completely and utterly agree with this. It should be taken over by HA devs for better integration. I feel like it is an excellent way of interacting with Home Assistant, and should honestly be the preferred method of automation within HA.
for the moment it is for this repository, he is looking to publish a new version once he has finished coding for the new auth system.
I understand what he is doing, and I appreciate his work. I am asking that AYapejian pass the torch to him or someone else (a team preferably) for continuation of the project. I feel like some of you guys aren't understanding the point of my issue. We should have more cohesion with Home Assistant and more integration. I am not asking anyone to work on this or any other project, or for a way for my system to continue working, I am merely asking that @AYapejian allow the project to be taken over if he is not going to continue working on it.
This needs to be maintained by HA devs. I've only used it for a span of several months and it simply isn't updated frequently enough and it is becoming too important for anyone using NR with HA. Every new HA release brings another problem.
I see that the fork is now available and installable via NR under the name node-red-contrib-home-assistant-llat
I have switched to node-red-contrib-home-assistant-websocket now. Mode stable, uses websocket and has more functionality. Under a node you can see when it was last executed and what the status was at that time. And you can start a sequence after deployment.
@GoSpursGoNL - sorry if this is a noob-y question: what is the advantage of using websockets?
