Node-red-contrib-home-assistant-websocket

Mikefila · November 15, 2021, 3:30pm

I have simple boolean sensors that correspond to users.

In the log entry when this flow is triggered I see

I’d like to see which user/sensor triggered the release.

maxym · November 15, 2021, 3:48pm

Yeah, it’s an option but it’s not run time. It must be “hardcoded” before being used by sending calls to nodes already being part of a flow. I do my best to avoid hardcoding.
IN addition, would it impact performance? WIll it create as many connections to HA as those nodes?

I initially meant something which allows to set the name on-the-fly without need to maintain explicit nodes for each user. Let’s say: NR connects HA with NR credentials, but adds specific user name to the HA call. Service Nodes (and others) would be fed with data found in input message.

I assume Node-red-contrib-home-assistant-websocket is not able to achieve that right away, but if HA API has support for such a feature, I would find NR extension useful.

SeveredDime · January 9, 2022, 9:17pm

So I’ve somehow nuked my install.

Node red stand alone install in docker on Unraid

I updated node-red-contrib-home-assistant-websocket in Node Red and I’m now getting the following error when starting Node Red

I’m removed and reinstalled the component via HACS. I’ve tried to remove the Palette from Node Red but I’m getting an in use error but stopped because I didn’t know if I would have to nuke my flows to do that, which I don’t currently want to do.

Talk to me like I’m 4 as I’m not the most experienced user.

Mikefila · January 9, 2022, 10:10pm

I don’t know where the logs are for the stand alone version but start there. You can also try to start nodered in safe mode node-red --safe

SeveredDime · January 9, 2022, 10:45pm

I had trouble finding the logs, so I’m not sure what was up but I managed to fix it by pulling down the container again. For what ever reason that worked.

typeonegative · February 9, 2022, 10:17pm

i just discovered this is not working as i expected. is that “& topic” can be also " & global.name"?

Kermit · February 9, 2022, 10:31pm

typeonegative · February 10, 2022, 9:56am

thank you!

lbedogni · November 25, 2022, 11:05am

These nodes do not work anymore for me. Every time I open node-red I see the message I post i this image. I tried to uninstall, reinstall, nothing solves it. Any idea?

CypherMK · November 27, 2022, 9:46pm

I have the same same issue. On install I get this:


-----------------------------------------------------------
2022-11-27T21:36:17.867Z Install : node-red-contrib-home-assistant-websocket 0.47.0

2022-11-27T21:36:17.946Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2022-11-27T21:37:08.603Z [err] npm
2022-11-27T21:37:08.605Z [err]  WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
2022-11-27T21:37:08.605Z [err] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
2022-11-27T21:37:08.606Z [err] 
2022-11-27T21:37:08.609Z [out] + [email protected]
2022-11-27T21:37:08.609Z [out] updated 1 package in 48.279s
2022-11-27T21:37:08.739Z rc=0

CypherMK · November 27, 2022, 9:55pm

Latest version known to work: 0.43.1

lbedogni · November 28, 2022, 9:10am

So I actually deleted an empty file with the same name in the node-red directory, and everything works.

CypherMK · November 28, 2022, 12:37pm

I had to update node red to version 3. So everything working now.

bwims · January 29, 2023, 3:46pm

Hi,

would it be possible to show an example of how to create an entity that will appear in HA?

I’m stuck. When I drop a binary sensor and attempt to configure it, it wants me to provide device details, rather than entity details.

Maybe it’s just that the documentation doesn’t go through the steps?

Thanks!

B.

Kermit · January 29, 2023, 4:21pm

Drop a binary sensor onto the NR workspace
Open the node in the editor, edit the entity config, and click on the pencil button.
Everything is optional on the entity config except the server and type.
Click Add for the entity config
Then Done in the binary sensor editor.
Deploy

In HA under Settings > Devices & Services > Node-RED you should now have a binary sensor with the state unknown. Attach a inject node to the binary sensor in NR and send it a payload and the state will update.

bwims · January 29, 2023, 5:08pm

Hi Kermit!

Thanks so much for your rapid response!

B.

bwims · February 3, 2023, 12:21pm

