I just buy a Heltun Thermostat HE-TH01. (If i well understand, it succeed HE-ZW-THERM-FL2).
When I include it, it is recognize as HE-ZW-THERM-FL2, but parameters are different and I can’t configure it properly.
I haven’t yet experienced adding a device (moreover a new version of device) in the database and by reading the User Guide… I will need support and/or explanation
Adding a new version of an existing device
If you have a different version of a device in the database, before adding another entry to the database, check that the association group configuration, parameters, and channels are the same. If they are, then it is only needed to update the device IDs of the existing device. If there is a new version required because the above data has changed, then first edit the exiting devices versions so that it does not conflict with the new device, then you can add the new device.
Before adding the new version (ie uploading the XML), change the type/id to a random number. This avoids any consistency issues when importing into the database. After the file is imported, change the type/id back, and set the firmware versions appropriately.
I have already try to create a new device in DB using the xml file, but it failed because of the already existing device (thanks @chris). If I well understand, we have to update the existing device so that it won’t conflict with the new one… but what we have to change ?
We shouldn’t do that unless you are really sure it is not also used with the old version? If not, we have now made a hole where some devices will no longer be detected. If you’re sure these IDs are not used on the older device, then not problem.
I guess we can leave it open until the new device is ready, which probably will only be a few days. Then we need to decide as we will either need to adjust version numbers, or manufacturer IDs, or both…
If we think that the current manufacturer ID should not be on the old device and was entered by mistake, then we should remove it and leave both devices versions set to the maximum numbers.
if we think that there are older devices with the same manufacturer IDs, then we should leave it set in both devices, but set the version ranges appropriately.
If you think it’s likely that the information was set incorrectly, then I’m happy to remove it, and leave the version range maxed out on both. I do agree that this seems most likely given the information from @dirandad that the hardware is also quite different…
Well, I have updated the device on the DB. It is still in modify state.
I have :
Update Association : There was difference from old device
Update parameters : Should be ok, but as there is a lot of parameters, an external control may be good. There is also a lot of differences from old device
Update endpoints : Well, here I’m not confident. I’m not sure if initials endpoints came from my xml, or the old device (as this new device was created by @chris from old device) . All endpoints can be found in the documentation and I have update version. I haven’t change channel. So, if somebody can control these endpoints before I change the status of the device ?
It’s a Teams work !
I haven’t made any change to the old device, only on the new one. And I haven’t notice any suspect change in this device. @chris, how can we confirm endpoints list of the new device ? Is there a compare tool to see if the xml file match the DB ?
And another question, is possible to test the device declared on the DB that is still in modify status in my openhab installation where I can made test with the real device ?