Hi,
One of the most requested support from European users is certainly the support for more TRV models. Most manufacturers announce Matter compatible devices or devices that are exposed as Matter devices by a hub. Homematic IP is one of the most popular systems for heating in Europe (aside Bosch) and their TRV are great, but it's a closed system. Bridges like the Mediola ( Matter Bridge Homematic IP ) bridge expose them as Matter devices.
Correct me, if I'm wrong. Hubitat needs a unique Matter TRV driver to be able to pilot Matter TRV devices (similar to the generic TRV driver that never works). And, Hubitat should be able to connect to exposed Matter devices. If so, the development of a Matter TRV integration would open a completely new world of TRV devices to the European users. One driver. What holds Hubitat staff back from doing it ?
I've noticed that more high-quality Matter-compatible TRVs are becoming available on the market, and I was wondering if there are any plans for Hubitat to support these devices. It would be great to know if this is something in the pipeline and, if so, when we might expect it.
For many of us in Europe, this feature is quite important in making Hubitat a competitive alternative to other systems. I purchased my C8 Pro based on the promise of Matter support, but it seems that full integration, particularly for TRVs, is not yet in place. Any updates or information on this would be greatly appreciated!
No, I don't. If the Matter bridge worked with Hubitat that could be an alternative, but I prefer to wait for the Thermostat II (+M) that will be released soon as stand-alone Matter TRV. Also, the Tado Matter TRV that is already available, is expensive but seems to be very high quality as Tado always is. As TRV support is a long-standing issue with Hubitat I don't understand that Hubitat is not integrating its Matter support as a priority, making all Europeans happy and solving a mass of complaints.
I'm using 'Google Nest Matter Thermostat' driver for 4th Gen Nest thermostat and find there is no thermostatOperatingState value returned from the driver. I need the value for my automation. My 3rd Gen Nest thermostat using 'Google SDM API' returns thermostatOperatingState value. Why the matter driver doesn't?
Other problem of 3rd Gen Nest thermostat using 'Google SDM API' is that the attribute values have never been refreshed after changed. I have to refresh to get changed values, so I made a RM routine refresh every miniutes but it doesn't look clean.
I'm not sure why, but some other thermostats and TRVs I've tested using the Matter protocol do not return or update the thermostatOperatingState. I'm considering simulating this attribute at the driver level by setting it to 'heating' when the heating setpoint exceeds the measured room temperature. But I can't say when this may happen.
The Eve TRV is delivered as Homekit version, but can be connected to the Eve App (iPhone) and updated to Matter Firmware. I have no idea if it works well with Hubitat, but with Apple Homekit and as Matter version it works extremely well, and all available features in Matter are reporting and working. Maybe the Matter updated TRV is a solution for Hubitat users. When I have the time I will bind one to my C8 Pro as Matter devices can be bound to more than one controller in parallel. I think that it is a Hubitat thing, as all my spirits worked flawless with my eedomus system, but became very unreliable when connected to Hubitat. As this one is the only officially supported TRV I became frustrated, and I am switching to Apple Homekit. Another interesting thing with Eve is their thermostat controller, a small device that you can place anywhere in your room, that measures temperature, where you can set temperature and that uses Matter direct binding to control my 2 TRV in that room without passing by the central and all three devices show up as one thermostat only in the dashboard...
Tado X connects flawlessly with Matter and is working with the "Google Nest Matter Thermostat" driver as kkossev mentioned. I also tried some other drivers (not all thermostat drivers), without succes. One downside I noticed so far with the Nest driver: it has to be initialized about every 2 days, or else the hubitat will not receive updates. I will solve this by automatic triggering the "initialize" every day in rules machine. Does anyone has a better solution for this?
