andrew_j_w
andrew_j_w
About
- Username
- andrew_j_w
- Joined
- Visits
- 76
- Last Active
- Roles
- Member
Comments
-
Yay! So glad it’s working! I was very confused :-)
-
That should match the default topic name, if you pass —mqtt serverip I would expect it to work.
-
I think if you change DEFAULT_MQTT in arguments.py line 22 to your local server, and pass —topic SMART/HILD/+ it might work.
-
That line is ok. Triple quotes are a multi line string in Python. It’s closed on line 46. If it’s connecting to MQTT ok then it must be listening to the wrong topic. That’s handles in mqtt.py line 47. You probably want to experiment with different t…
-
Ah, I hadn’t planned for that use case. The topic names and message formats are different for cloud and local mqtt modes. It won’t work with cloud format via a local server. If you configure it to point to the cloud directly it should work.
-
That’s definitely good progress :-) I will have to test the bind parameter to make sure it works correctly. The metrics will return 404 until it receives some data. Are you able to confirm the Glow IHD is sending data to your mqtt server? Andrew
-
Sounds like you might have bigger docker issues then, not specifically glowprom. You want to try asking somewhere like Stack Overflow to see if they can help get docker working. Andrew
-
The bind address is where it exposes the metric, you then need to add a line to the prometheus configuration file to scrape it. You should be able to visit http://bindaddress:port/metrics in a web-browser to confirm it's working. In your prometheus.…
-
Yes, bind is ipaddress:port. I've not tested localhost, but it should work.
-
Thanks, I will see if I can workout how the error is being thrown and make it clearer. It just listens to everything under the glow/ topic, so it should pick everything up. Andrew
-
Ah, that's interesting. Does it print out a full traceback, including line numbers? I need that to be able to work out where the problem is. Andrew