Clkg not supported, although in list

[lars05]

Hi,

I have 3 curtain switches (CLKG). They appear in HomeKit shown as "not supported".

[0x5e]

Hi,

I have 3 curtain switches (CLKG). They appear in HomeKit shown as "not supported".

Hi, can you try to clean homebridge accessory cache from web gui settings? I'm not sure if it is cache issue or something. If problem still happen, please provide your device's detail info.

[lars05]

I can confirm this didn't help.

https://www.amazon.de/gp/product/B07MXT9Y2D/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1
According to Tuba IoT platform the category is "clkg". Smart Curtain Switch

[0x5e]

Can you take a picture of Standard Instruction Set and Standard Status Set page ? So I can see what difference between your device and my virtual device.

[0x5e]

[lars05]

Status and instruction page look the same

[0x5e]

Ok, all juse one control ?

[lars05]

Yes there seems to be no calibration or percentage control

[0x5e]

Homebridge requires Window Covering must have Current Position, Position State, Target Position.
If only control exist, do you have any ideas of how to handling position issue? Or maybe we should treat it as a dual-switch ?

[lars05]

Yes maybe that would solve it, but as a dual switch I think it would only provide "open" and "close", not "stop", right?

[0x5e]

Yes, swicth is not the perfect solution, some plugin will treate device fan's level (low/medium/high) as three switches, if low is open, other two will be closed. But if all closed...

[0x5e]

For the curtain switches:

One way:
Set the slider with step 50, so it only can be 0%, 50%, 100%, and 0 means close, 50 stop, 100 open.

Another:
as described before, add 3 switches represents close, stop and open, If the on switch was changed to off, let it back to on again.

What do you think of these two?

[lars05]

I think the slider option would be the best applicable, this way it could also display the correct status wether its opened or closed

[0x5e]

Yes, but 50% means stop may confuse users. But I can't think way better than this. I will update later.

[0x5e]

When you close the curtain, will it be stoped by device it self and change state to stop?

[lars05]

[lars05]

Yes, changes to stop all by itself

[0x5e]

Please try the latest version

[lars05]

Unfortunately devices don't appear in HomeKit at all, although they are recognized by protocol

[0x5e]

Try clean accessory cache and restart, I have experienced too during the develop, and not sure why.

Edit: then kill and reopen Home App, open the room page. Home App may get update with delay.

[lars05]

Works pretty well.
Only downside is that although opened or fully closed it shows as "50% opened" as the system sets itself to "stop".
But guess we gonna have to live with that :)

Yes, we cant know stop means fully opened or fully closed.

[0x5e]

Yes :)

[lars05]

Thanks for your support