lux firmware continually disconnects

[vnprc]

this miner continually connects and disconnects, indicating incompatibility between lux firmware and the translator proxy software

2025-09-26T17:30:50.550615Z  INFO translator_sv2::lib::downstream_sv1::downstream: PROXY SERVER - ACCEPTING FROM DOWNSTREAM: REDACTED
2025-09-26T17:30:50.550680Z  INFO translator_sv2::lib::downstream_sv1::downstream: 📋 Registered miner 359 from REDACTED with ID 359
2025-09-26T17:30:50.558606Z  INFO translator_sv2::lib::downstream_sv1::downstream: Down: Configuring
2025-09-26T17:30:50.697202Z  INFO translator_sv2::lib::downstream_sv1::downstream: Down: Subscribing
2025-09-26T17:30:50.836650Z  INFO translator_sv2::lib::downstream_sv1::downstream: Down: Authorizing worker: m0ntan1
2025-09-26T17:30:51.686584Z ERROR translator_sv2::lib::status: Error: Io(Custom { kind: ConnectionAborted, error: "Connection closed by client" })
2025-09-26T17:30:51.686704Z  INFO translator_sv2::lib::downstream_sv1::downstream: 📤 Removed miner 359 from tracker
2025-09-26T17:30:51.686716Z  WARN translator_sv2::lib::downstream_sv1::downstream: Downstream: Shutting down sv1 downstream reader
2025-09-26T17:30:51.686746Z  WARN translator_sv2::lib::downstream_sv1::downstream: Downstream: Shutting down sv1 downstream job notifier for REDACTED
2025-09-26T17:30:51.686771Z ERROR translator_sv2::lib::status: Error: ChannelErrorReceiver(RecvError)
2025-09-26T17:30:51.686784Z  WARN translator_sv2::lib::downstream_sv1::downstream: Downstream: Shutting down sv1 downstream writer: REDACTED
2025-09-26T17:30:51.686924Z  INFO translator_sv2::lib: HEALTHY message: I/O error: `Custom { kind: ConnectionAborted, error: "Connection closed by client" }
2025-09-26T17:30:51.686938Z  INFO translator_sv2::lib: HEALTHY message: Channel receive error: `RecvError`

[vnprc]

[vnprc]

[vnprc]

I also received anecdotal evidence that BraiinsOS displays the same behavior. I just completed a migration to SRI 1.5.0 and tested it locally. My BraiinsOS miner still displays this behavior.

Ugh! I was hoping the translator rewrite would resolve this issue. 🤦