Hi @Zakarias_Mortensen
I’m on a quite similar route right now. Just starting to move automatons from HomeKit to Homey Pro. I try to have as much as possible moved to advanced flows in Homey and still have HomeKit as my major user interface with Siri.
I’m just using HomeKitty + HomeKit Controller. They have different purposes in my eyes. I use HomeKit Controller to get working Aqara FP2 e.g. and HomeKitty to have the directly connected (to Homey) devices to HomeKit again.
Maybe it’s also a way to try for you, to move some devices and automation from HomeKit to Homey to use advanced flows…
Due to the limited Support for Aqara devices, I decided to move my E1 Shutter controls back to the E1 Hub and connect it via the controller to homey.
Works great so far but there are some issues with the variable formats I wanted to share with you.
Position slider:
Seems to work in 0/100 format instead of 0/1
Thus the position shows either 0 or 1% instead of 0-100%.
Battery status
Same issue
Battery level is 100% but status shows 1%.
Maybe it’s easier to just add a setting for the device to let people manually chose wich format?
thanks for the quick response, idk why but I think the aqara motors are doing it somehow differently, I had the same issues when transferring them to HASS using the official homey aqara app and MQTT, I had to use custom settings
E.g. I change the opening to 30% in Aqara, the device shows 0.3% in Homey
I tried creating a diagnostics report but I always get an error „rate limited“…homey restart didn’t help…
But the slider itself seems to be correct. Like the slider positions, when I drag to ~25% it goes to 25% but shows 0% as description and 0.25 as position status
Edit: while dragging the slider, the description is correct, but once I let go it shows 0%.
Currently i only have a generic THEN card for capabilities that have on/off and enum values. Still need to come up with a generic one for range/numbers like the set position for the curtain. So in my opinion there can be a card for setting a position.
Hope to have fixed the transform to a right value in the sensor screen. Will be pushed in a next update.
Question:
I do have 10 Nanoleaf bulbs here (LINK), they are “Homekit over Thread”.
Today I clarified with Homey that “Thread” on Homey means “Matter over Thread” - no (direct) support for my devices. However, with the “Homekit Controller” I believe I can add them, correct? Unlike “Thread over Matter” (11 digit code) my bulbs have a 8-digit code…