How many (nodered) service-calls at the same time?

[Rempert]

Hello!
I use nodered to switch different lamps via the node ‘call service’. I notice that every now and then a lamp does not switch. How many ‘call-service’ actions can you perform at the same time and could this be the problem of occasionally missing a switch?

it may be possible to place a small delay between the ‘call-service’ actions.

Does anyone here have experience?

greetings, Rempert

[mobile.andrew.jones (Andrew Jones)]

If you need to switch multiple lamps at the same time, why not just include all the entity_ids that need switching to a single service call?

[Rempert]

Thanks for your response… because of the overview I have all entities in node red together. So for each entity a separate ‘call-service’ node. But I’ll give your solution a try. If that fixes the problem I’m happy enough.

[Mikefila]

@Rempert

How many ‘call-service’ actions can you perform at the same time

1,000s

Have you looked at your logs nodered and home assistant? Do you know that the bulbs/switches aren’t dropping offline?

Que messages and send with specific rate

I don’t think this should be an issue unless your call-service node is receiving thousands of inputs every couple of milliseconds. I tested it with 10, 100, 1000, and 1 million requests and it was HA that closed the connection because it NR filled its message queue. It still was able to process around 7k messages before the queue filled. 2021-09-01 00:32:07 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140315601471088] Client exceeded max pending messages [2]: 2…

[Rempert]

Thanks… No, the lamps are not offline, I can switch them ‘manually’ right after the nodered action.

I’ll take another look at the nodered log files!

[jonrupell]

I have the exact same problem. For me it happens even with them in the same service call. Even tried making a group with all the devices and calling that group and it does the same thing. Did you ever solve this?