deggle
commented
3 years ago Firstly, the client ID should absolutely be unique by default, maybe postfix the MAC address on it or something. Ideally the topic would be too, but that may be less ideal for some new and single device users.
Regarding the config, I agree this would be useful - to be able to collect the current config in JSON from a REST endpoint and post a replacement (full or partial) config to REST or MQTT.
I'd like to be able to switch the dimming/screensaver behaviour at night and this would facilitate that. So hopefully this is something that can be done?
It would be extremely useful for deployments, if there were a REST endpoint or MQTT topic for pulling the current configuration, and pushing a new configuration to the wallpanels. Additionally (per the documentation), it would also be useful if the MQTT client name were unique (eg, wallpanel-) or something out of the box.
Likely the best implementation via MQTT would be to publish a topic to set config on a uniquely named wallpanel instance (and not broadcast to all).
I have a number of panels in my home configuration, and it would help greatly if I could push updates from my server directly to all. I'd like to write a backend module that would poll the configs, maintain a database of the settings, and allow changes to be pushed as needed.