Replies: 3 comments 24 replies
-
my goal would be to have generic, small footprint UI support which can can be dropped in as a library or component, not another tasmota or espeasy let's assume the whole config can be mapped onto a JSON file which is either onboard in nvs or fetched on startup, which includes broker, credentials etc looking at the broker->UI path I'd see:
1+2 are easy
assume I want to associate "tempc" with a UI label something like JSONata expressions would be cool but that's from nodejs land and not c++ embedding berry would be an option btw I'd try to keep those parts esp-unaware to the extent possible because they are generic what do you think? |
Beta Was this translation helpful? Give feedback.
-
@sukesh-ak I've been playing with integrating PicoMQTT into my playground found it to work nicely as a broker fed both with OMG and esp32-ble2mqtt I think broker + UI is an interesting combination as it can get rid of an external broker in many cases PicoMQTT is right now MQTT-over-TCP only but should sport Websockets later this spring - can then serve web MQTT clients + publishers as well ok, it's an Arduino component and as such probably not to your liking, but it might serve as a blueprint for an ESP-IDF component |
Beta Was this translation helpful? Give feedback.
-
meanwhile, on the embedded MQTT broker front: PicoMQTT now also supports MQTT-over-Websockets, opening the path to a web client with say MQTT.js or paho-mqtt |
Beta Was this translation helpful? Give feedback.
-
Lets discuss the requirements for a Simple MQTT Client UI for ESP32-XX Display devices
@mhaberler
Beta Was this translation helpful? Give feedback.
All reactions