Another option now is to use "DB Browser for SQLite". it can be downloaded from sqlitebrowser.org. You can export the device history data from the backup database to excel, modify the idx and import it into the current database (stop domoticz first!). The data is in the table Calendar_Meter.

Then create a new dummy device and do the transfer/merge.
Make a backup before you start the transfer/merge!!!!

That could be the right direction to create a new similar device and the use the command option --transfer-old=idx --transfer-new=idx Was it already a dummy device in the past or related to a normal hardware gateway? Because when connected to an existing hardware gateway it could automatically be ...

If you know the device type of the device that misses data you can determine what the table is you need to merge.
Is the device completely gone or just some historic data?
Because when the device is completely gone you have a bigger issue.

See the database merge tool mentioned in this topic: viewtopic.php?p=312243#p312243

What if you temporarily remove the linebreak in the text?
What if you temporarily remove the icon change in the script?

Perhaps better do discuss this in a new topic. But dzvents logging should work. For test you can use the logging template script that is available when creating a new dzvents script from the event script editor. See also for example viewtopic.php?p=325700#p325700

Make use of the dzvents asynchronous openURL function.
wiki: https://wiki.domoticz.com/DzVents:_next ... P_requests
example: viewtopic.php?p=319573#p319573

Clear, lets wait for FlyingDomoticz if he nows a rule for

If the rssi element in the json contains a value, the tracker is present (On). If rssi is missing from the message, the tracker is not present (Off).

Ambientweather-F007TH-2-154 seems to be the unique ID string like 0x00158d0004a98668 for zigbee2mqtt.

The +/+ issue was already fixed in 2023 with PR https://github.com/domoticz/domoticz/pull/5548

First of all, thanks for this great plugin. It's a Swiss army knife. I'm trying to implement a bluetooth (BLE) tracker as a presence tracker in Domoticz with the TheengsGateway as the intermediary. These trackers don't provide an on/off value, but instead just the rssi value. If the rssi element in ...

Yes it is the Unique ID you have to look at But what is the logic behind it? How should that unique ID look like to get Domoticz combine the Temp+HUM sensor? When I look at these 2 unique ID's, what is wrong with it? "uniq_id":"Ambientweather-F007TH-2-154-temperature_C" "uniq_id":"Ambientweather ...

I see a unique_id in the config topic payload that is made up like ID_type_gateway eg "unique_id":"0x00158d0004a98668_humidity_zigbee2mqtt" and "unique_id":"0x00158d0004a98668_temperature_zigbee2mqtt" Yours is ID-type (so no underscore) "uniq_id":"Ambientweather-F007TH-2-154-temperature_C" and "uniq ...

From this discussion it could be the Openhab auto Discovery setting as there is a "| is defined" in the value template definition. It could be Domoticz is failing on this. https://forum.domoticz.com/viewtopic.php?p=297743 If this also is not helping please create a GitHub issue with all the ...

On what Domoticz version are you running? As it should create combined temp/Hum devices on 2025 stable Domoticz.

Should already be fixed in latest 2025.1 beta
https://github.com/domoticz/domoticz/issues/6341

See for example the wiki page https://wiki.domoticz.com/MQTT_AD_Report_Problems how to find and copy MQTT Autodiscover config topics.

There should be a config topic, or multiple config topics in the MQTT homeassistant folder for this device. These config topic decides what devices are created.
Can you post those config topics?

You have run the following command while installing docker (using the docker wiki)? Edit: and also post your docker-compose.yml file.

Edit2: moved this to a separate topic.

To test, what happens if you do not use customstart.sh.
It should start. Then login to the container and run apt-get update ? Will the update also not continue?