From the FLM v2.4.4 source code of /usr/sbin/wwd.lua I see that there should be a MQTT topic MOSQ_TOPIC_SENSOR_CONFIG, set to "/device/flukso-id/config/sensor", which should provide the configuration parameters of all FLM attached sensors. Also this message should be retained for any newly subscribed MQTT client.
Nevertheless, a mosquitto_sub -h host -v -t /device/#, nor a generic /# receives such a topic's payload (which in principle should work as, for example "old" gauge and counter data is resent".
What is missing?
Issue solved - the flukso-daemon requires a tiny addition to gain the capability to also publish the FLM's configuration data as an own MQTT topic; see below.
| Attachment | Size |
|---|---|
| FLMlocalGauge.png | 172.59 KB |
After a reboot following topics are published:
No /device/%s/config/sensor, and also the /d/device I would question...
After a "sensor save" in the web interface also just above information is passed on...
As I just see, there is some other tmpo topic
which also looks rather weird.
Software archaeology unearthed: The config-topic is provided just by the new ww-daemon that seems to be started only for a FLM02W...
The result
publishes only on topics /sensor/#/gauge and /sensor/#/counter as the flukso-daemon does not contain any configuration publishing - so I stop my investigations for now and cannot hold off some irritation.
<eot>With a few lines added to the flukso daemon lua the configuration may also be obtained from an "old" Fluksometer via MQTT. Now I can obtain gauges with real names (and potentially a lot more).
Help yourself with https://github.com/gebhardm/flmlocal/tree/develop or https://github.com/gebhardm/flmlocal/releases/tag/AngularV1.1 AT OWN RISK - slowly but steadily I understand how the FLM works...
The corresponding commit is https://github.com/flukso/flm02/commit/1e2a0b52d9349c6a93744681e60153c46... - it may also be used for manual update (I still hope that Bart will merge this already in v246 as it is really, really helpful)
Sensor config publishing is now centralized in tmpod. See commit ddf49f.
Perfect - thanks; now the TMPO-daemon just needs to publish the query topics and I am happy...