Communication issues between Node Red and HA

[obsidian root]

I have several issues with Node Red that all appear to be related to communication issues between Node Red and HA.

1. Inject nodes and debug nodes don't work when I use NR within HA. The 1880 port workaround works.

2. One of my flows sets the LED color on several Inovelli Dimmers to notify me of specific things such as open doors, etc. I use zwave_js.multicast_set_value to set each device accordingly. Out of 7 devices, 3 error out with the following error: HomeAssistantError: Node(node_id=103) - NotFoundError: Value 103-112-0-99 not found on node Node(node_id=103). The 3 ids that NR says are not found were added today and work just fine. It is as if NR were not aware of them. I tried to re-interview the node in zwave js ui just to be sure but it did not help.

3. I have lots of these entries in my supervisor logs:

2024-10-06 17:08:16.934 INFO (MainThread) [supervisor.auth] Auth request from 'a0d7b954_nodered' for 'alex'
2024-10-06 17:08:16.935 INFO (MainThread) [supervisor.auth] Auth request from 'a0d7b954_nodered' for 'alex'
2024-10-06 17:08:16.945 INFO (MainThread) [supervisor.auth] Auth request from 'a0d7b954_nodered' for 'alex'```
Why so many (50+)? Also, not long ago there were lots of errors that mentioned SSL which I do not use. In NR config I turned on SSL, saved, rebooted, turned off SSL, rebooted, and the red errors no longer show. Maybe some progress but not much if any.

On a side note, something suddenly changed related to the zwave_js.multicast_set_value node as the flow was working fine. I went to make a change and suddenly it was complaining about needing an entity_id which can only be passed to it as there is no box for it. Although I have a group with all the devices that need the same setting sent to them, the only way I could get the flow to work was to send each one separately... but doesn't that defeat the purpose of multicast?

[obsidian root]

 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 18.1.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.2.rc1  (amd64 / qemux86-64)
 Home Assistant Core: 2024.10.1
 Home Assistant Supervisor: 2024.10.0```

[candid knoll]

Previously in Node-RED, it was possible to enter entity IDs in the target field, but this was incorrect for certain schemas in Home Assistant. This is no longer allowed. For example, if you check the zwave_js.multicast_set_value service page, you’ll see that entity_id should be placed in the data field instead.

[obsidian root]

I indeed changed my flow to feed one entity_id at a time which now requires 7 calls to thst service. Before I was using a group but that doesn't seem to work anymore. Since 3 devices were erroring out stating the parameter didn't exist (now solved), I need to try again with the group. The one major downside of using multicast appears to be that if one device doesn't work, the command fails for all... or maybe I am doing it all wrong.

[obsidian root]

Just noticed that if I access the flow while NR is in the iframe, it still shows the target field, while if I use NR via port 1880, it is not there... I edited another flow using NR within HA and it did not complain... so this issue is tied to the uber annoying issue where inject and debug don't work.