#SwitchBot Matter device not reporting values
1 messages ยท Page 1 of 1 (latest)
That device literally came out 2 days ago ๐
Can you go to the device page in HA settings for this device and then download the diagnostics filer and share it here ?
yeah i would love to figure out how to make it work with bluetooth, or i at least thought it would show up in matter
i just dont know enough about how to start to discover via bluetooth and help them add to the integration
its above. hope that works
what are you looking for exactly?
that data includes a dump of all the matter 'clusters' on the device, which should make it possible to see what features the device is exposing, and how.
ok, so that's the switchbot hub 2, exposing a bridged device. Unfortunately, the only clusters it's providing are the humidity and temperature sensors which home assistant is already displaying. they aren't providing anything else.
you're probably going to have to wait for updates to the hub firmware to get any more info over matter
gotcha. so i need to get on switchbots butt see if they can expose it
would you be able to tell me what LINE in that file you are looking at, so as I may learn what you are looking
Not a specific line - I'm referencing various places in the data structure to the matter specifications.
oh. i was hoping there would be something I could easily spot to tell what its doing
to summarize what i did - starting on line 180, under "attributes", there is a dump of all of the endpoints, clusters, and attributes reported by the matter device. For each endpoint, I looked at the descriptor cluster (29) device type list attribute (0) to get the list of device types which that endpoint claims to implement. I cross-referenced the numeric values there against the list of standardized device types from the matter specification. the only things i found were the "root" endpoint for the bridge itself, the endpoint for the humidity sensor, the endpoint for the temperature sensor, and a couple of auxiliary endpoints used to provide information about how the bridged devices are arranged.
that sounds pretty complicated
theres no support yet in bluetooth for these or i would use that...and i dont know how to go about viewing the bluetooth data to see how i could help with that.
might want to follow https://github.com/Danielhiversen/pySwitchbot/issues/251 for that; nothing there yet, but the developer might ask for some information that you could provide.
yeah i left a reply. didnt even see that
If you want an easier way to do that - Open the Matter server UI panel and just explore the node cluster and attributes there.
It even lets you import that diagnostic dump ๐
I am working with SwitchBot for some other stuff, I'll ask around.
alright
What are you expecting to see using the Matter connection? Air quality is a fairly new part of the Matter standard and it's unclear whether CO will fall into that category.
i was expecting all sensors to show up
fwiw, the Matter 1.3 specification for an "Air Quality Sensor" does support a whole variety of measurements including temperature, humidity, CO, COโ, particulates, and a few other things. That version of the spec was published earlier this year.
so it should be possible for Switchbot to expose all the features of the Meter Pro CO2 as a matter air quality sensor.
Thanks. I had just seen "air quality sensor" but not what might be included in that.
So this is the switchbot "roadmap" for Matter and they don't give any indication this is coming.
The product listing on their website does not mention Matter even once, so I'm not sure why you would be expecting that. Seems to me the fact that temp and humidity are exposed, in spite of not being advertised to do so, is kind of a bonus.
I'd figure it would be exposed since their hub2 which is the matter bridge exposes it (temp / hum)
I'll just have to wait until someone adds the devices via bluetooth
Got an answer from SwitchBot. The Hub is still at matter 1.1, which is not compatible with the Air Quality clusters. There may be an update to 1.2 or 1.3 later but that is not set in stone. Could be that there is a newer revision of the hub needed to do that upgrade.
I'll give them a tip that they should probably disable adding the sensor to the matter bindings
It doesn't make sense to disable adding the sensor - the temperature and humidity clusters on it appear to be working fine?
Yeah, disable is a bit harsh. At least give a warning/message that not all functionality of the device will be exported to matter. Setting expectations
Switchbot needs to step up their game. I was initially pleased with their approach as they brought Matter to basically all their devices early on, rather than forcing people to buy newer versions to get Matter support.
But now they need to adapt to keep up as others are passing them by.
They need to release a true hub with ethernet, no silly limit of 8 devices exposed, and support for Matter 1.3. It needs to expose a fan as a fan and a vacuum as a vacuum (ok fine, wait on this one for more platforms to be handle vacs). Not just have all those show up as switches.
/end rant
i got a similar reply
fortunately, i was able to provide the necessary data on github to get CO2 added via bluetooth
The data for the pro meter co2 looks like b'\xb0\xe9\xfeT2\x15#\xe4\t\x99\xa5\x00#\x04f '
after i was made aware that it could be converted, i tested a few samples and was able to convert it from bytes in big_endian to an int
spoiler: I am working with them for the vacuum and its going to be in the next HA release. They will actually be the first to have a fully controllable vacuum. So maybe dont jump into conclusions too fast ๐
You've got my attention! Both S10 and K10 models?
working with SB directly?
For now the S10 but the K10 will also follow as far as I know.
thats nice. its too bad these companies cant see all the work users put in to make stuff work, and then just take over and help out since people clearly use it
local support or cloud?
Matter
Would there be map support
At some point yes, but at this time Matter does not yet have support for maps
for as long as that standard has been under discussion, it certainly didn't make much progress in supporting features
It made more progress in 2 years than Zigbee and Z-Wave in 15 years
it did get a head start by re-using a lot of stuff from zigbee, tho :)