[homekit] roller shutters anomaly after update 4.57

Hello

following the 4.57 update the roller shutters appear correctly in HomeKit and that’s super cool!
However, the roller shutters that are only open/closed cannot be operated.
HomeKit asks for an opening percentage (0-100) whereas my shutters expect

Hi @zedyxer :slight_smile:

Normally, from what I can see of @bertrandda’s development, the two cases are indeed handled.

If that’s not the case, it’s probably a bug!

The PR:

@bertrandda what do you think?

Did you test the case with the « Open/Pause/Closed » button that we have on Gladys?

While waiting for a possible fix I created an MQTT cover for each of my shutters, with the « shutter position » feature. Via a small script in Node-RED I manage to control all my shutters — it’s almost perfect ^^

So each shutter is duplicated:

  • one with open/closed state
  • one with shutter position

Z.

1 Like

Normally both functions are handled, it works well with Aqara. Can you give me the model of your shutter please? And list all the associated features in Gladys? I’ll try to reproduce your case with a virtual MQTT device.

Have you tried tapping the curtain directly in your Home app? Normally

My shutters are Bubendorff, hacked with a Raspberry Pi Zero.
Je contrôle ces volets via

1 Like

I found something. In the library we use to replicate the HomeKit protocol, it is specified that for curtains/shutters the 3 characteristics (state, position, target position) are necessary.

In your case you said you only had the state (open/closed) as a feature in Gladys — in HomeKit the state is read-only (it shows whether it’s open/closed but doesn’t allow control). I need to change something so that if there is only a state feature, Gladys maps the position/target position percentages to the state feature.

1 Like

Back to the subject. As I said above, HomeKit needs certain characteristics to work, including a position. I tried to simulate the absent states — it partly works but the visual rendering in the Home app isn’t perfect. For example: it gets stuck in an open/closed state even when it’s finished. It still prompts you to choose an opening percentage, but of course it will open/close without exactly respecting that…

You can test with the docker image bertrandda/gladys:homekit

Thanks for watching @bertrandda, it’s always better than nothing :slight_smile:

@zedyxer Can you test the image and tell us if it works for you ( Tutoriel: Lancer une image Docker de test ) ?

Thank you,
I’ll take a look tonight :wink: I’ll keep you posted!

1 Like

After testing it works perfectly! I actually have the same setup, but it’s no longer necessary to duplicate the MQTT devices for the shutter’s state and position, thanks for taking the time on this topic :slight_smile: you just made a user happy ^^

3 Likes

It’s fixed in Gladys Assistant 4.61.1:

Thanks @bertrandda for the development!

1 Like