7 Commits

Author SHA1 Message Date
peri4 afb4ae8126 MQTT ready to use
change subscription logic - now keep subscriptions independently from connecting state. No unregisters on disconnect, but resubscriptions on connect. So one-time subscription on app start and just connect() on lost connection - all subscriptions keeps
2026-05-29 09:56:29 +03:00
peri4 38d09e272c MQTT seems to work
1. subscribe now similar to HTTP server, with lambda
 2. subscribe topic syntax support all HTTP features as path arguments and wildcards
 3. event received() changed to receivedUnhandled() for unhandled messages (should never be called in proper work)
 4. internal logic got more complicated, several endpoints may be serviced by single MQTT topic, so nested Map used
2026-05-28 20:26:49 +03:00
peri4 aadf3375a6 PIMQTT::Message now Const & Mutable (as in PIHTTP) 2026-03-26 16:50:55 +03:00
peri4 089e241a67 migrate to PIThreadPoolWorker 2026-03-26 13:28:34 +03:00
peri4 c05fe46d04 pimqttclient before migrate to threadpoolworker 2026-03-26 13:06:57 +03:00
peri4 6a6cfe1efe Merge branch 'master' into mqtt_client 2026-03-26 12:57:03 +03:00
peri4 feb86b15f8 start mqtt client (based on paho.mqtt.c), basically works 2026-03-13 23:56:55 +03:00