Oddiwahn / Rti-Tek-TRV601

Converter file for the Rti-Tek TRV601
1 stars 0 forks source link

How to change heating times #1

Open grochib opened 3 years ago

grochib commented 3 years ago

Hey Oddiwahn,

I successfully used your converter to have my TRV working with Z2M on home assistant.

But some things I cannot get to work:

When in the zigbee2mqtt addon of home assistant I can see both the window detection button as well as the mentioned heating times. But I cannot make any changes: when pressing the window detection button nothing happens (though it appears like a working button, just without any visible changes) and no way of changing the programming times (there is simply no changes possible). When I tried changing it right in the state.json the devices suddenly became "not supported" until I configured them again in the Z2M addon of home assistant.

Please help me with this issue :) In case it is a matter of zigbee2mqtt or maybe a problem with the home assistant addon.

thanks a lot!

grochib commented 3 years ago

Just to add, this is my device manufacture: _TZE200_a4bpgplm

In "exposes" the programming_mode is greyed out so I cant change it. See picture attached

z2m_hass_trv601

Oddiwahn commented 2 years ago

Hi grochib,

regarding the window detection, I cannot tell whats the issue, this is working fine with my TRVs. However, sometimes I have problems when zigbee2mqtt doesn't pair with the TRV sucessfully. Did you try setting the TRV to OF and then long pressing the button to re-pair? This usulally helps with my TRVs. Also, I find the zigbee2mqtt implementation a bit buggy, apperently it makes a difference whether you restart the addon out of zigbeet2mqtt itself or from the supervisor.

For the schedule I haven't implemented a function to set the state (only read), because I am controlling my TRVs from home assistant.

grochib commented 2 years ago

Hi Oddiwahn,

thank you very much for your kind help!

Today (being sunday...) I tried your approach and did an automatisation in Home Assistant. But the first issue was that I couldnt set a "heating point", I was only able to define max and min temperatures. Any way, I tried setting the min temperature (22 Degrees Celsius), then changed the heating point down to 15 degrees on one trv only to discover that I the automatisation (sending the min temp of 22 degrees) didnt change anything. Neither the heating point was changed (I kind of hoped this would solve my issue) nor the actual min temperature (still 5 degrees). Then I tried the repairing: I set the same trv off, long pressed the button (starting the search for a host procedure) and the trv obviously repaired with my z2m host. I also restarted the z2m addon from within, not from the supervisor. No change! I could only set a heating point from within the z2m addon (still no option available in home assistant) but I couldnt change the window detection setting nor the min heating point.

I'm a bit lost: obviously, the trv are connected and integrated in home assistant (I can see their current state, I even can change the heating point manually at the lovelace card. But I cannot chose this setting as an option anywhere else - I'm lost... See the screen shots attached. Maybe I just confused. It would be great if you could help me with this!

Screenshot_20211128_203731 Screenshot_20211128_203940

thank you very much!

grochib commented 2 years ago

Hey Oddiwahn,

after writing my last comment I realized that since I can change the heating point from within lovelace there must be a way to do this automatically/scheduled. So I installed scheduler card (HACS) where I could define a schedule when the heating point (I assumed it would act like a human would change the heating points in lovelace) shall be changed. by the way: the entity for the heating point is called "climate.trv-of-choice", I could only find out while researching the raw data of the lovelace card - but nowhere else.. So I tried changing the heating points ("climate.trv-of-choice") but instead of a new heating point (18 degrees instead of 22) the heating mode changed from "fan_only" to "heat" (it showed "ON" on the trv instead of the 18 degrees I hoped to achieve).

All in all my trial didnt succeed and I'm still lost..

By they way: my zigbee2mqtt addon delivers continuisly errors: "UnhandledPromiseRejectionWarning" I start assuming that the issue is with the addon. When I first installed the addon I was still using a cc2531 and only later switched to slae.sh I was wondering if I should remove the whole addon, reinstall it and do the pairing all over again...

Thank you so much for your help so far!

Oddiwahn commented 2 years ago

Hi grochib,

sorry for the late reply. So the TRVs have four modes, these are off, manual (=fan_only), auto and heat. If you set the temperature to the minimum value (5°C in your case), the mode would automatically switch to "off" and if you set it to the max value (35°C), the mode would switch to "heat". Mabe this is the reason?

Actually, I do not know how your automation approach is working. If you can set the attributes inside the zigbee2mqtt addon directly but not from your automation, then there must be some issue there.

Also, I was using a CC2531 which is totally crap. It constantly hangs, so I have to pull it out and plug it in to get it working for maybe another few hours before it fails again. Yesterday I received my SONOFF USB Dongle Plus 3 after waiting for 6 weeks. Unfortunately, it is not working at all so I have to get my zigbee network running first. So I am also a bit lost too at the moment.