I'm missing more events like burnerhours/starts etc. It would be nice if OTGW monitor would post every message (with a changed value) to mqtt. I tried to dig into the source code and i'm having trouble to figure it out. I think it has to do with the $signals object not containing all data items. But not familiair with the language and build environment.
# Publish all known persistent parameters dict for {key args} $signals { if {[llength $args] == 0} continue set param [string tolower $key] if {[info exists gui($param)]} { mqttsignal $param $gui($param) } }
timoline wrote:I'm waiting for a year now.....but I still hope it will be implemented eventually...
I admire your patience to wait a year for someone else to do something for you. Of course you could also have spent a rainy afternoon to figure out how to do it yourself.
This is nice, this will save me the effort to extract this data from the otgw by hand! I've been able to compile the updated sources from Github into a binary that runs on my orange-pi otgw, and I've got several new topics available in my MQTT broker: https://imgur.com/a/Ej3oc8U