I've recentlty bought a couple of Renkforce FT007TH sensors en they were working pretty ok. Some gaps in the readings, but nothing to bad.
Today I saw that one of te sensors wasn't giving a signal, although the red light flashed. I checked the AAA's and they were almost empty (in Domoticz they still reported as full). I changed the AAA's and there was stil no signal in Domoticz, until I looked at the Devices-menu.
There was a new ID (and idx) fot the same sensor.
Ofcourse the history is in the 'old' Device and not that it is a huge problem, I would like to keep history of the temperatures.
Does anybody else experience the same behaviour? and how can this be prevented, so that after a battery-change the sensor keeps the same ID.
FT007TH Temp and moister sensor history when getting a new ID Topic is solved
Moderator: leecollings
- waltervl
- Posts: 5859
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: FT007TH Temp and moister sensor history when getting a new ID
This is unfortunately the standard behavior of RF sensors (zigbee and zwave do not do this).
But you can merge the old data into the new device with the Domoticz replace function: https://wiki.domoticz.com/Managing_Devi ... ace_device
But you can merge the old data into the new device with the Domoticz replace function: https://wiki.domoticz.com/Managing_Devi ... ace_device
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Re: FT007TH Temp and moister sensor history when getting a new ID
thnx!
That is good enough, as it is not that often it needs to be done.
That is good enough, as it is not that often it needs to be done.
Who is online
Users browsing this forum: No registered users and 1 guest