My initial tests show that this is working perfectly. Now for full integration! Thank you again!
Trying to update to 0.2.0, but with: āgit+https://github.com/zachowj/node-red-contrib-home-assistant-websocket#masterā
I get this:
The Node-RED custom component is at version 0.2.0 but youāre installing the Node-RED package?
The Node-RED package canāt be installed via a Github link because it requires a build process to finished creating all the files. It is best to install it directly from npm. This will solve the missing files issue.
npm install node-red-contrib-home-assistant-websocket.
I was trying to update 'cause I have the (solved?) problem to have sensors duplicate (with _x appended) if use more than one node with same Home Assistant Config Name.
Is there another way to update the sensor value?
The sensor node is a one to one entity in HA. If you need to set a sensors value from two different flows use a link node.
How do you get this note to update the state of a binary sensor? When I give a second sensor node the same name and try to update it to false for instance it just creates a new binary sensor.
Sorry, Iām on the mobile and I can post more details in the morning.
To clarify, Iām trying to update the binary sensor state from the same flow that initially created it using a switch node to determine whether to set it true or false.
Use one sensor node and pass it the true/false as msg.payload
1 Like
Please Help Me
Iāve installed the hassio with hassos on VM, the node red is ok but for the two node in topic something is wrong and i donāt understand. Iāve installed the additional integration and every seem ok, iāve put the palette for the sensor in the flow and deployed immediately the entity was registered in history by the integration
but when i try to put a value by the msg.payload iāve got an error on node red below my node red say that iāve to install the integration!
the node red was installed by the add on of the store, meanwhile for the two nodes (already presents in the palette) Iāve created the custom component following instruction on the github of https://github.com/zachowj/hass-node-red
Is there anybody who can help me? Thank you a lot
Looks like you had a successful update after the error timestamp. My guess would be that the sensor node tried to update HA before it had responded back that it had the node-red integration installed.
thank you for your answer, yes it seems only a matter of syncro, anyway still the message remain anyway the node works corretly and in hass iāve my entity with value update corretly. It seems that at the deploy as the connection with the hass serve itās not very fast the node red is not able to know if the integration is working. After the deploy no error and everything goes well.
Change your deploy method on Node Red to be Flow only or Modified Nodes only. You donāt need to do a full redeploy every time.
HI @Kermit,
sorry to bother you but I would appreciate your help. Iām positive Iāve followed all the instructions and what I see looks promising
but I donāt see a thing āon the other sideā.
Seeing the word āRegisteredā suggests the webhook was created and I donāt see any message in the sensor configuration pop-up either.
Could you provide some guidance? many thanks in advance! 
disregard my post aboveā¦ I just went to lovelace UI and the entity seems to be available!!
First it need to register and second message will send msg.payload to Home Assistant
Not sure if this has been brought up yet. Would it be possible to have a msg output when the node is disabled?
Most of the cases in which I would use require a disable of stop message do disable the timer or node.
Team, for some reason today my node-red integration with home assistant seems to have gone south. All my nodes in Node-red, even the ones which are not exposed to HA (like the one snipped below) have stopped working.
I keep seeing this messages populate the node-red log
5 Mar 12:01:41 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:01:46 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:01:52 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:01:57 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:02 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:07 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:12 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:17 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:22 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:28 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
5 Mar 12:02:33 - [info] [server:Home Assistant] WebSocket Connecting http://supervisor/core
any idea what may be happening? Iāve tried some things already with no success. Upgrade HA, restarted the add-on, etc.
For the sensor-node, is there a way to change icon depending on state? Pretty much the only thing keeping me from converting the rest of my template sensors from HA to node-red.
I.e. in HA iām using the icon_template attribute but in node red I only see a field for icon.
Yeah, could make it process jinja2 templates if the icon value from NR contains {% or {{
Sorry, you mean itās already working like that or that you could make it in a future release?