search

samuelventura / athasha

Automation Now
MIT License
0 stars 0 forks source link

Laurel devices may fail to reconnect after sudden disconnects #71

Open samuelventura opened 2 years ago

samuelventura commented 2 years ago
samuelventura commented 2 years ago

Two failure modes have been identified:

  1. Pressing "Save & Enable" from editor make the meter echo back the request package overlapped over the normal response makeing the CRC mismatch. This was solved by inserting a 100ms delay between connect and first command. A 10ms seems to work equally well.
  2. Connecting to a meter with an active connection puts the meter in an state that timeouts any further connection attemps until not connection is attempted for several seconds. Then it allows connections again. This is unresolved, severe, but not frequent. The 4-5 the runner takes to restart are not enough to clear the condition.
samuelventura commented 2 years ago

I just saw a case of the second mode of failure where it reconnected by itself after a couple attempts. Great!

samuelventura commented 2 years ago

I replicated the secode failure mode yesterday night. I created a couple of laurel items in different machines, enabled the first, then the second which failed, disable the first, then the second took several reconnections but managed consistently to reconnect after a while.