Ecowitt: Temp + Humidity send to wrong sensor after initially being send to correct one

[igntion]

I have a Froggit GW2000 weatherstation (PWS). It is connected via Ecowitt2MQTT to a Mosquito server and with the "MQTT Auto Discovery from LAN" connected to Domoticz. All is working fine except the 2 sensors "Temp Binnen" and "GW2000 Binnen".
When I restart the MQTT AD from LAN (press update on the hardware page) the temperature (tempin) and humidity (humidityin) values from the GW2000 gateway are correctly send to the right sensor "Temp Binnen" and "GW2000 Binnen". But all it's values thereafter are wrongly send to the sensor "GW2000 Buiten". Straight thereafter "GW2000 Buiten" receives it's correct values (temp & humidity), so "GW2000 Buiten" is then correct again. But "Temp Binnen" and "GW2000 Binnen" are not updated anymore. it looks like they are not receiving data anymore.

After pressing Update journalctl shows (info edited):

Oct 24 11:36:06 domoticz domoticz[352019]: 2023-10-24 11:36:06.881 Status: Ecowitt2mqtt: discovered: GW2000/runtime (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_runtime)
Oct 24 11:36:06 domoticz ecowitt2mqtt[347134]: 2023-10-24 11:36:06,990 | INFO | Published to Home Assistant MQTT Discovery
Oct 24 11:36:07 domoticz domoticz[352019]: 2023-10-24 11:36:07.198 Ecowitt2mqtt: General/Custom Sensor (runtime)
Oct 24 11:36:07 domoticz domoticz[352019]: 2023-10-24 11:36:07.302 Status: Ecowitt2mqtt: discovered: GW2000/tempin (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_tempin)
Oct 24 11:36:07 domoticz domoticz[352019]: 2023-10-24 11:36:07.608 Ecowitt2mqtt: Temp/THR128/138, THC138 (Temp Binnen)
Oct 24 11:36:07 domoticz domoticz[352019]: 2023-10-24 11:36:07.711 Status: Ecowitt2mqtt: discovered: GW2000/humidityin (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_humidityin)
Oct 24 11:36:08 domoticz domoticz[352019]: 2023-10-24 11:36:08.026 Ecowitt2mqtt: Temp + Humidity/THGN122/123/132, THGR122/228/238/268 (GW2000 Binnen)
Oct 24 11:36:08 domoticz domoticz[352019]: 2023-10-24 11:36:08.130 Status: Ecowitt2mqtt: discovered: GW2000/baromrel (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_baromrel)
Oct 24 11:36:08 domoticz domoticz[352019]: 2023-10-24 11:36:08.436 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)
Oct 24 11:36:08 domoticz domoticz[352019]: 2023-10-24 11:36:08.540 Status: Ecowitt2mqtt: discovered: GW2000/baromabs (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_baromabs)
Oct 24 11:36:08 domoticz domoticz[352019]: 2023-10-24 11:36:08.880 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)
Oct 24 11:36:09 domoticz domoticz[352019]: 2023-10-24 11:36:09.009 Status: Ecowitt2mqtt: discovered: GW2000/temp (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_temp)
Oct 24 11:36:09 domoticz domoticz[352019]: 2023-10-24 11:36:09.314 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)
Oct 24 11:36:09 domoticz domoticz[352019]: 2023-10-24 11:36:09.418 Status: Ecowitt2mqtt: discovered: GW2000/humidity (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_humidity)
Oct 24 11:36:09 domoticz domoticz[352019]: 2023-10-24 11:36:09.723 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)

Then one minute later it receives an update:

