ok, i’ve been doing quite a bit of tinkering here, and i’m getting a little discouraged. I am hoping that this is my own lack of understanding of the software stack. So I’m looking for a little guidance.
I am on the v1.1 release of the Hestia One software, because 1.2 was listed as dev, and I wasn’t sure if that was in fact OK for “production” use. Let me know if I should in fact be on 1.2.
Task 1. is to figure out how to rename the topics that Hestia uses in mqtt. What I want to do is simply take my hestia and make its topic tree look more like ‘hestia/testtherm/’ testtherm is just a stand in name im using to identify this thermostat for now, later that might look like ‘hestia/zone1/’ or ‘hestia/livingroom/’. I am trying to do this locally without the HA integration yet, I figure that’ll come once I get this part worked out.
As i understand it, the local mqtt broker is mosquitto, and the configuration of the mqtt service is prety simple, and its all in /etc/mosquitto. I havent really touched that much yet.
I have found two components that refer to the ‘hestia/local’ topics, those are /etc/openhab/things/default.things, where all of the topics for various reads/writes happen, and the UI that displays on the touch panel, in /home/pi/scripts/oneui/js. The files for the UI are really hard to sift through though, and it makes me wonder if they were not written by a human, and are instead auto-generated somehow?
Editing these topics in the default.things and then watching mqtt explorer after restarting the thermostat, i see that hestia/testtherm gets populated with topics! but making the same edits in the js files for the UI doesnt seem to work out quite as well. At this point my display shows 0 degrees, 0 humidity, the three icons for heating, cooling, and fan are not even present, and where you;d set the temperature just says OFF.
Task 2. of course, is going to be bridging mqtt, or re-pointing it to my HA mqtt broker. I did attempt the bridge once, and it didn’t go so well, but I intent to re-try that once I’ve got these topic names worked out. I also tried just pointing the ‘localhost’ entries in the two files mentioned above, for the broker host, to my mqtt broker, and that at least partially worked, the hestia started populating the remote mqtt broker instead of its local one, but I had the same local display problem mentioned in task1.
so, both tasks are currently related to MQTT, can someone let me know if editing default.things, and the js files in /home/pi/scripts/oneui is the right way to make the changes i;m looking to make to the topic names?
Thanks! I feel like i’m close to getting this working. I need to tackle wiring it to my heating system next. My Thermostats are 2-wire… Sigh… So that’ll be another challenge, but I want to get this piece worked out before I tackle that as its going to mean wiring changes it seems.