Heltun HE-HT01 (zwave Thermostat)

Hello All.

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.

Is it possible to add HE-TH01 in the database ?

Documentation can be found here : https://drive.google.com/file/d/1CgqG39zl5MqTNhfqUAX1d5RbUB95EgPC/view

Thank you by advance

Sure, It is a community maintained database. Here is the guide.

Thank you for the answer,
I will create the device (when i will have the Create button :-))

I will give feedback here when it will be done.

Be sure to open a ticket there requesting database access.

Hi @dirandad

I’m not sure if we really need a new device entry for that.

I also have five of this Thermostats running. And I also have some params which I could not set yet.

The case is open at Heltun Support.
Could you tell which parameterss you have an issue with?

1 Like


Thanks for answer. By reading both documentation, it seems there is no doubt that we have 2 differents parameters sets for two differents (version of) device

doc of HE-TH01 (the one I have) zwave 700 chips (the new one): https://drive.google.com/file/d/1CgqG39zl5MqTNhfqUAX1d5RbUB95EgPC/view

doc of HE-ZW-THERM-FL2 (the one in Database) zwave 500 series (the old one) :

Hetltun support website where you will found both device :

In documents, you will notice that parameters lists is different:

first parameters of HE-ZW-THERM-FL2 :

first parameters of HE-TH01 :

First parameters of my device HE-TH01 reconized as HE-ZW-THERM-FL2 in openhab

So we can reconize value of a HE-TH01 parameters in the skin of HE-ZW-THERM-FL2.
For exemple parameter 15 is Floor temp Max (32°C) and not Floor temp Min as written in openhab.

Does it answer to your doubts ? :slight_smile:


Hi Adrien

The First device of Heltun was added by me. It was based on lended one from my distributer.

So let’s go on and add a second one. I will create a request against the database.
@chris Do I firstly need to adjust the device type as done earlier. Or can this be done after it?



I have the xml file for HE-TH01:
HE-HT01.xml (37.4 KB)

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 :slight_smile:

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 ?

Thanks for support.

I’ve created the new entry -:

Please update this.

Also, we need to update the old entry to fix the version numbers -:

I’d also prefer that if these two things are just different versions of the same device, that they had the same name and thing uid. Or has the manufacturer changed the name of the devices?

Thanks @chris

These two devices have the same function (Heating Thermostat), but use two different hardware and indeed, manufacturer has give two different references and identified them as different “model” :

Old (hardware 500 series) : HE-ZW-THERM-FL2 --> chosen as uid
New (hardware 700 series) : HE-TH01 --> should be chosen as uid

We are in the same case as Fibaro and FGS-222/FGS-223 where two device has been created in DB.


I have made the change to the older model and removed the device type which is used with the newer model.

1 Like

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.

Hi Chris

I’m pretty sure on it. But can further clarify with Heltun.

I actually have ordered the older Model and received the newer ones this year after waiting for about 1.5 years.
Maybe you can keep the change request open. Till I know it finally.


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…

@chris, @dirandad
Question submitted to Heltun support. Expecting answer in the next days.

EDIT 21.12.2020:

Dear Stefan,

You are right. There are no plans to use the device type 0004:0001 on the older models.

Best Regards
Heltun Support Team

1 Like

Well, I have updated the device on the DB. It is still in modify state.
I have :

  • Update overview
  • Update Attachment
  • 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 ?

Thank you

It appears 2 different user are working on this. We need to be careful here.

I don’t think so. I think @smhaller has modified the old version and @dirandad has modified the new version? At least that’s what I think is happening :slight_smile:

1 Like

It’s a Teams work ! :slight_smile:
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 ?


1 Like

Not supported, but in the past, some have tried this with OH2.

1 Like