Closed KlausHans closed 10 months ago
"Error: Client Not Ready To Read At State init" means you inject a request while it is not ready and do the initializing of the client. You need some switch variable to give MQTT msg just to the client if it is ready to work.
This issue is stale because it has been open 60 days with no activity. It will be closed in 30 days, but can be saved by removing the stale label or commenting.
Which node-red-contrib-modbus version are you using?
"node-red-contrib-modbus": "5.25.0"
What happened?
I have a weird issue, that only happens after x amounts of deploying the flows. x is most often 3 from my observation. I have 3 Usb-Rs485 adapters on an usb hub connected to a Raspi. The adapters are defined in the modbus node via /dev/serial/by-id/ or /dev/serial/by-path. The error is "Error: Client Not Ready To Read At State init". If i unplug and then plug the usb hub where the adapters are connected to, everything works again flawless without end (as long as i don't deploy). Of course i can not unplug and plug the usb hub every ~3 deployments.
I am not really sure if this is an issue with the node though. I tried other usb hubs, but then the issues were even worse. Defining a startup or queue delay doesn't help.
Server
Modbus-Flex-Server Node (Please attach Script to the next section)
How can this be reproduced?
"Please attach relevant flows as a .json file. " Github wont let me. So here plain text:
What did you expect to happen?
No error appears after deploying.
Other Information
No response