Oct 24 11:37:07 domoticz domoticz[352019]: 2023-10-24 11:37:07.967 Status: Ecowitt2mqtt: discovered: GW2000/runtime (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_runtime)
Oct 24 11:37:07 domoticz ecowitt2mqtt[347134]: 2023-10-24 11:37:07,993 | INFO | Published to Home Assistant MQTT Discovery
Oct 24 11:37:08 domoticz domoticz[352019]: 2023-10-24 11:37:08.304 Ecowitt2mqtt: General/Custom Sensor (runtime)
Oct 24 11:37:08 domoticz domoticz[352019]: 2023-10-24 11:37:08.412 Status: Ecowitt2mqtt: discovered: GW2000/tempin (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_tempin)
Oct 24 11:37:08 domoticz domoticz[352019]: 2023-10-24 11:37:08.755 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)
Oct 24 11:37:08 domoticz domoticz[352019]: 2023-10-24 11:37:08.868 Status: Ecowitt2mqtt: discovered: GW2000/humidityin (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_humidityin)
Oct 24 11:37:09 domoticz domoticz[352019]: 2023-10-24 11:37:09.184 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)
Oct 24 11:37:09 domoticz domoticz[352019]: 2023-10-24 11:37:09.295 Status: Ecowitt2mqtt: discovered: GW2000/baromrel (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_baromrel)
Oct 24 11:37:09 domoticz domoticz[352019]: 2023-10-24 11:37:09.601 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)
Oct 24 11:37:09 domoticz domoticz[352019]: 2023-10-24 11:37:09.709 Status: Ecowitt2mqtt: discovered: GW2000/baromabs (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_baromabs)
Oct 24 11:37:10 domoticz domoticz[352019]: 2023-10-24 11:37:10.060 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)
Oct 24 11:37:10 domoticz domoticz[352019]: 2023-10-24 11:37:10.165 Status: Ecowitt2mqtt: discovered: GW2000/temp (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_temp)
Oct 24 11:37:10 domoticz domoticz[352019]: 2023-10-24 11:37:10.505 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)
Oct 24 11:37:10 domoticz domoticz[352019]: 2023-10-24 11:37:10.610 Status: Ecowitt2mqtt: discovered: GW2000/humidity (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_humidity)
Oct 24 11:37:10 domoticz domoticz[352019]: 2023-10-24 11:37:10.915 Ecowitt2mqtt: Temp + Humidity + Baro/Weather Station (GW2000 Buiten)


I was wondering what I could do to get the tempin & humidityin values to the right sensor (Temp Binnen & GW2000 Binnen)?

Configuration:
Weather Station: Froggit GW-2000 + WS-90
Ecowitt2MQTT version 2023.08.0
Mosquitto version 2.0.11
Domoticz Version: 2023.2
dzVents Version: 3.1.8
Python Version: 3.11.2

[waltervl]

