maziggy a4fad2d2f5 fix(mqtt): fail-safe request topic subscription for ams_mapping capture (#405) ...

Some printer MQTT brokers (e.g. P1S) reject subscriptions to the request
topic by killing the TCP connection, causing a disconnect loop. The request
topic subscription for ams_mapping capture is now fail-safe with two
detection paths:

- SUBACK rejection: on_subscribe callback detects failure code 0x80
- Broker kills connection: on_disconnect detects disconnect within 10s of
  unconfirmed subscription attempt

After detection, the request topic is disabled for that printer and
reconnection succeeds with only the report topic. Printers that support
the request topic (e.g. X1E, H2D) get ams_mapping capture; printers that
don't (e.g. P1S) gracefully degrade to tray_now-based tracking.

2026-02-17 09:33:32 +01:00

..

app

fix(mqtt): fail-safe request topic subscription for ams_mapping capture (#405)

2026-02-17 09:33:32 +01:00

tests

fix(mqtt): fail-safe request topic subscription for ams_mapping capture (#405)

2026-02-17 09:33:32 +01:00

__init__.py

Added screenshots

2025-11-28 10:23:59 +01:00