search

mwraith / homebridge-somfi-blinds

A Homebridge plugin to control any device with the Somfy RTS technology with a Raspberry Pi connected to a simple 433 MHz transmitter. Adapted from wibberryd/homebridge-rpi-rts, but provides a stateful service.
MIT License
7 stars 3 forks source link

"My" button (stop) in non admin mode #6

Open Louison-B opened 2 years ago

Louison-B commented 2 years ago

To start thank you for this beautiful plugin.

I was already using "rpi-rts" but your plugin displays a real rolling shutter on the home application. 👍

Is it possible to have an opening percentage according to the time the shutter takes to open ? To configure in the config file of course.

Secondly, is it possible to have a "my" button to stop the shutter without activate the admin mode and lost the beautiful rolling shutter in the home app ?

Greetings,

mwraith commented 2 years ago

Hi @Louison-B

Thank you for you kind comments, it's nice to know that others are finding it useful too.

I have just published 0.4.0 which was previously a Beta version that I had been testing for a while. One change in this version is that you can now set the amount of time it shows the blind as opening/closing in the config time to make it more realistic. And if you tap the blind while it is moving then instead of sending the opposite Up/Down signal, it rather presses the "my" button and stops the blind at current position. This therefore allows you to still just have the one accessory appear in HomeKit, but still make use of partial opening positions. Additionally there is a new parameter that was added that can entirely replace the Up signal with the My signal when fully opening although this is only really helpful if you never open the blind fully (as with Venetian Blinds).

In terms of being able to send an exact percentage I did think about this. This challenge is the blinds give no feedback about their current position, so you are just relying on the timings being exactly accurate. It feels like it would be quite fiddly to setup and probably a bit prone to error over time. That said, I wouldn't rule it out as an experimental option at some point and so I will leave it open as an enhancement request.

All the best

Mark

Louison-B commented 2 years ago

Thank you for your respond. I can't wait to test these new features !

Also, today I have to restart my RPI. After that, the plugin show me this error "pigpio error -1 in gpioInitialise" so I try these cmd "sudo killall pigpiod", "sudo systemctl disable pigpiod" "sudo restart" no improvements...

I finally find the good way : these cmd "sudo 1sof -i TCP: 8888" and "sudo kill -9 PID" but I'm not sure if it's lasting solution.

Greetings,

Louison.

mwraith commented 2 years ago

Hi Louison

Cool, let me know how it goes. And it sounds like something else is using the same port (8888) as pigpio. There was another issue raised related to ebusd taking the same port with a very similar error. Maybe try to switch the port to something else (pigpiod -p 8887) ?

Mark

Louison-B commented 2 years ago
résoudre_problème_pigpiod-1

I will try to change the port of pigpiod thank you again !