Better check the MQTT messages (config and state) with MQTT explorer, looks like some Device ID or configuration in Ecowitt2mqtt is incorrect.
eg
homeassistant/sensor/*/config

and the content of the asscociated state topics that are mentioned in the config topic.

[igntion]

Thanks for the quick reply!

I am not familiar with MQTT explorer nor with mosquito_sub and I am also not at home at the moment but I did check from a distance the state of the 2 temp. sensors (tempin & temp) of the GW2000.
The command mosquitto_sub -t \ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/tempin/state gives:
17.1
17.2
while the shown sensor in domoticz stays at 17.5
The other sensor returns with
mosquitto_sub -t \ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/temp/state
11.199999999999998
11.300000000000002
and it updates the shown associated sensor.

Is this provides already any direction?

I can provide more logs, eg from mqtt_ad_record.sh from domoticz if that is needed.

[igntion]

Quick update: I am able to approach the broker from the outside world with mqtt-explorer. I don't see anything in particular that points to a malfunctioning broker or malformed mqtt messages.

[waltervl]

Perhaps remove all your Ecowitt devices from Domoticz and have them rediscovered again. I myself do not use MQTT so cannot help you directly.

Domoticz uses the config topics to create the devices and the state topics to update them. Perhaps Domoticz gets confused by using the same names or something.

[igntion]

Removing and rediscover the devices will also remove their logs. That is not a big deal but that is why I only removed the three sensors involved for the moment. One sensor gets recreated straight after I removed it, that is the outside sensor (unique_id's without the "in" in the end, eg. _temp, not _tempin). It also gets updated every minute (as configured). Once I update the MQTT AD Client Gateway on the Hardware page the other 2 are recreated, but are not updated afterwards. I had a look at the domoticz.db. I could see that the items of the IDX of the not updated sensors are stored with a correct value (every 5 min.). So I think the MQTT payloads send are correct and stored correctly in the database. I also removed any of these sensors from my blocky scripts, to prevent interference from that.
Question is where to look further now?

[waltervl]

You have to look at the connection between the MQTT messages and the Domoticz devices.
Also check for retained Ecowitt2MQTT config messages (with MQTT Explorer) as they could mix things up.
Did you change names/ids in the Ecowitt2MQTT configuration before or is it all default values?

[igntion]

Thanks for the replies!

You have to look at the connection between the MQTT messages and the Domoticz devices.

Sorry, how to do that? In the first post I showed part of the output of journatctl, eg:

Oct 24 11:36:07 domoticz domoticz[352019]: 2023-10-24 11:36:07.302 Status: Ecowitt2mqtt: discovered: GW2000/tempin (unique_id: BDAFCCBA2F5CA4FDC76E19C8A869845A_tempin)

I had the impression that that showed that domoticz received this message from mqtt (mosquitto). What can I do to check the connection between the mqtt message and domoticz device?

Also check for retained Ecowitt2MQTT config messages (with MQTT Explorer) as they could mix things up.

There are none.

Did you change names/ids in the Ecowitt2MQTT configuration before or is it all default values?

I don't think anything is changed except the discovery-prefix, Ecowitt2mqtt is started with systemd:

Code: Select all

ExecStart=ecowitt2mqtt --mqtt-broker=localhost --port 82 --hass-discovery --hass-discovery-prefix ecowitt2mqtt --disable-calculated-data --input-unit-system imperial --output-unit-system metric

[waltervl]

Look in MQTT explorer. in the folder ecowitt2mqtt the config devices are shown. In those config topics there should be reference to state topics.

Did you change names in Ecowitt of the temperature sensor while already connected to Dmoticz? eg the tempin or temp buiten? Somehow Domoticz is mixing things up due to some configuration issues.

The domoticz log file is not fully logging the mqtt messages.

But here my knowledge ends. Hopefully somebody else can help you....

[igntion]

Thanks for all your help!

I am still busy finding out what's going wrong. The name of the sensors were changed in Domoticz, not in Ecowitt or elsewhere. I did a firmware-update of the GW2000 gateway lately but I am not aware if the problem was there already or happened afterwards. The reference to the state topic looks normal to me:

Code: Select all

{"availability_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/tempin/availability", "device": {"identifiers": ["BDAFCCBA2F5CA4FDC76E19C8A869845A"], "manufacturer": "Ecowitt", "model": "GW2000A", "name": "GW2000", "sw_version": "GW2000A_V3.0.8"}, "json_attributes_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/tempin/attributes", "name": "tempin", "qos": 1, "retain": false, "state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/tempin/state", "unique_id": "BDAFCCBA2F5CA4FDC76E19C8A869845A_tempin", "unit_of_measurement": "\u00b0C", "device_class": "temperature", "state_class": "measurement"}

And the same for the humidity:

Code: Select all

"state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidityin/state", 

The state of the sensor gets updated every minute and the sensor that is updated gets first an update of _tempin & _humidityin, you can see it changed if you watch at the right time. Within a second it then changes to what it supposed to be, _temp & _humidity.

[waltervl]

Please compare these topics with the other temperature device buiten.

[igntion]

This is not true:

I had a look at the domoticz.db. I could see that the items of the IDX of the not updated sensors are stored with a correct value (every 5 min.). So I think the MQTT payloads send are correct and stored correctly in the database

I had another look and compared mqtt values with the stored values and this is not correct! It just stores the last known values of the not updated sensors (again & again).

[waltervl]

Yes as Domoticz somehow gets confused. Please check the Mqtt messages!!!

[igntion]

Just for the completeness of it, I hope it is not too much, this are the config messages of the 3 domoticz sensors in MQTT-explorer:

tempin (was Temp Binnen but after removing at was auto-recreated as that and did not change the name):

Code: Select all

{"availability_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/tempin/availability", "device": {"identifiers": ["BDAFCCBA2F5CA4FDC76E19C8A869845A"], "manufacturer": "Ecowitt", "model": "GW2000A", "name": "GW2000", "sw_version": "GW2000A_V3.0.8"}, "json_attributes_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/tempin/attributes", "name": "tempin", "qos": 1, "retain": false,]"state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/tempin/state", "unique_id": "BDAFCCBA2F5CA4FDC76E19C8A869845A_tempin", "unit_of_measurement": "\u00b0C", "device_class": "temperature", "state_class": "measurement"}

In there: "state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/tempin/state"
In the explorer is also showsn: availability = online, attributes = {}, state = 15.2 (domoticz shows 15.8)

GW2000 (was GW2000 Binnen, same as above):

Code: Select all

{"availability_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidityin/availability", "device": {"identifiers": ["BDAFCCBA2F5CA4FDC76E19C8A869845A"], "manufacturer": "Ecowitt", "model": "GW2000A", "name": "GW2000", "sw_version": "GW2000A_V3.0.8"}, "json_attributes_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidityin/attributes", "name": "humidityin", "qos": 1, "retain": false, "state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidityin/state", "unique_id": "BDAFCCBA2F5CA4FDC76E19C8A869845A_humidityin", "unit_of_measurement": "%", "device_class": "humidity", "state_class": "measurement"}

Extracted from above: "state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidityin/state"
It shows: availability = online, attributes = {}, state = 72.0 (domoticz shows 71)

GW2000 (was GW2000 Buiten):

Code: Select all

{"availability_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/temp/availability", "device": {"identifiers": ["BDAFCCBA2F5CA4FDC76E19C8A869845A"], "manufacturer": "Ecowitt", "model": "GW2000A", "name": "GW2000", "sw_version": "GW2000A_V3.0.8"}, "json_attributes_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/temp/attributes", "name": "temp", "qos": 1, "retain": false, "state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/temp/state", "unique_id": "BDAFCCBA2F5CA4FDC76E19C8A869845A_temp", "unit_of_measurement": "\u00b0C", "device_class": "temperature", "state_class": "measurement"}

Code: Select all

{"availability_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidity/availability", "device": {"identifiers": ["BDAFCCBA2F5CA4FDC76E19C8A869845A"], "manufacturer": "Ecowitt", "model": "GW2000A", "name": "GW2000", "sw_version": "GW2000A_V3.0.8"}, "json_attributes_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidity/attributes", "name": "humidity", "qos": 1, "retain": false, "state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidity/state", "unique_id": "BDAFCCBA2F5CA4FDC76E19C8A869845A_humidity", "unit_of_measurement": "%", "device_class": "humidity", "state_class": "measurement"}

"state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/temp/state",
"state_topic": "ecowitt2mqtt/sensor/BDAFCCBA2F5CA4FDC76E19C8A869845A/humidity/state"
It shows :
availability = online, attributes = {}, state = 7.999999999 and
availability = online, attributes = {}, state = 99.0 as does the domoticz sensor.

[igntion]

I am still struggling with this issue. One thing that might point in the right direction:
I restarted ecowitt2mqtt with the retain option and updated the MQTT AD Hardware: the sensors on the temp. page get not updated.
I restarted ecowitt2mqtt without the retain option and updated the MQTT AD Hardware: the sensors get updated once (after deleting all retained mqtt-messages on Mosquitto). Is this a Domoticz issue or should I look for help somewhere else?

[waltervl]

It could perhaps be that in Domoticz name temp and tempin are not correctly being identified as separate devices.
Perhaps you could try latest Domoticz beta version to see if this issue is still present. There have been some changes to MQTT AD gateway in beta. If it continues I would create a GitHub issue with config and state topics so the developer can reproduce your issue.

[igntion]

Thanks waltervl, I will change to beta in about 2/3 days when I have time..

[igntion]

I have changed now to the latest Beta, Version: 2023.2 (build 15636). Unfortunately the issue is still there..

It could perhaps be that in Domoticz name temp and tempin are not correctly being identified as separate devices.

When I restart the MQTT Auto Discovery Client Gateway with LAN interface initially the temp/humidity sensors are updated correctly, but only once. Thereafter the issue returns (this is the same behaviour as in the stable version).

If it continues I would create a GitHub issue with config and state topics so the developer can reproduce your issue.

I will do my best to create it, hopefully it will resolve then.

[igntion]

For people who read this now, the problem is solved in Version: 2023.2 (build 15643)

[waltervl]

Great!