You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all huge thanks for creating this, I love being able to solve a 300€ problem for about 3€ ;)
What I have
1 shutter in my bedroom (+ a 1-channel remote with 3 buttons up/down/my)
3 blinds in my living room(+ a 4-channel remote with 3 buttons + scroll wheel (+ch select))
linked to Home Assistant via MQTT. I'm shocked how easy it was to set everything up.
I have been able to pair all my shutters and they all respond to commands. The bedroom shutter works exactly as expected, i.e. the UP command opens it completely, the DOWN command closes it all the way down, "my" either stops it or sends it to the preset position.
The original 4-channel Telis remote for my living room blinds has both the UP/DOWN buttons and the scroll-wheel for adjusting tilt (+the my button). The "my" button works as expected however when I send an up/down command from HA to my covers they only move by a small amount, equivalent to one-step move of the scroll wheel (aka tilt adjust)
Is it possible to add the also option to send the "full down/up" command from pi-somfy instead of just the short tilt adjust? If I'm not mistaken in Home Assistant this is mapped to two different services:
As a result the position reporting in HA is also incorrect as pi-somfy assumes the blinds are moving to an end position and will report 0% or 100% after the operation time expires, preventing further movement.
If there's anything I can do to help troubleshoot this I'll be happy to.
Thanks again for the great work.
m.
The text was updated successfully, but these errors were encountered:
Update after 2 weeks: I now actually prefer the way it works at the moment (as opposed to ONLY having full up/down). My preset position is blinds all the way down and tilted open - this allows me to reset them using the "stop" command and then tilt them progressively by sending repeated down commands from HA. It would still be great to have both options available as it's not exactly practical to be closing them fully by repeating the tilt command 6 times (let alone having to open them fully bit by bit - I think the motors would conk out..).
This is a HA script that first sets both blinds to "my" position, then drops both down 3 times to give me partial shade:
Very late to this party but I had this same issue with RFLink. I have six of the (relatively new, I think) Somfy "Lift & Tilt 25" motors, which may be the reason.
First of all huge thanks for creating this, I love being able to solve a 300€ problem for about 3€ ;)
What I have
linked to Home Assistant via MQTT. I'm shocked how easy it was to set everything up.
I have been able to pair all my shutters and they all respond to commands. The bedroom shutter works exactly as expected, i.e. the UP command opens it completely, the DOWN command closes it all the way down, "my" either stops it or sends it to the preset position.
The original 4-channel Telis remote for my living room blinds has both the UP/DOWN buttons and the scroll-wheel for adjusting tilt (+the my button). The "my" button works as expected however when I send an up/down command from HA to my covers they only move by a small amount, equivalent to one-step move of the scroll wheel (aka tilt adjust)
I've googled, found this https://community.home-assistant.io/t/rflink-somfy-cover-moves-only-a-bit/187904/20 - it is for RFLink however the issue seems the same. The OP there suggest to switch the blinds to US mode, I tried that, no success.
Is it possible to add the also option to send the "full down/up" command from pi-somfy instead of just the short tilt adjust? If I'm not mistaken in Home Assistant this is mapped to two different services:
UP/DOWN - cover.open_cover/cover.close_cover
Wheel UP/DOWN - cover.open_cover_tilt/cover.close_cover_tilt
As a result the position reporting in HA is also incorrect as pi-somfy assumes the blinds are moving to an end position and will report 0% or 100% after the operation time expires, preventing further movement.
If there's anything I can do to help troubleshoot this I'll be happy to.
Thanks again for the great work.
m.
The text was updated successfully, but these errors were encountered: