MQTT Channels are crossed up

[jkosharek]

Ben, playing with MQTT to get data from Dashbox to HA or maybe to EISY/IoX/PG3x and noticed that some of the channels are crossed up.
C1 name is pulling from what should be in T1 and T1 isn't pulling a name
V33 name is going to C33

The instructions on the 'MQTT Publisher\MQTT Publisher Steps' for #3 seems like it needs to be deleted because the menu to select channels is not there, or there is a bug that isn't displaying the MQTT settings I saw in someone else's screen shots.

Can the frequency be configured for how often topics are published or set to publish on any value change?

Screenshot 2023-11-19 at 5.59.36 PM.png (299.25 KiB) Viewed 5890 times

[jkosharek]

Ben, also can the MQTT be configured to send the info in JSON format?

[ben]

Frequency is not controllable, mixing a bunch of options was causing some conflict with data logging on the DashBox.

I suggest using packet forwarding and btmon.py if you want full control over frequency so the DashBox is just dumping the packet.

Ben, also can the MQTT be configured to send the info in JSON format?

Not currently.

[jkosharek]

Frequency is not controllable, mixing a bunch of options was causing some conflict with data logging on the DashBox.

I suggest using packet forwarding and btmon.py if you want full control over frequency so the DashBox is just dumping the packet.

Ben, also can the MQTT be configured to send the info in JSON format?

Not currently.

Will the MQTT topic channels/values being mixed be addressed?

So the btmon.py setup would be another Packet Forward in the Dashbox, any current setup info on btmon.py with dashbox?

[ben]

Frequency is not controllable, mixing a bunch of options was causing some conflict with data logging on the DashBox.

I suggest using packet forwarding and btmon.py if you want full control over frequency so the DashBox is just dumping the packet.

Ben, also can the MQTT be configured to send the info in JSON format?

Not currently.

Will the MQTT topic channels/values being mixed be addressed?

So the btmon.py setup would be another Packet Forward in the Dashbox, any current setup info on btmon.py with dashbox?

Looking into the ordering thru the DashBox. Added some sorting to the query but it's still a little weird.

Based on the btmon.py documentation it looks like you get this by default:

the voltage of the system:
<base_topic> /volts -> <volts-value>

for each energy channel:
<base_topic> /ch <channel-n> _w -> <power-value>
<base_topic> /ch <channel-n> _wh -> <energy-value>
<base_topic> /ch <channel-n> _dwh -> <delta-energy-value>

for each temperature channel:
<base_topic> /t <temperature-n> -> <temperature-value>

for each pulse channel:
<base_topic> /p <pulse-n> -> <pulse-count>

Or you can map what you want to be sent.