-
Notifications
You must be signed in to change notification settings - Fork 111
Description
nodejs-poolController Version/commit
8.01
nodejs-poolController-dashPanel Version/commit
8.0.0
relayEquipmentManager Version/commit
No response
Node Version
No response
Platform
No response
RS485 Adapter
No response
Are you using Docker?
- Yes.
OCP
Intellicenter i5PS - 1.064
Pump(s)
No response
Chlorinator(s)
No response
What steps will reproduce the bug?
Occasionally, when you make any changes to the heater set point or heater mode, I get a communication timeout error, after which this module no longer works until nodejsPC is restarted (dsahPanel can stay running). Unfortunately (or fortunately), it only happens about once a week during normal use, so it's hard to capture a replay of it because I haven't noticed any patterns for when I might be causing it. It's not just if I turn the spa on and adjust features, for instance. It last happened with me simply changing the Set Temp while the heater wasn't even on.
What happens?
ApiError: Message aborted after 3 attempt(s): 165,1,15,33,168,41,0,0,18,1,0,0,0,0,0,0,0,0,0,0,176,89,27,110,3,0,0,88,100,94,100,1,1,0,0,15,0,1,0,100,0,0,0,0,0,0,0,5,67
at RS485Port.writeMessage (/home/admin/nodejs-poolController/controller/comms/Comms.ts:1010:31)
at RS485Port.processWaitPacket (/home/admin/nodejs-poolController/controller/comms/Comms.ts:946:22)
at RS485Port.processOutboundPackets (/home/admin/nodejs-poolController/controller/comms/Comms.ts:954:19)
at RS485Port.processPackets (/home/admin/nodejs-poolController/controller/comms/Comms.ts:936:14)
at Immediate._onImmediate (/home/admin/nodejs-poolController/controller/comms/Comms.ts:896:114)
at processImmediate (node:internal/timers:466:21)
What should have happened?
It doesn't change temp or heat mode, and then nodejs remains stuck where those things can no longer be changed. Everything else still works as normal.
Additional information
No response