3 Acova Percale2 but only 2 reconized

[llaumgui]

Hi,

I migrate from zigpy (plugin Zigbee on Jeedom) to Zigbee2MQTT (plugin jeeZigbee on Jeedom). On zigpy, no soucy.

I have bought 3 Acova Percale 2. 2 of them are reconized witout any problem but the third is marked unsupported and display “TAFFETAS2 D1.00P1.03Z1.00” Instead of “PERCALE2 D1.00P1.03Z1.00” (remark: Taffeta is also supported).

Is there a way to map my Percale like a Percale ?

[Koenkk]

Added!

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[molusk]

Hello @llaumgui,

If I understand well, you have 2 Acova Percale2 heaters which think they are Taffetas2 ?
It seems Percale2 and Taffetas2 have the exact same features (including presence and open window detection), the heating technology seems to be the only difference between them.

On the other hand, Zigbee2MQTT integration is not at the same level for both. I added a few features to Taffetas2 converter lately : motion sensor and temperature calibration. A Taffetas2 user is complaining to me my late additions don’t show up with his heaters and I think he may have Taffetas2 heaters with the same firmware as yours (I asked him to confirm that).

So, my question, what do you think about making the configuration clean ? It means, at least, putting all Taffetas2 definitions together and maybe add the features to Percale2. I can do the configuration modifications but I can’t test anything as I don’t own the impacted devices. You would have to confirm everything is working well (using a custom converter before pushing anything to github of course).

The impact for you, once it is done, is having a bit more control on your heaters (useful or not, it’s your call) but 2 of them would be identified as Taffetas2 instead of Percale2 unless you keep a custom converter for them but you have to follow future configuration evolution manually.

Anyway, I won’t do anything without your agreement as I am not impacted and you are.

[llaumgui]

Hi,

I have 3 Acova Percale2. But only one is reconized like a Taffetas2.

For me:

• Electronic of Percale2 and Taffetas2 is identical.
• Features of Percale2 and Taffetas2 are identical.
• Look & feel are identical.
• Percale2 is a fluid inertia heater and Taffetas2 is a Dry inertia heater. It's the only difference.
• Acova can mount a Taffetas electronic on a Percale whitout issue.

For me you can clean configuration and allow same feature for Percale2 and Taffetas.

Best regards.

[molusk]

Ok, I will share a custom converter here soon and notify you so you can confirm everything is ok in your configuration.
Thanks.

[llaumgui]

I check that, but for me, there is another error.
I thought that localTemperatureCalibration allow to change the room temperature. But it's seem to be a factor (-3° to +6°) from the local temperature... But the local temperature is not the temperature of the room but the temperature of the set point.

Look your example:

        "hvacThermostat": {
          "attributes": {
            "localTemp": 700,
            "runningState": 0,
            "occupiedHeatingSetpoint": 1900,
            "unoccupiedHeatingSetpoint": 700,
            "systemMode": 0,
            "ocupancy": 1,
            "localTemperatureCalibration": 0,
            "ctrlSeqeOfOper": 2,
            "runningMode": 0,
            "setpointChangeSource": 0
          }
        },

Temperature of your room is it 7°00 ? Temperature on my heater is currently 23°3 (read on screen), but temperature of my sonde is 23,6. How to fix it ?

[molusk]

How did you get -3 and +6° limits ? Z2M UI allows me to set a value between -12.8 and +12.7°.
I did not test temperature calibration yet, I play with my heater management only when I don’t need them 😄 so I added the feature at the end of the cold season. It’s a new feature for me too.

One of the many limitations of Acova heaters is we can’t get the temperature sensor value... Local temperature is actually the current set-point (in my case, frost protection mode (7°) is active, shown as heat in Z2M, another limitation...).

My plan is to test the local temperature calibration early in the cold season with my kids room were temperature sensor is beside the bed while the heater in quite far from there so I have about 0.5° difference between them. I hope it will make the heater push to 19.5° when I ask 19° but it kind of a leap of faith 🤣

Another issue, maybe, is the temperature calibration seems to have no effects on any part of the heater interface (neither the set-point, nor the sensor) so we can’t be sure it is effective...

If you live in a colder region than mine, you may test all of these earlier than me 😉

[llaumgui]

How did you get -3 and +6° limits ? Z2M UI allows me to set a value between -12.8 and +12.7°.

My fault, I write an mistake.

My plan is to test the local temperature calibration early in the cold season with my kids room were temperature sensor is beside the bed while the heater in quite far from there so I have about 0.5° difference between them. I hope it will make the heater push to 19.5° when I ask 19° but it kind of a leap of faith 🤣

For that, you can increase the localTemp.

If you live in a colder region than mine, you may test all of these earlier than me 😉

I live in the south of the France... Currently, all my heaters are off.

Another issue, maybe, is the temperature calibration seems to have no effects on any part of the heater interface (neither the set-point, nor the sensor) so we can’t be sure it is effective...

If you look to this video (and speak french), you can see that you can associate your heater to a temperature sensor : https://www.youtube.com/watch?v=gXSuO8J4Tvk (~2mn35) I thinks it's for calibration.

[molusk]

For that, you can increase the localTemp.

Unless temperature calibration works... we will know soon.

I live in the south of the France... Currently, all my heaters are off.

Ok, I’ll start then, I am in Brittany 🌦️

If you look to this video (and speak french), you can see that you can associate your heater to a temperature sensor : https://www.youtube.com/watch?v=gXSuO8J4Tvk (~2mn35) I thinks it's for calibration.

It’s been a long time since I tested Enki stuff (they gave me the box when I bought the heaters), it evolved nicely.
I am not sure the sensor associated to the heater is a direct link between them, I think it’s an Enki feature as you can do with any automation or some integration in Home Assistant. It means it would only work if the brain is online (HA or Enki).

[llaumgui]

It’s been a long time since I tested Enki stuff (they gave me the box when I bought the heaters), it evolved nicely.
I am not sure the sensor associated to the heater is a direct link between them, I think it’s an Enki feature as you can do with any automation or some integration in Home Assistant. It means it would only work if the brain is online (HA or Enki).

When you manualy calibrate your sensor you see in the bottom a gauge. For me it's that the -12.8 and +12.7° calibration. But When you calibrate your sensor it's from a displayed temperature... It's this temperature that I would like to find, the point of calibration. Because without this, you can calibrate without reference.

[cperriot]

Hello,
Got an Acova Taffetas 2 today, and it has the ZigbeeModel : TAFFETAS2 D1.00P1.03Z1.00 so the fix done in august make my heater configured as a Percale 2 so I wasn't getting the occupancy. I had to modify the acova.ts to get it right.
I guess Acova made a mess in the factory and assembled Percale with Taffetas modules/firmware....

[molusk]

Hello,
That’s what I was afraid of...
As we discussed earlier, I should merge Percale and Taffetas models in the acova.js as soon as we are confident in the configuration and @llaumgui can confirm both have the same features.
We also should update the documentation, currently occupancy sensor is not documented for example.