This object is in archive! 
Eurotronic Comet radiator thermostat
Known
I have a Eurotronic Comet radiator thermostat included in my network for about 2 weeks now.
Basically is this device working fine, but the problem is that is goes offline randomly en it doesn't come back online anymore. When i remove- and reinstall the batteries it comes online.
Does anyone else have this device / problem? And what can i do about it? (I've already tried exclude/including near the zipabox serval times and set the wakeup time to the minimum of 4 min. but that doesn't solve the problem)
Can it be a firmware problem or is the device maybe not fully supported yet?
No connection
Real-time notifications may not work
Hi,
one of my customer is using it....so it seems to work
regards Helle
Hi,
one of my customer is using it....so it seems to work
regards Helle
same problem for me!
same problem for me!
Hello, I have sever of these and just adding to Zipatile. Before used VERA EDGE and had a option to change temp by setting it with +/- buttons. Now in zipatile it is 0-100%. Do you know how to change that?
Hello, I have sever of these and just adding to Zipatile. Before used VERA EDGE and had a option to change temp by setting it with +/- buttons. Now in zipatile it is 0-100%. Do you know how to change that?
Hi Sebastian, any chance to get full integration of this device in Zipabox/Zipatile?
Hi Sebastian, any chance to get full integration of this device in Zipabox/Zipatile?
I would pray for this too. I have 4 of those, winter is comming ...
I would pray for this too. I have 4 of those, winter is comming ...
Hi, I have just received mine..
The only fonction which is working for me by now is : off (and after manuel handling, it goes to default 22°)
I have set the wake up time to 5 minutes.
Still testing...
Hi, I have just received mine..
The only fonction which is working for me by now is : off (and after manuel handling, it goes to default 22°)
I have set the wake up time to 5 minutes.
Still testing...
Hi,
after testing, it doesn't work for me; Just the "off" function is working.
So, anyone an idea ?
Is it a little working for somebody ?
thx
Hi,
after testing, it doesn't work for me; Just the "off" function is working.
So, anyone an idea ?
Is it a little working for somebody ?
thx
It seems that the manual control of the device send the information to the box (% valve openning), but no command from the zipato to the device.
I though Zipato is 100% zwave compatible ? so what ?
It seems that the manual control of the device send the information to the box (% valve openning), but no command from the zipato to the device.
I though Zipato is 100% zwave compatible ? so what ?
I am new in zipato and zvawe and I cant to get Eurotronic comet to work, I try to send SETPOINT_HEAT, VALVE_POSITION nothing change .... the actuator works and holds temeterature what I set to the display on unit, but I cant to send to it. Please help me somebody!!!
I am new in zipato and zvawe and I cant to get Eurotronic comet to work, I try to send SETPOINT_HEAT, VALVE_POSITION nothing change .... the actuator works and holds temeterature what I set to the display on unit, but I cant to send to it. Please help me somebody!!!
I have same problems with eurotronic acurator, I testing and try diffrent settings and roles to get that valve work, but no good result I try to send setpoint heating but I cant device all time staying in MANU mode on default 22.0 C I try to add acurator to thermostat but anyway it dose not work, can anybody give some instructions how to add device to get it work propertly??
I have same problems with eurotronic acurator, I testing and try diffrent settings and roles to get that valve work, but no good result I try to send setpoint heating but I cant device all time staying in MANU mode on default 22.0 C I try to add acurator to thermostat but anyway it dose not work, can anybody give some instructions how to add device to get it work propertly??
I've opened a ticket and support said :
It seems that our descriptor for Comet Z-Wave thermostat is missing support for heating setpoint feature. Please be patient we will contact you with more information as soon as we will have them. Best regards,Pero Zovkic
I've opened a ticket and support said :
It seems that our descriptor for Comet Z-Wave thermostat is missing support for heating setpoint feature. Please be patient we will contact you with more information as soon as we will have them. Best regards,Pero Zovkic
That's funny because I also have contacted the Zipato support recently and asked for full support of this device. They told me that what we see is all they can do.
Since then I have tried to control the device with a virtual Thermostat but without any real success. This Information bríngs now some light into the problem. Please update as soon as you get some news from Zipato.
That's funny because I also have contacted the Zipato support recently and asked for full support of this device. They told me that what we see is all they can do.
Since then I have tried to control the device with a virtual Thermostat but without any real success. This Information bríngs now some light into the problem. Please update as soon as you get some news from Zipato.
It stucks since 7 months....I though zipato is zwave compatible ? Can We expect some upgrade for this device ?
It stucks since 7 months....I though zipato is zwave compatible ? Can We expect some upgrade for this device ?
I agree, I have 3 of those and they are stuck in my garage for last 9 months!
I agree, I have 3 of those and they are stuck in my garage for last 9 months!
Is there any update in this case, I have outside winter i buy zipato for main task to economy on house heating. But I am so dissatisfied and sad because nothing work :(
Is there any update in this case, I have outside winter i buy zipato for main task to economy on house heating. But I am so dissatisfied and sad because nothing work :(
Maybe we all should open a ticket again to bring this topic more into focus ....
Maybe we all should open a ticket again to bring this topic more into focus ....
Santa maybe ?
Santa maybe ?
As far as i see it, you can ask Santa for a different thermostat :P
As far as i see it, you can ask Santa for a different thermostat :P
never worked on my zipato. just the off function is working.
never worked on my zipato. just the off function is working.
Unfortunaly it is still not working properly. Readings (temp/mode/valvepos.) are fine, but no control possible. Setpoint_heating is not working.
Unfortunaly it is still not working properly. Readings (temp/mode/valvepos.) are fine, but no control possible. Setpoint_heating is not working.
Greetings,
We will receive a sample soon, we will check it out as soon as possible.
Greetings,
We will receive a sample soon, we will check it out as soon as possible.
I have two of those devices, they were added to the network correctly - only in vicinity of main controller. One of them dissapeared from network after 3 days of using, second works well.
Setting target temperature (setpoint heating) doesn't work for them, you can set valve position only - which is actually guessing. Built in thermometer reports temperature rather correctly. Summarizing - as setpoint doesn't work, it works in default mode (22'C) and reports temperature.
I have two of those devices, they were added to the network correctly - only in vicinity of main controller. One of them dissapeared from network after 3 days of using, second works well.
Setting target temperature (setpoint heating) doesn't work for them, you can set valve position only - which is actually guessing. Built in thermometer reports temperature rather correctly. Summarizing - as setpoint doesn't work, it works in default mode (22'C) and reports temperature.
We received a sample today, we will have more information about this sometime this week.
We received a sample today, we will have more information about this sometime this week.
Please rejoin your units, they should work a lot better now.
Here are a couple of notes about the Eurotronic COMET:
* It does not send unsolicited status updates, ever. The jog wheel on the unit is only used for turning it on, off or for temporary manual setpoint override. Because of this it can't really be used as a thermostat input. It works fine if you use it as just a thermostat output.
* Since it does not send unsolicited status updates, the actual current valve position will usually only be updated on the ui after two wakeup intervals
* The default wakeup interval is very long, somewhere around 160 hours. We suggest you keep this somewhere between 4 and 24 minutes. Intervals in this range should be a good compromise between responsiveness and battery life.
* if you want to use manual valve control you need to set the thermostat mode to MANUAL_CONTROL. Of course, in that case you can't use it with the virtual thermostat.
Please rejoin your units, they should work a lot better now.
Here are a couple of notes about the Eurotronic COMET:
* It does not send unsolicited status updates, ever. The jog wheel on the unit is only used for turning it on, off or for temporary manual setpoint override. Because of this it can't really be used as a thermostat input. It works fine if you use it as just a thermostat output.
* Since it does not send unsolicited status updates, the actual current valve position will usually only be updated on the ui after two wakeup intervals
* The default wakeup interval is very long, somewhere around 160 hours. We suggest you keep this somewhere between 4 and 24 minutes. Intervals in this range should be a good compromise between responsiveness and battery life.
* if you want to use manual valve control you need to set the thermostat mode to MANUAL_CONTROL. Of course, in that case you can't use it with the virtual thermostat.
Hi, Do we have to delete the device and add it again, or update the zipato fw ?
Hi, Do we have to delete the device and add it again, or update the zipato fw ?
Yes, delete your unit and add it again.
Yes, delete your unit and add it again.
Deleted ok, but can't add it again. After Zipato found it I have the message :"Manufacturer specificic report not found" try again
Deleted ok, but can't add it again. After Zipato found it I have the message :"Manufacturer specificic report not found" try again
Reboot your controller and try again.
Reboot your controller and try again.
same issue with Danfoss valves - ERROR E5 only for those handled by thermostat
same issue with Danfoss valves - ERROR E5 only for those handled by thermostat
:( not better
:( not better
It does the exclusion but after finding the device I have the same message.
It does the exclusion but after finding the device I have the same message.
Make sure to hold the button for longer than 5 seconds when adding or removing your unit.
Make sure to hold the button for longer than 5 seconds when adding or removing your unit.
And i forgot to mention one more thing, the valve will wake up each time you turn the jog wheel and the screen comes on.
And i forgot to mention one more thing, the valve will wake up each time you turn the jog wheel and the screen comes on.
:(( always the same problem "MANUFACTURER_SPECIFIC_REPORT not received" ...
I have reset the Zipato twice, tried everything...but its worse
:(( always the same problem "MANUFACTURER_SPECIFIC_REPORT not received" ...
I have reset the Zipato twice, tried everything...but its worse
I will try at home and let you know...presumably same error
I will try at home and let you know...presumably same error
Hi all,
First of all i want to thank Marko for his effort!
Problem here is that it is -5 outside right now in the Netherlands... so i'm going to test it tomorrow moring.
( My cats live in the room where i have the Comet and i don't want them to be freezed ;-)
Hi all,
First of all i want to thank Marko for his effort!
Problem here is that it is -5 outside right now in the Netherlands... so i'm going to test it tomorrow moring.
( My cats live in the room where i have the Comet and i don't want them to be freezed ;-)
Update: the including was succesfull. In the attached pictures you can see how the comet shows op in the module- and devicemanager.
But.... the communication/response is weird. When i change the valveposition or the mode, sometimes it seems to work, but mostly the values jump back to the previous setting.
I get it... that's what Marko ment with "* Since it does not send unsolicited status updates, the actual current valve position will usually only be updated on the ui after two wakeup intervals "
Also, on the display of the comet i saw 'REMO' . Never seen this before.
Update: the including was succesfull. In the attached pictures you can see how the comet shows op in the module- and devicemanager.
But.... the communication/response is weird. When i change the valveposition or the mode, sometimes it seems to work, but mostly the values jump back to the previous setting.
I get it... that's what Marko ment with "* Since it does not send unsolicited status updates, the actual current valve position will usually only be updated on the ui after two wakeup intervals "
Also, on the display of the comet i saw 'REMO' . Never seen this before.
My Comets added successfully, no weird "MANUFACTURER_SPECIFIC_REPORT not received" for me.
Now, can anyone help me out how to control Comets in terms of setting their required temperature rather then 0-100% valve. I had these installed on Vera before and it worked that way. Thanks.
My Comets added successfully, no weird "MANUFACTURER_SPECIFIC_REPORT not received" for me.
Now, can anyone help me out how to control Comets in terms of setting their required temperature rather then 0-100% valve. I had these installed on Vera before and it worked that way. Thanks.
This morning it was very cold in my room, the comet was outline and -8 outside.
Yesterday it seems to work perfectly, so what happends ?
This morning it was very cold in my room, the comet was outline and -8 outside.
Yesterday it seems to work perfectly, so what happends ?
Strange.... it's still working fine here. Can you still set it to manual_control mode and control the valveposition?
Maybe the wakeup interval config set too high? I've mine set to 4 minutes because i'm still testing.
Strange.... it's still working fine here. Can you still set it to manual_control mode and control the valveposition?
Maybe the wakeup interval config set too high? I've mine set to 4 minutes because i'm still testing.
Hi, my wakeup was 4 minutes, but maybe there is a time the thermostat goes to sleep very deeply ?
Hi, my wakeup was 4 minutes, but maybe there is a time the thermostat goes to sleep very deeply ?
Do you use rules to control it? I have not yet. I first want to be sure that it is working correct by controlling it from the ui.
Maybe it went to 'engery_save_mode'? Do you have a temperature set for that mode?
Do you use rules to control it? I have not yet. I first want to be sure that it is working correct by controlling it from the ui.
Maybe it went to 'engery_save_mode'? Do you have a temperature set for that mode?
I use the virtual thermostat to set the rules.
I use the virtual thermostat to set the rules.
This morning again, Comet Offline (red dot). After manual handle, it is always offline for the zipato zwave. The same after sync. I had to push the inside zwave button to wake it up, but for how long ? 24 ?
This morning again, Comet Offline (red dot). After manual handle, it is always offline for the zipato zwave. The same after sync. I had to push the inside zwave button to wake it up, but for how long ? 24 ?
Jacques, same situation here. I just came home from work, cold room, device offline. I had to reinstall the (same) batteries to get it back online.
I think it still needs a little finetuning...
Jacques, same situation here. I just came home from work, cold room, device offline. I had to reinstall the (same) batteries to get it back online.
I think it still needs a little finetuning...
I'm happy you have the same trouble, this means its not my device...What about the others ? We want your feedback !!
Keep testing...
I'm happy you have the same trouble, this means its not my device...What about the others ? We want your feedback !!
Keep testing...
I have 2 connected since 4-5 days and they keep working. No offline, keep reporting valve % and temp.
PS: I made sure to set the wakeup interval to 15min and other to 20min straight away after adding them to system (moved wheel to wake up screen and synchronized once they were on). Hope this helps.
I have 2 connected since 4-5 days and they keep working. No offline, keep reporting valve % and temp.
PS: I made sure to set the wakeup interval to 15min and other to 20min straight away after adding them to system (moved wheel to wake up screen and synchronized once they were on). Hope this helps.
Hi, i'm wondering how your device is working after a few days.
Mine is working good, but the only serrious problem i have is that the batteries drain out VERY quickly (in a few days) no matter what the update-interval is set to...
Strange....
Hi, i'm wondering how your device is working after a few days.
Mine is working good, but the only serrious problem i have is that the batteries drain out VERY quickly (in a few days) no matter what the update-interval is set to...
Strange....
Hello !!!
I also same problems with five of these devices !!!
Not even work with the virtual thermostat !!
Only on or off solution and always set the temperature to 22 ° !!
It is about 10 days I try to do all possible evidence ..... but nothing !!
They are also continuing the disconnection from the Z-Wave network !!!
I point out that it also disconnects the device a few meters from my ZipaTile !!
I must say that before with my Fibaro Home Center Lite functioned and also could adjust the TEMPERATURE !!!
THEN THE PROBLEM IS PRESENTED WITH ONLY ZIPATO !!!!
Unfortunately I had the bad idea to switch to buying a ZIPATO Zipatile !!!
I could rush back .... but unfortunately I sold my Fibaro Home Center !!
I think it would take a nice update from ZIPATO and by the parent of these infernal devices !!!
Possible that no one takes into consideration that now famous problem?
To consider that all these devices do not come cheap !!
The Z-Wave protocol should not guarantee a certain compatibility between devices?
I ask a few officially responsible ZIPATO to be a participant in solving the compatibility of this device with its own ZipaBox and ZipaTile !!
I suggest you contact the Eurotronic directly to solve the problem !!!!
Thank you
Max
Hello !!!
I also same problems with five of these devices !!!
Not even work with the virtual thermostat !!
Only on or off solution and always set the temperature to 22 ° !!
It is about 10 days I try to do all possible evidence ..... but nothing !!
They are also continuing the disconnection from the Z-Wave network !!!
I point out that it also disconnects the device a few meters from my ZipaTile !!
I must say that before with my Fibaro Home Center Lite functioned and also could adjust the TEMPERATURE !!!
THEN THE PROBLEM IS PRESENTED WITH ONLY ZIPATO !!!!
Unfortunately I had the bad idea to switch to buying a ZIPATO Zipatile !!!
I could rush back .... but unfortunately I sold my Fibaro Home Center !!
I think it would take a nice update from ZIPATO and by the parent of these infernal devices !!!
Possible that no one takes into consideration that now famous problem?
To consider that all these devices do not come cheap !!
The Z-Wave protocol should not guarantee a certain compatibility between devices?
I ask a few officially responsible ZIPATO to be a participant in solving the compatibility of this device with its own ZipaBox and ZipaTile !!
I suggest you contact the Eurotronic directly to solve the problem !!!!
Thank you
Max
Hello !!
In essence, the device work ....... only in this way:
- On off;
- It always turned on when the temperature set at 22 ° !!
Although it is associated with the virtual thermostat and start the weekly program with various temperature of the day and for example at night should be 18 ° the device is always fixed at 22 ° !!
You saw that the Zipato system recognizes the device as the old model StellaZ Radiator Thermostat?
Max
Hello !!
In essence, the device work ....... only in this way:
- On off;
- It always turned on when the temperature set at 22 ° !!
Although it is associated with the virtual thermostat and start the weekly program with various temperature of the day and for example at night should be 18 ° the device is always fixed at 22 ° !!
You saw that the Zipato system recognizes the device as the old model StellaZ Radiator Thermostat?
Max
Hello !!
I just bought a new ZipaTile and I did all the updates a few days ago !!!
But the firmware of the Comet Z-Wave as you upgrade?
Thank you
Hello !!
I just bought a new ZipaTile and I did all the updates a few days ago !!!
But the firmware of the Comet Z-Wave as you upgrade?
Thank you
What firmwareversions are out there? My comet has firmwareversion 0.5
Also.... i'm am not sure yet, but it seems to me that the batteries drain out fast when the Comet routes via neighbour nodes. In my first test-environment i had the comet near my zipabox. But last week i have moved it to another room. Now it routes via an fibaro wallplug and an FGS221 and my batteries drain out faster than i can drain out a can of beer :)
But like i said, i'm not sure yet but i'll let you all know.
What firmwareversions are out there? My comet has firmwareversion 0.5
Also.... i'm am not sure yet, but it seems to me that the batteries drain out fast when the Comet routes via neighbour nodes. In my first test-environment i had the comet near my zipabox. But last week i have moved it to another room. Now it routes via an fibaro wallplug and an FGS221 and my batteries drain out faster than i can drain out a can of beer :)
But like i said, i'm not sure yet but i'll let you all know.
Comet is not Zwave Plus so it is not possible to upgrade. Even if it would be Zwave Plus you would require some toold to do it.
Comet is not Zwave Plus so it is not possible to upgrade. Even if it would be Zwave Plus you would require some toold to do it.
Hi,
I would like to share some hints on this device, gathered from some user experiences from openzwave:
- the device antenna is of a bad design. make sure that this device operates near the controller or near some routing slave
- on wake up, the device does not send an updated reading of its internal temperature sensor. This can be done only by reading out this explicitly (overall refresh)
- trying to read out the temp value regularly will drain the battery very fast. Openzwave does not do that anymore. If needed, make sure you do so at least each 2 hours.
- this device has 2 Thermostat modes (ECO and Heat), and for each a setpoint could be set.
- the device has a 1 digit precision for setpoints. It won't accept values like 23.5. Most probably this command will be rejected. Some users even mentioned that might cause the device to become irresponsive.
- changing the setpoint on the device locally using the built in wheel will only cause a wakeup in the device. The changes will not cause any setpoint changes in the system (unlike the danfoss Lc13). So don't be surprised if your Virtual Themostat in Zipato does not get synchronized.
- a local change with the wheel will set the device in manual mode for 2 hours. After 2 hours it will revert back to the mode and temperature set before.
Tipps for usage:
- if you want to use the built in temp sensor as input sensor, don't do it. This will drain the batteries very fast. Try to use another sensor in your room instead.
- try as much as possible not to operate the device locally with the wheel
- try to heal the network after installation
- use only 1 digit precision setpoints in your rules or heating calendar.
- I use a wake-up time of 600s (10mn). I managed to have this device operated for 8 months. With openzwave I managed to have it run for more that a year because I adjust the wake-up time depending on the season (in winter 600s, in summer 3600s)
Hope this helps
Hi,
I would like to share some hints on this device, gathered from some user experiences from openzwave:
- the device antenna is of a bad design. make sure that this device operates near the controller or near some routing slave
- on wake up, the device does not send an updated reading of its internal temperature sensor. This can be done only by reading out this explicitly (overall refresh)
- trying to read out the temp value regularly will drain the battery very fast. Openzwave does not do that anymore. If needed, make sure you do so at least each 2 hours.
- this device has 2 Thermostat modes (ECO and Heat), and for each a setpoint could be set.
- the device has a 1 digit precision for setpoints. It won't accept values like 23.5. Most probably this command will be rejected. Some users even mentioned that might cause the device to become irresponsive.
- changing the setpoint on the device locally using the built in wheel will only cause a wakeup in the device. The changes will not cause any setpoint changes in the system (unlike the danfoss Lc13). So don't be surprised if your Virtual Themostat in Zipato does not get synchronized.
- a local change with the wheel will set the device in manual mode for 2 hours. After 2 hours it will revert back to the mode and temperature set before.
Tipps for usage:
- if you want to use the built in temp sensor as input sensor, don't do it. This will drain the batteries very fast. Try to use another sensor in your room instead.
- try as much as possible not to operate the device locally with the wheel
- try to heal the network after installation
- use only 1 digit precision setpoints in your rules or heating calendar.
- I use a wake-up time of 600s (10mn). I managed to have this device operated for 8 months. With openzwave I managed to have it run for more that a year because I adjust the wake-up time depending on the season (in winter 600s, in summer 3600s)
Hope this helps
Hello !!
Now I have made a total reset my system .... so it is still under development !!
First inclusion I put one of these devices ..... it is always recognized as STAR Z !!!!
Did you as the device is detected?
Some of you are able to regulate the temperature of COMET through ZipaTile?
My Comet is inserted in the virtual device Cooling device as in HEATING OUTPUTS.
The temperature is detected by the sensor inside the ZipaLite as default.
Yet the temperature at COMET in SETPOINT_HEATING value is always 22 ° !!
On the site of EUROtronic provides the following features:
"Heating and cooling temperature individually configurable via the Z-Wave-main controller."
But then where is the problem of ZipaLite?
I repeat with my Fibaro Home Center Lite could to set this value !!!
Possible that I have to throw 10 of these Comet just because I'm damn past Zipato?
I recommended to take a ZIPATO / DANFOSS?
With DANFOSS you can adjust the temperature Z-Wave central to let him follow the air conditioning program?
I do not know what to do.....
Hello !!
Now I have made a total reset my system .... so it is still under development !!
First inclusion I put one of these devices ..... it is always recognized as STAR Z !!!!
Did you as the device is detected?
Some of you are able to regulate the temperature of COMET through ZipaTile?
My Comet is inserted in the virtual device Cooling device as in HEATING OUTPUTS.
The temperature is detected by the sensor inside the ZipaLite as default.
Yet the temperature at COMET in SETPOINT_HEATING value is always 22 ° !!
On the site of EUROtronic provides the following features:
"Heating and cooling temperature individually configurable via the Z-Wave-main controller."
But then where is the problem of ZipaLite?
I repeat with my Fibaro Home Center Lite could to set this value !!!
Possible that I have to throw 10 of these Comet just because I'm damn past Zipato?
I recommended to take a ZIPATO / DANFOSS?
With DANFOSS you can adjust the temperature Z-Wave central to let him follow the air conditioning program?
I do not know what to do.....
Hello !!
After making a total reset and updated my ZipaTile all my Comet Z-Wave (10) are all recognized as STAR Z !!!
Someone who has a ZipaTile Comet device and a Z-Wave could you tell me please what has versions of these applications?
Here is my data:
- Zipatile Ver. 1.1.38 (Firmware?)
- Zipato Ver. 1.2
The Comet Z have a firmware version 0.5
Thank you
Hello !!
After making a total reset and updated my ZipaTile all my Comet Z-Wave (10) are all recognized as STAR Z !!!
Someone who has a ZipaTile Comet device and a Z-Wave could you tell me please what has versions of these applications?
Here is my data:
- Zipatile Ver. 1.1.38 (Firmware?)
- Zipato Ver. 1.2
The Comet Z have a firmware version 0.5
Thank you
Hello !! continue my tests with this thermostat.
I tried to associate one of these thermostats on a beautiful Raspberry PI 3 with Aeon Z-Stick and is increasingly recognized as a STELLA Z and not COMET Z but at least I can set all the parameters in the right way !!
Comfort mode or savings, operating temperature etc. c !!
But I tell me how it is that with hardware from 80 dollars and with an open source software (Domoticz, Home Assistant, Jeedom) everything works with a ZipaTile $ 400 does not work anything?
I repeat with Fibaro full compatibility ... so the problem is unfortunately the Zipato !!
Maybe it's because so one is forced to buy the famous Zipato-Danfoss to $ 60?
Hello !! continue my tests with this thermostat.
I tried to associate one of these thermostats on a beautiful Raspberry PI 3 with Aeon Z-Stick and is increasingly recognized as a STELLA Z and not COMET Z but at least I can set all the parameters in the right way !!
Comfort mode or savings, operating temperature etc. c !!
But I tell me how it is that with hardware from 80 dollars and with an open source software (Domoticz, Home Assistant, Jeedom) everything works with a ZipaTile $ 400 does not work anything?
I repeat with Fibaro full compatibility ... so the problem is unfortunately the Zipato !!
Maybe it's because so one is forced to buy the famous Zipato-Danfoss to $ 60?
Replies have been locked on this page!