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

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 ...

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

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 ...

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): {"availability_topic": "ecowitt2mqtt/sensor ...

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 ...

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 ...

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 ...

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 ...

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.

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 ...

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 ...