Error: socket hang up

[na-am]

1st, many thanks for that node
that's what i missed for my home automation :-)

from time to time i get after "updating" in the text node a "socket hang up" error
what does that mean? the pixoo is online and pings are about 5ms from the Raspi running Node-red

thx
na-am

[nickiv]

Please! I’m glad it is useful to you.

I checked my logs, and I don’t encounter the 'socket hangup' error. My Pixoo works 24/7.

So for now, I can only help with some guiding questions.

Could it be that you’re updating information too frequently? Pixoo has a built-in web server, and it’s possible that at some point it can’t handle the requests.

Currently, every update to any field triggers a request to Pixoo. I’ve thought about adding rate limiting directly to the module, but it’s not implemented yet.

If that might be the issue, you can use the Delay node in Rate Limit mode.

If the problem occurs rarely, it might be okay to just ignore it. Every field change triggers a full redraw. Even if one request fails, the latest values will be displayed on the next successful one. Although I understand that random errors are frustrating.

Also, it’s possible that the device occasionally disconnects from the Wi-Fi network, especially if it’s far from the router. You can monitor this by setting up 24/7 Ping.

Lastly, make sure you’re controlling Pixoo from only one device. Is it just Node-RED sending requests? If not, the chances of the built-in Pixoo server failing increase.

[na-am]

sorry for the late reply
I connected all function nodes to one rate limit node (5 messages per second) and then to the pixoo-text node. That solved the problem with the "socket hang up" errors

thx
na-am