Yes that’s not an issue to restart. Did you full remove the somfy entry in your configuration.yaml? Meaning no somfy: at all.
I confirm I removed somfy: !include somfy.yaml in configuration.yaml and removed somfy.yaml from the config folder and still have the same message after restart " The component is not configured. Please follow the documentation."
Hello guys. A quick question. I want to connect an Alarm System also with Tahoma.
From the French forums seems that Protexial/Protexiom systems works flawlessly.
Does anybody know IF the RTS sensors send the information (about actions - battery etc) in the Tahoma BOX ? Or ONLY the IO sensors do that ?
Basically the IO sensors paired with Tahoma can trigger the Protexial/Protexiom system ?
Because RTS is undirectional while IO is bidirectional.
Hi all,
I’m new to home assistant. I’ve installed the Somfy Home Assistant Cloud integration service. Then, I’ve created a cover group for all my covers so I can close them all with one click.
There are about 20 covers. When I close them all, I get HTTP 500 errors and some of them won’t close.
Example :
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://api.somfy.com/api/v1/device/XXX/exec
2020-12-11 12:33:11 WARNING (SyncWorker_0) [urllib3.connectionpool] Connection pool is full, discarding connection: api.somfy.com
2020-12-11 12:33:12 WARNING (SyncWorker_11) [urllib3.connectionpool] Connection pool is full, discarding connection: api.somfy.com
2020-12-11 12:33:12 WARNING (SyncWorker_13) [urllib3.connectionpool] Connection pool is full, discarding connection: api.somfy.com
2020-12-11 12:33:12 WARNING (SyncWorker_3) [urllib3.connectionpool] Connection pool is full, discarding connection: api.somfy.com
2020-12-11 12:33:12 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139901372659840] 500 Server Error: Internal Server Error for url: https://api.somfy.com/api/v1/device/XXX/exec
I’ve read that I should use scene but my created scenes from tahoma doesn’t show up in HA. What did I miss ?
Contact me by PM. I will try to understand your issue.
Can you try with group of 5 or 10 covers?
First of all many thanks for all the good work!.
I’m testing the somfy plugin with Home Assistant with all my shutters. I have 10 Somfy RS100 IO motors and some other Somfy products
With my testing I have created an automation that sends me a notification on my iPhone when a particular shutter IS opened (so not the trigger shutter is opening, but is opened).
Today I got an unwanted notification on my iPhone: the shutter was totally open, nothing was happening at my side of position changing the shutter. In the log I see this information:
Logger: homeassistant.components.somfy
Source: helpers/update_coordinator.py:153
Integration: Somfy (documentation, issues)
First occurred: 13:19:31 (1 occurrences)
Last logged: 13:19:31
Error requesting somfy device update data: 502 Server Error: Bad Gateway for url: https://api.somfy.com/api/v1/site
Has anybody some idea what the reason is for this?
I know that the Somfy Tahoma box (I have version 1) is terrible because of the needs of an internet connection. I have created several topics about it on the Dutch forum and also many bugs and wishes for the tahoma. But I give up. They do nothing with it. Somfy is not a company that makes things for their customers.
But in this topic I have read about the Velux KLF 200. It is really exciting to see that the bridge should work with the IO products and that it is working locally. So probably I will buy this bridge in the near future.
But for now does anybody now what the reason is for my problem?
Hello tetienne, it seems to work just fine with a cover group of 7 covers.
But I’ve created a group with all my covers (which is about 20) and in this case I have HTTP 500 errors.
I’ve coded a dirty hack last night which waits 2 seconds between each toggle command. It seems to work fine, it’s just not an elegant solution.
For those interested, here’s the solution below:
ui-covers.yaml (dashboard yaml code)
- type: button
show_state: false
name: Tous les volets
icon: hass:window-open
tap_action:
action: call-service
service: script.toggle_covers_with_delay
service_data:
entities:
- cover.volet_veranda_1
- cover.volet_veranda_2
- cover.volet_veranda_3
- cover.volet_veranda_4
- cover.volet_veranda_5
- cover.volet_veranda_6
- cover.volet_veranda_7
- cover.volet_veranda_8
- cover.volet_cuisine_1
- cover.volet_cuisine_2
- cover.volet_sejour_1
- cover.volet_sejour_2
- cover.volet_sejour_3
- cover.local_piscine
- cover.volet_bureau_anthony
- cover.volet_chambre_d_amis
- cover.volet_chambre_parent
- cover.volet_bureau_daria
- cover.volet_couloir
- cover.volet_salle_de_bain
scripts.yaml:
toggle_covers_with_delay:
fields:
entities:
description: 'List of cover entities'
sequence:
- repeat:
count: "{{ entities|length }}"
sequence:
- service: cover.toggle
data_template:
entity_id: "{{ entities[repeat.index - 1] }}"
- delay: 2
To give some explanations, I have set a button widget on my dashboard which calls my script toggle_covers_with_delay with a list of all my covers.
My script toggle_covers_with_delay then loop over the list of covers to toggle each of their position and wait 2 seconds between each processing.
It’s not elegant, but It works.
Can you please uninstall the Somfy integration, and reinstall it using this custom component (through HACS for instance): https://github.com/tetienne/somfy-custom-component
That’s the same one you already know, but I use it to quickly test some fixes. Here, I have added a retry on the send command.
Tell me if it solves your issue.
Somfy server can return sometimes an error. You have only one occurrence of this error so that’s not a big deal. If it happen really more often, contact me again.
Hi tetienne,
Okay I will see how many times I will get this error. But actually every error I got is actually a probleem because it triggered a false automation. But we will see…
Then I have some other questions:
- In this topic I read also that somebody has requested the option of moving the shutter (RS100 IO) silently (the discrete mode).
Is there any news about it? When will it be implemented? Because it is a very important option for me. So you want the possibility to have this option on or off for a partical shutter or for serveral shutters.
- I noticed that when the roller shutter (RS100 IO) is completely open the position value is 100 and when it is totally closed the position value is 0.
For me that is not what I actually expect. I think it should be when the roller shutter is totally rolled up (so the window is open), it should be 0. When it is totally unrolled it should be 100 (so window is closed).
Is it possible to present this in the UI, so that when the window is open the slider is presented at the left and that the slider is totally filled to the the right when the window is closed (so shutter is down)?
@martinst The fact that 100 is fully opened and 0 closed is a Home Assistant choice. There is no way we can change this.
@SeBsZ @martinst For the slow mode, there are several possibilities I’m thinking about:
- Add an option that will force all the covers to be in slow mode every time.
- Add one option by device to force the linked cover to be in slow mode every time.
- Add a service taking one or several covers to move it/them slowly.
What do you think is best for your need?
@tetienne, for me, all options will work. If I had to think for everyone else I would go with option 3. If I understand correctly, this would allow you to make an automation that would move a cover slowly during the night and fast during the day - I think that would be the most flexible solution. Of course you will have to balance the time it takes whether it is worth it. Otherwise option 2 would be second best I think.
@tetienne Okay I understand it the issues about the 0 and 100.
Then the slow speed:
For me option 3 will be the correct one. I always operate my roller shutters in discrete mode (in the Tahoma app, but I will move everything to Home Assistant soon when this option is implemented).
But when my smoke detectors are detecting smoke, offcourse all my 10 shutters should be openend with the fast speed.
Hi tetienne, thanks for your answer.
I’ve installed your custom component through HACS but it doesn’t show up in Configuration / Integrations.
It just show up in HACS page without any possibility to configure it :
Once installed through HACS, you have to enable it like a classic integration like you did with the original Somfy.
@SeBsZ @martinst OK I will have a look this week to add this service. It should not be over complicated.
@tetienne That should be great when it is implemented. Thanks!
But the problem which I mentioned this saturday about the false triggers:
- This is occurred today a few times, the same error ==>
Logger: homeassistant.components.somfy
Source: helpers/update_coordinator.py:153
Integration: Somfy (documentation, issues)
First occurred: 12:47:54 (4 occurrences)
Last logged: 13:49:06
Error requesting somfy device update data: 502 Server Error: Bad Gateway for url: …
So in the history the state is presented as NOT AVAILABLE for all my roller shutters. I think it is really a problem of the false triggered automations.
Imagine starting a 2000 watt device on the trigger. Then you don’t want to have false triggers.
I’m quite new to Home Assistant maybe I do something wrong. But is it possible to execute the trigger of shutter is OPENED only by the correct ones and not when the status was not available at the moments before. So do I need some exclusion on my trigger?
Hi tetienne,
Thanks, I thought that installing the somfy integration through Configuration panel would install the official one 
So, that didn’t work as expected. Here are the logs, but it just seem to give up after 5 tries. Ideally, I would need an exponential backoff strategy I guess.
I’ve seen there’s an other somfy addon in HACS which you seem to be one of the authors : https://github.com/iMicknl/ha-tahoma
What’s the difference with this one ?
edit: I’ve tested with the non official Somfy TaHoma - Home Assistant from HACS and therefore I get access to all my scenes defined in Tahoma !! So now, it works perfectly because it calls a scene from tahoma. Does this custom component rely on a deprecated API ?
@SeBsZ @martinst I added 3 services related to the slow mode (only available if at least one cover support this mode):
- somfy.open_cover_slowly
- somfy.close_cover_slowly
- somfy.set_cover_position_slowly
Can you please install you too uninstall your Somfy integration and replace it by this one: > lease uninstall the Somfy integration, and reinstall it using this custom component (through HACS for instance): https://github.com/tetienne/somfy-custom-component
You can play with them within the dev tool panels.
Once you will confirm it works fine, I will add them to the main repository.