Home Automation Domotica Forum Europe, Bwired Forum

Just to be clear: It is possible to upgrade the firmware on a PIC16F88 using ESP firmware 0.9.5, but only via the built-in upgrade mechanism. Upgrading the PIC firmware using OTmonitor via port 25238 does not work. So I advise to use the upgrade feature of the ESP firmware. Then you don't have to disconnect the OTGW to upgrade the PIC firmware to 5.7.

I used the old Nodoshop software together with the old OTGW having an ESP8266.
I could set an override temp from Domoticz easily.

After I flashed your software ( amazing job) I get all devices available in Domoticz but cannot set een overrule temp.
Mqtt explorer reflects a set command but OTMONITOR does not receives this data.
Note that from Otmonitor I can, as always, set an override temp.

Do I overlook a setting in your software?

TIA
Bart

Please help me what am I doing wrong.
I download the whole package from https://github.com/rvdbreemen/OTGW-firmware
I'm trying to call it into the Arduino IDE environment. Which file should be called to manage the package as one, and should I make a firmware at the end? There are a few modifications I would like to try.

BartSr wrote: ↑Thu Oct 26, 2023 5:00 pm I used the old Nodoshop software together with the old OTGW having an ESP8266.
I could set an override temp from Domoticz easily.

After I flashed your software ( amazing job) I get all devices and site available in Domoticz but cannot set een overrule temp.
Mqtt explorer reflects a set command but OTMONITOR does not receives this data.
Note that from Otmonitor I can, as always, set an override temp.

Do I overlook a setting in your software?

TIA
Bart

Try checking the OTMonitor log files for errors when receiving data from MQTT. This may give you a clue as to what went wrong

HI, I wonder if anyone could advise, I'm probably missing something.

I have a gateway installed and using OTGW-firmware (version 0.10.3+e334c42) on an ESP device attached and for a couple of years it's been working fine. I've had it reporting to MQTT into Home Assistant and it's been great.

Recently I scrapped the MQTT server and built a new one, just to upgrade to MQTT v5 (from 3.1).

Once ready I removed the existing OTGW device from Home Assistant then connected OTGW-firmware via the ESP to the new MQTT server, but the OTGW device never appears in Home Assistant.

From what I can gather HA expects a config message on a homeassistant topic for autodiscovery, and monitoring this no message ever seems to be sent from OTGW-firmware.

To force a new autodiscovery message, I've tried rebooting the OTGW, tried changing the MQTT server ip, enabling and disabling MQTT in OTGW, power cycling the OTGW hardware, changing the MQTT Home Assistant prefix and changing it back, switching back to the old mqtt 3.1 server, all to no avail.

I'm not up on exactly what should and should not be happening for it to appear in HA, but it seems like OTGW is just never sending autodiscovery compatible messages so HA isn't picking it up. Everything else on my network seems to be sending autodiscovery and is being picked up with no issue, even when removing readding devices, which makes me think it's probably an OTGW-firmware related somehow.

I can log into the MQTT server and see all the data OTGW-firmware is sending when I subscribe to the OTGW topic so it's all connected and sending data about the boiler fine, I can also use the MQTT subscription option inside HA to view the same topic and it's all coming through fine there, it's just the autodiscovery message never seems to appear.

Anyone any ideas?

I guess it is possible I did upgrade to OTGW-firmware version to 10.3 during all this and that's introduced something but downgrading to 10.2 then 10 it still seems the same, no autodiscovery, nothing seems to be sent to the homeassistant topic.

I set my NodoShop Wifi OTGW up a couple of weeks ago, with Home Assistant. Although the OTGW wasn't auto-discovered in Home Assistant as an Integration, it did automatically appear as a Device in the MQTT integration.

Not sure if that helps you or not...

Cheers. It's the mqtt autodiscovery that doesn't seem to work.

The opentherm device should send out an mqtt message under the "homeassistant" topic containing details of each entity it reports, as I understand it this is required for Home Assistant to autodetect the device and its entities. Once discovered you can then enable those entities in HA and it will track the value mqtt messages for each entity.

HA just doesn't seem to discover the opentherm gateway, and it seems to be because OTGW never broadcasts it, I can't see any of the announce messages for OTGW on the homeassistant topic (I can see them for every other device I have).

I can see the OTGW values themsselves reporting to my MQTT server, ie the ongoing boiler temps and all that under the "OTGW" topic are all coming through, just never the config announcements that allow me to configure it in HA.