Hi @tetienne, thanks for the quick response.
Yes I saw these HTTP 404 und 50x reponses from the Somfy API.
There are also a lot of these errors (~10 errors per hour).
Are they a followup issue of not being able to connect to the somfy endpoint correctly?
Logger: homeassistant
Source: components/somfy/__init__.py:164
First occurred: 8:06:21 (54 occurrences)
Last logged: 12:55:06
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 119, in _handle_refresh_interval
await self.async_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 193, in async_refresh
update_callback()
File "/usr/src/homeassistant/homeassistant/components/somfy/__init__.py", line 209, in _handle_coordinator_update
self._create_device()
File "/usr/src/homeassistant/homeassistant/components/somfy/cover.py", line 70, in _create_device
self.cover = Blind(self.device, self.api)
File "/usr/src/homeassistant/homeassistant/components/somfy/__init__.py", line 164, in device
return self.coordinator.data[self._id]
KeyError: '6b0d5b11-eb766146-995cdac9-7e471798'
This error is an other issue. From time to time, Somfy returns an empty list of devices. They will check the reason.
I will submit a fix to handle properly this case. You will still see the error but not a huge stack trace like today. We talked about this few posts above.
I think this is just a question of implementation work, as already mentioned, the API allows a lot of functions, but currently only a few are implemented in the HA used pyvlx module.
Iâve just installed my RTS blinds and none of them show up in the official integration, but then Iâve also tried the Somfy Tahoma application and that doesnt seem to accept my credentials. From what I gather, being in Australia, our blinds are pretty much useless?
At the moment no, but Iâve started some discussions with the author of the tahoma integration and we will see if we can find the right URL to login with. I think this link will give you the hassio thread.
I never got my rts cover good working with the api or tahoma plugin.
So eventualy i bought a rfxcom RFXtrx433e, and thatâs working great and its al local solution without the cloud.
Iâm trying to execute my roller shutters by Home Assistant and with Apple Homekit safely. That means that when a window is open the shutter should not go down and not execute an position change what results in going down (so gowing up with a position change should be allowed).I have Somfy RS100 IO motors which have obstacle detection, but offcourse I dont want to happen this because it is not good for the motors and the other materials. So the software should implement this smart operation.
I have a window sensor to test if the window is open or closed.
In my configuration.yaml I have this template cover:
safe_close_cover:
alias: Closing the cover safely
sequence:
- condition: and
conditions:
- type: is_not_open
condition: device
device_id: f82f0d142f6d366f36876045f7dac11e
entity_id: binary_sensor.window_hal_1e_etage
domain: binary_sensor
- service: cover.close_cover
data: {}
entity_id: cover.05_hal_1e_etage
mode: single
safe_set_cover_position:
alias: Set the position of the cover safely
sequence:
- condition: and
conditions:
- type: is_not_open
condition: device
device_id: f82f0d142f6d366f36876045f7dac11e
entity_id: binary_sensor.window_hal_1e_etage
domain: binary_sensor
- service: cover.set_cover_position
data:
entity_id: cover.05_hal_1e_etage
position: '{{position}}'
mode: single
So what works?
Controlling from Home Assistant:
Closing the shutter when the window is open is blocked (GOOD)
Closing the shutter when the window is closed is working (GOOD)
Opening the shutter when the window is open is working (GOOD)
Opening the shutter when the window is closed is working (GOOD)
Changing position of the shutter (shutter going down) when the window is open is blocked (GOOD)
Changing position of the shutter (shutter going down) when the window is closed is working (GOOD) Changing position of the shutter (shutter going up) when the window is open is blocked (NOT CORRECT, I want to have this always working)
Changing position of the shutter (shutter going up) when the window is closed is working (GOOD)
Controlling home Apple HomeKit on an iOs device:
When the window is closed every works correctly.
When the window is open, everythings doesnât works. I think because HomeKit is always using the set cover position services and not the open and close services.
Another thing what you see in the HomeKit app is that the gear stays turing around on the icon of the cover and doesnât stops. So maybee Home Assistant should send a stop cover command so that the UI of HomeKit stops turing the gear.
So my questions are:
The way I do it now with the template cover and scripts is this the correct way to go?
How can I allow a cover set position change (which results the shutter to go up, so the window will more open) even when the window is open?
How can I solve the issue in HomeKit of continious turing gear on the cover icon?
Hey Martin
I have isolated the covers in HA completely by using input_number as helpers. Whenever the input number slider is changed, an automation is triggered to move the cover. Here you can limit the movements or deny the cover actuation completely. Expose the input_numbers to homekit instead of the covers and the same automation is triggered by homekit than within home assistant.
Eventually, I have moved all cover automation to appdaemon. Whenever an input_number slider is changed, python takes over and has some very complex algorithm to determine the next move.
How have you done this by using an slider with an input_number helper? Is it not triggered to much when changing the slider?
How is your input_number presented in HomeKit?
And when you change it from HomeKit and your logic doesnât allow it, what happens in Homekit? You donât have a contineous turning gear?
I have also made some progress. I have now moved my code to Node-RED and there I can allow action that will move the shutter up and deny when the action should move the roller down. The only thing what still is the case, is that the gear is never stop turning on the icon in HomeKit.
Iâm new on Home Assistant
I just installed the SOMFY Integration yesterday.
I made a group with 10 I/O covers. When I use the open_cover on my group, some cover stay closed (itâs random). Do you have an idea of the problem?
Thanks for the great work. I have Somfy Tahoma box and have the integration setup and working, but its very intermittent. I have lots of this in the logs:
Now, I know this is likely from the Somfy side, but any other controls I have using the somfy apps seem to work reliably (Alexa, or directly through the app). Not sure where to log an issue for this one, so thought I would post here first.
