I posted this on another topic, but thought maybe it deserved it's own. I have 4 altitude fans that all support matter. 3 currently installed. I have been using HADB to bring them into hubitat, but realized today that hubitat does not seem to know what speed the fan is in, even though it can set the speed. I thought about adding it to Hubitat directly. There are several drivers that seem to work for the light, but none for the fan function. I tried the big a** fan driver as well, with the same outcome; light responds, but fan does not. The light is color temp, but not rgb. To make things possibly more difficult, 2 of the lights have separate up and down lights. I can control it all individually through smartthings, but would really like to get it added to hubitat if possible. Any help is greatly appreciated.
I agree, you should try to get the fans connected directly through matter. I've never connected a matter device myself, but there seem to be pretty clear instructions available from Hubitat to do that. Others here could certainly help you with that if need.
Just curious why you were using HADB instead of HubiThings Replica to bring in a device you have working in Smart Things?
Honestly...
I haven't been using smartthings that much. I used them for a short period before I switched to HE. Honestly, if felt like samsung was abandoning it. I actually had hubithings replica at one time, back before I had any matter devices, but thought I had read somewhere that it wasn't going to be supported anymore and since I wasn't really using it, I removed it. It wasn't until I needed a thread border router that I started using smartthings again. I have a eufy lock that uses thread and tried the aqara p2(?). I initially upgraded my amazon devices to use thread, but found that the connection wasn't stable. I plugged in my old smartthings hub when I found out it had thread and have been using it alot to test matter/thread devices. We just moved and I am using smartthings station to add matter / thread devices for their initial commision before adding them elsewhere.
Posting this hear since it is more specific to this thread. Modified version of my BAF fan driver posted below.
Matter_By_Mavrrick/Altitude Fan Matter at main · Mavrrick/Matter_By_Mavrrick
Needs to be validated,
seems to be working. I'll copy logs here, but I think I may just have moved too fast or it took a couple of commands for it to create the child devices.
from there on it started working. sorry for the data overload
I added one of the other fans to look at it. Ive been looking through the driver to see how all this works. Due to the other fans having 2 lights and 1 fan, they have 3 endpoints. 01 being the down light, 02 bein the uplight, and 03 being the fan. I added the endpoint and changed the fan to 03. I was able to get it working. The only thing that appears to not work is the uplight updating its status. Do you think it needs its own child device to call / its own operations within the parent device? Im not home right now but was in the process of adding a second operation calling the new endpoint but then realized i might need to do the same with a child device.
I would need to look at the clusters for that third endpoint to see what is needed. Probably need to refresh my memory for what clusters mean what.
Can you go ahead and generate that cluster list by using thr "devices" driver.
I was actually gonna ask you about cluster and attribute identification. Do you have a place you refer to for that information or is it just something you have come to know after all the work you've done with this? Are they pretty much the same across similar devices?
is HubiThings Replica local?
No, it uses the Samsung cloud. I had only used it in the past to connect cloud devices that were connected to SmartThings. I got the impression the fan was connected to SmartThings via cloud, but I see you never really said that, and it is probably connected via matter.
Yes, it's connected via Matter. Seems to be the friendliest for commissioning and easy to share with other services afterwards.
Now i kind of know what some of them are just by looking at them, but in learning i had to go to the Matter spec website and download the docs for the spec. Then search them. The spec has a few docs and one of then has the magic sauce to know is what and what commands can be passed. Since i did that the spec has been updates twice now. I think my docs are for version 1.3 and they recently released 1.5.
Were you able to look at the third endpoint. I tried adding it to the driver. Saved it as a separate driver and then used an additional if statement to parse that device. However, I didn't quite get it. I let it go for a bit and now that I'm revisiting, I'm going in circles. when adding the device, it makes a light and fan child. I delete those (at least the fan), change the driver to the altered driver, initialize, and it creates all three child devices. The light (endpoint 01) works fine. Endpoint 02 responds to commands, but will not update without sending a refresh command for some reason. Somehow in this process, I seem to have bricked the fan (now endpoint 03). It doesn't respond at all. It shows the following error when I do get something.
Nevermind, I finally messed with it enough until I was able to fifure it out. Main thing was I had to change the subscriptions I believe. For some reason, it didnt like the initial value of 1 in the previous speed. Once i was able to get that changed, the dan started working. Somehow during the process i reverted back to the original parent for the 2 children instead of the 3 children and that had me confused for a bit.
Thanks for all of your help on this.
So are you all set. The last st of endpoints you posted do appear to both be light devices. Does that sound right. Does the fan have something like up and down light?
That wold be similar to the BAF fan my driver was originally written for.
