Add EverspringAC301/Nexa ZRT-106

[filikun]

What is the feature?

Add EverspringAC301/Nexa ZRT-106

Description

I just got two EverspringAC301/Nexa ZRT-106 and get this in the logs. Both devices seem to work ok but I haven't run them that long.

better_thermostat Office TRV BT: intigration: zwave_js isn't native supported, feel free to open an issue, fallback adapter generic

hvac_modes: off, heat
min_temp: 5
max_temp: 35
preset_modes: none, Energy heat
current_temperature: 17.5
temperature: 16
preset_mode: none
friendly_name: Bedroom TRV
supported_features: 17

Additional Information

If you need any other info please tell and I'll share what I can get my hands on.

Everspring AC301 Nexa ZRT-106 Recent talk in the community about these devices

[auanasgheps]

It's exactly as it seems: zwave_js isn't native supported. It means isn't guaranteed to work and BT doesn't enable anything fancy

[filikun]

It's exactly as it seems: zwave_js isn't native supported.

It means isn't guaranteed to work and BT doesn't enable anything fancy

Ah okay, so it will still work ok? Like using an external thermometer ?

[KartoffelToby]

Yes, all main BT Features will work.

It only a hint, if Something didn't Work, or you have some bugs. It can be necessary to add an Adapter for zwave js to fix such issues.

Otherwise if everything work, there is no need for a Special Adapter

[filikun]

Okay, after having it on for the night I woke up in the morning with the radiators blasting on full heat. Target was set to 19c and room had 20c. Both BT sensors had that grey "inactive bage". When disabled BT the ordinary climate sensors had a target of like 32c or something. What could be wrong here? I set it up with climate sensor, external room/humidity sensors and outdoor temp sensor.

[filikun]

Even though the target temperature is already met the radiator is still warm and you can see the temperature is rising. Any idea what is going on? I use the AI time based calibration and my external temp and humidity sensor is an Awair. The Trv internal temp is at 24 degrees. And if I look at the original Trv entitie it's set as target 21.

[filikun]

Not sure where I can get logs for what's going on

[auanasgheps]

Here's how to enable logs:

Edit your main configuration.yaml file Add the following

#better thermostat debug
logger:
  default: warning
  logs:
    custom_components.better_thermostat: debug

Save and reboot. Logs wil appear in HA Settings > System > Logs > Load full logs

However you'll have to replicate the issue.

[filikun]

Sorry for my slow respons, I'll try that in 1.0 and see what I can find in the logs!

[filikun]

Here is almost a days worth of logs. I feel like they are not boosting enough like currently there is 18°C in the office and target is set to 22°C but the radiator is just lukewarm.

The history graph seems off as well

I'm using the AI model with temperature, humidity, outdoor and weather integration. Only child lock added on the 2nd settings page.

[filikun]

Here is logs from the night, the radiators was blasting on full for some reason https://pastebin.com/RWk2Paqy

Why does the graph look so unfinished? the orange area just disappears? Is that where the heating should be off? Because at 06:00 when we woke up the radiator was on max.

[filikun]

Does it take some time for the AI mode to get to know the external temp? And is it a good idea to have the external temp sensor closer to the radiator itself? Radiator and sensor are on opposite side of the room right now.

[auanasgheps]

Does it take some time for the AI mode to get to know the external temp? And is it a good idea to have the external temp sensor closer to the radiator itself? Radiator and sensor are on opposite side of the room right now.

The AI mode takes about 24 hours to learn, but the external temp is acquired instantly.

No, place the external temp sensor away from the heater. I would place it at least 2 meters away from the heater, and never close to a window or a door.

[wtom]

The orange part is where the heating is actually happening.

I've checked your logs and it's strange.

Office, your external sensor just reports full degree changes, it's not a problem but it's weird. But the main problem is, the target temperature is set to 35 degrees and you say it's not really warm the radiator. And you also see it on the temperature in the chart, it's not really going up. In the logs you got up to 21 degrees, but it's taking a very very long time.

Sleeping room looks fine from the logs and everything. Just that your radiator seems to heat even though BT doesn't want it to heat. So either your TRV does something to keep a temperature (maybe the overheat protection would solve it) or there is some other algorithm or mechanical problem.

On the office could be also a mechanical problem like that the valve is stuck or something.

[filikun]

After the recent Z-wave js update the bedroom TRV got stuck at full blast and became dead in HA. Trying to get it back BT shows humidity as temperature all is just random. Sometimes the office trv shows the set temperature of what the "real" TRV has for some reason and BT sometimes raises my set temp (in BT) to 10 times what I have set it to.

Not sure what's going on and the logs is reset every time I reboot. Is there any way to make HA create a seperate log file so that it's easier to follow without everything else going on?

[custom_components.better_thermostat.utils.controlling] better_thermostat Bedroom TRV BT: climate.bedroom_trv the real TRV did not respond to the system mode change seems like the hardware might be at fault here

[filikun]

When looking at the configuration on the device it uses a default of 120 minutes to auto report temperature. Might that be to long? It uses a max and min setpoint defaulting to 35C and 5C. Manual override is wierd one because it's set to 8 in the scale of 30minutes?! So what's that 8x30?

I also use the child lock on the device. But ProtectedBySequence is if you try to change anything on the hardware itself so that would not affect BT?

EDIT: On the manual override I found that 0x01~0x30, means 30mins is indeed the formula so default is 4hrs. I'm not sure what they mean by manual override though. The manual states Note: When adjusting temperature by manual override, the unit will send Thermostat SetPoint Report to the gateway, but the mode will remain the same mode.

EDIT2: Maybe just override on the hardware?

Manual Over-ride: the user can override the preset settings at anytime allowing for on-demand 
manual control of the TRV. Pressing the Up, Down and M button on the TRV will bypass the 
setpoints temporarily for 4 hours (Configure 10). After 4 hours, it will restore the last mode and 
temperature. 

Here is the manual

[filikun]

So a little update. It's doing its own thing sometimes and I can't figure it out really. I'll be starting logging it again and see if I can get some usefull information over time.

The biggest issue I'm facing is that the BT entitie changes target temperature at random times. I've setup an automation that keeps track of the target temperature and adjust it back when it goes crazy. So most of the times we have a target temperature around 18.5 and today it changed it to 25 for no reason and my automation kicks in and put it back to 18.5. I'm not sure why this happens as BT would only change the target temperature on the default climat entitie and not it's own target temperature?

I think it has problem with when Z-waveJS updates comes out and I guess it's not the updates itself but when the addon restarts after a completed update the TRV goes offline for a couple of seconds. A update came today and as stated bove the climate BT entitie was way above where I have put it. The other BT entitie I have (only two in two different rooms) was on 5.

EDIT: The Z-wave settings for the TRV's allow me to set a min and max setpoint value. They are defaulted to 5/35, can I change them without any issues with this integration?

[KartoffelToby]

You should Checkout the latest Version of BT