Any progress to expect on this? I was hoping 12.4.4 would solve this but unfortunately not (yet). Only solution now is to spin up HA? 
That’s always a good plan. You won’t turn it off again 
1 Like
Well seems like another firmware 12.4.7 update that appears to have kicked my eve motion sensors (matter) offline again. SMH. They were unresponsive and had remove them and now can’t add them. Any ideas?
I had them natively added to homekit and shared matter device from within IoS Homekit to Homey Pro.
How are the Kasa KS205 working for you now? I got some Kasa over Wifi switches and I am getting a ‘rate limited’ error from time to time which is a bit annoying. They are still within the return period window so was looking for replacements. I saw these, but was not sure if Matter helps prevent getting this error as it seems to be something with how Kasa works with homey to know the status of stuff.
Was thinking if it is a matter switch I do not even need to use the Kasa app.
The Aqara U200 just got an update to support three states /actions for their lock (Locked, Unlocked, Latch Pulled) via Matter (seems to work in HA). But it seems like homey does not support those states and still only shows me Locked / Unlocked.
@Doekse is this really not supported or some issue with how Aqara exposes it (kind of like those custom energy clusters some manufacturers use)?
Lock, unlock, and unlatch/open door actions are all fully supported for Matter locks in Homey!
We’re currently fixing a small bug where the text for the unlatch/open door button isn’t displayed correctly. For now, you’ll find it as a separate button labeled “-”, while the Lock and Unlock actions appear as standard capabilities.
It could be that you need to re-pair the device with Homey for the capability to show up.
1 Like
I just got some Hue Essential GU10 bulbs which I connected via Thread to Homey and when I increase the brightness the lights get colder. I can even change it manually to some warmer color temperature but as soon as I start changing the brightness it will shift again.
When I connect the same bulb via bluetooth to my phone (with the Hue app) the brightness control works as expected.
I assume that it might be some weird way how Homey sends the brightness command? I don’t have another Matter/Thread hub to test this out, but maybe somebody else is also running into this problem?
EDIT: I just tried to change the brightness via Homey and I see in the Hue app that the actual configured temperature starts to jump around. So I assume this is really due to how Homey sends the brightness command. @Doekse do you maybe have some insight into that?
EDIT2: When I share the matter device and then add it to Apple Home (just on my phone without a hub) the brightness controls also work as expected without shifting color temperature.
EDIT3: There is a option for the level control cluster in the Matter spec called “CoupleColorTempToLevel”. I assume that Homey might be using this incorrectly (or at least from my point of view unexpectedly).
EDIT4: Seems like it really was changed sometime between 12.5 and 12.7 to be coupled to the color temperature, which seems like a mistake
