Is there any way to run the MQTT keep alive on the CCGX itself, I can't find mosquitto_do on the CCGX to do?:
while :; do mosquitto_pub -m '' -t 'R/e0ff50a097c0/system/0/Serial'; sleep 5; done
asked
MQTT broker keep-alive on CCGX
Would you mind sharing how you got the Hubitat to talk to the Color Control? I'm trying to figure out the same set up right now for my RV.
Hi Elvis,
rather than a bash script you could make a small Python script to do that?
or use mosquitto-pub ? (my experience with mqtt is limited).
and you could check the available opkg-es to see if mosquitto is available to be installed (I’m not near a gx device myself now, so havent checked).
If you can install mosquitto_pub you can run it, sure. However, you're only running this if you have an external consumer, and I found it easier to set up the polling (also via mosquitto_pub) on the other machine instead.
Making changes to Venus OS that survive updates is something I didn't want to use precious mental space learning.
I've got an external consumer but it's limited, it seems, in being able to send the keep-alive (it's a Hubitat Home Automation hub) hence wanting to eliminate the 3rd piece of kit (that also needs to be powered of course and is an additional point of failure) just to send a keep-alive.
I was also hoping that mosquitto_pub may have been installed somewhere on the CCGX (or another mechanism to send the keep-alive/eliminate it as needed) to avoid having to work out how to let it survive an update as well! ;-)
Yeah, but if your HA hub or whatever "fails," then there is no sink for the MQTT anyway, so... isn't it the same result? System down?
I agree it would be nice to just have a switch in the UI that kicks off a process that keeps it alive permanently, though.
In theory, an embedded system like the Hub will be more stable than a Pi.
And in practice, adding a Pi is not going to make the Hubitat Hub more stable.