Hello again Kermit, one more question please? ( a multi-part…)

Once created, does the new sensor exist until destroyed?
How is it destroyed?
Should the same node that creates it be used to update it, or will a simple call service do?

Thanks again!

B.

bkcberry · March 30, 2023, 6:06pm

are there any known issues with 0.49.0? I just updated from 0.47.0, i am on Hass Core 2023.3.6 and the trigger:state and event: state nodes don’t seem to be working

johntdyer · May 16, 2023, 4:39pm

I was gettting the dreaded

23-05-16 10:21:50 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
23-05-16 10:21:50 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
23-05-16 10:21:50 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
23-05-16 10:21:50 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 258:WebSocketError(<WSCloseCode.MESSAGE_TOO_BIG: 1009>, 'Message size 4982137 exceeds limit 4194304') is not str
23-05-16 10:21:50 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed

and I was able to get past this by doing a few things

#1. Make a full backup incase you bork this, editing stuff in the .storage folder can really wreck your day if you’re not careful
#2. removed unifi and ibeacon integrations since they had amassed a few thousand entities. I had disabled all those entities via the UI and stopped them from adding more, but that didnt seem to matter… The websocket payload clearly showed them in the debug logs
#3. restarted HA to make things clean
#4. manually remove items from core.entitiy_registry config file ( steps below )

ha core stop
cp ~/config/.storage/core.entity_registry{,.original}
cat ~/config/.storage/core.entity_registry.original  | jq 'del (.data.entities[] |select(.platform=="unifiprotect"))' > ~/config/.storage/core.entity_registry

#5. Clean up core.device_registry ‘deleted_items’ as discussed here
#6. Start up HA again

ha core start

#7. Look for errors in supervisor logs

docker logs -f hassio_supervisor -n 100

This seemingly got me going again … hope someone finds it helpful…

@Kermit I do have a quick question for you if you have a second… is there any way to monitor the current size of the payload so I can maybe get ahead of the problem next time before it impacts my “uptime” and I blow all my family error budget when all the automatons fail

S474N · September 7, 2023, 11:43am

After upgrade to NodeRED 3.1.0 I have problem with this plugin:

Does anyone have an idea how to solve this?

07. 09. 2023 13:41:37
7 Sep 13:41:37 - [warn] Deprecated API warning: Calls to RED.util.evaluateJSONataExpression must include a callback. This will not be optional in Node-RED 4.0. Please identify the node from the following stack and check for an update on npm. If none is available, please notify the node author.
07. 09. 2023 13:41:37
7 Sep 13:41:37 - [warn] Error: 
07. 09. 2023 13:41:37
    at Object.evaluateJSONataExpression (/usr/src/node-red/node_modules/@node-red/util/lib/util.js:775:18)
07. 09. 2023 13:41:37
    at JSONataService.evaluate (/data/node_modules/node-red-contrib-home-assistant-websocket/dist/common/services/JSONataService.js:58:39)
07. 09. 2023 13:41:37
    at CallService.evaluateJSONata (/data/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/BaseNode.js:131:36)
07. 09. 2023 13:41:37
    at CallService.onInput (/data/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/call-service/controller.js:63:50)
07. 09. 2023 13:41:37
    at CallService.preOnInput (/data/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/BaseNode.js:208:18)
07. 09. 2023 13:41:37
    at /usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:210:26
07. 09. 2023 13:41:37
    at Object.trigger (/usr/src/node-red/node_modules/@node-red/util/lib/hooks.js:166:13)
07. 09. 2023 13:41:37
    at callServiceNode.Node._emitInput (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:202:11)
07. 09. 2023 13:41:37
    at callServiceNode.Node.emit (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:186:25)
07. 09. 2023 13:41:37
    at callServiceNode.Node.receive (/usr/src/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:494:10)
07. 09. 2023 13:41:37
    at deliverMessageToDestination (/usr/src/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:799:40)
07. 09. 2023 13:41:37
    at Immediate._onImmediate (/usr/src/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:815:21)
07. 09. 2023 13:41:37
    at processImmediate (internal/timers.js:464:21)