Replies: 1 comment
-
Home Assistant entities are exactly the same, just the reported state differs. Via unofficial integration it's "off" now, while via Matter it's "heat". So definitely Matter implementation in Kasa hub is causing this: Similarly via official HA integration for TP-Link I just installed, it's "heat". But this time there's also: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I just noticed that Matter option appeared in the Kasa app for KH100 hub (used for KE100 radiator valves). I will try to switch to Matter in the next few days and report the progress.
KH100 V1, firmware 1.5.19
KE100 V1, firmware 2.8.0
T310 V1, firmware 1.5.0
T315 V1, firmware 1.8.0
Initially I added the valves to HA in winter, but stopped using it after testing. Re-added this week, also with smart switch to turn on/off the gas boiler in line with valves' heating requirements, as well as a schedule. Works quite well so far!
I had to downgrade the plugin version to V3.0, as no devices connected to the hub have been recognized (awaiting PR acceptance and new release I think).
Matter update 1: all devices were recognized within seconds. Only entities available are Climate from valves and temperature/humidity from sensors. But there's one annoying issue which would force me to rethink my automations. All valves report "heating" whenever active ("ON" in app), regardless if the radiator is open or closed. This unofficial plugin is more accurate as "heating" always indicates the radiator is open and needs to heat the room.
I reported the issue on manufacturer's forums: https://community.tp-link.com/en/smart-home/forum/topic/706792
Beta Was this translation helpful? Give feedback.
All reactions