With Cozytouch, I have not yet seen the event RefreshAllDevicesStatesCompletedEvent (which triggers in the binding a refresh of devices at least every 5 minutes). What triggers this event in Tahoma ?
For the discovery, your idea would be to rely on refreshTahomaStates called every 5 minutes ? What I noticed in case of Cozytouch is that it does not trigger events describing all device states. So I don’t think we can rely on that for discovery.
To be honest with you, that is not fully clear for me what is doing URL “setup/devices/states/refresh”.
But maybe they are specific events produced for new devices or removed devices that are not yet supported by the binding ?
By the way, the discovery service is also retrieving the list of action groups.
For the discovery, I think this is not necessary to trigger an automatic scan every hour. If the user wants to scan, he can use the search button in UI. So I would suggest to simply remove the scheduled search every hour and only keep the manual scan. That’s being said, that is only 2 requests run once per hour, I don’t think the discovery is what will trigger the “too many requests” blocking.
Great hint. When I go to Tahomalink.com it tells me my user name or password is incorrect. Requested a password reset, was able to reset the password, and logged in. After logging out and logging in again, I got the same error message though. I can only get to the member area with the password reset option. And most importantly, the binding is not able to connect again.
I am wondering why the binding uses tahomalink. (And yes, my account has been locked, too.)
Official SOMFY API describes some other way using OAuth: Somfy Open API Developer Portal | APIs & Docs
Is it planned to update the binding to use this API?
I presume whether you use OAuth2 or not, the account will be locked anyway.
What I don’t know if it’s enough to reset the password and disable the Gateway thing for a while (1 day ?) to reactivate the account, or if someone from somfy must unlock the account manually (via phone or the somfy forum)
UPDATE: I reset my password this morning, and disabled the “Somfy Tahoma Bridge” thing until tonight. Just enabled it now, and the bridge is back online.
So i guess the account unlock itself after a while if you don’t hammer the server.
But, it looks like the long refresh interval causes status updates of devices (for example percentages of rollershutters) not to show up in time. Not sure if that’s really the solution.
I have looked through this thread to try solve my issue and tried everything to no avail. I also have a Connexoon so cant login at the Tahomalink site but the only thing that has worked is I was able to test to the https://ha201-1.overkiz.com/enduser-mobile-web/enduserAPI/login server using the Curl command you suggested.
Is there anything I need to change to point the binding to this.
As I started to do for the cozytouch bridge, we could add the support of the Connexoon bridge with its different URL. It would be easy considering what I already implemented. The main question would be; what are the current binding things supported by the Connexoon bridge?
But I now realize that my approach is probably not the best. We could simply have a generic bridge with a setting to choose between Tahoma, Connexoon, Cozytouch, …
I will prepare such an enhancement.
The difficulty is that each solution has apparently a slightly different way to handle the connection (cookie). No idea how Connexoon is providing the result of the login. So it would require testing with such s bridge.
it was quite quiete around the tahoma binding the last years, but since 6 month there some activities in my installation.
according to my log, the binding goes offline and online every minute. I changed the refresh intervall, but only one effect: it toggles now every 7 minutes.
Are you facing the same issues or am I the only one?
If yes, may you have a hint for me?
Extending the refresh interval results in authentication problems (token expiration etc). Please use the settings I have and enable the trace log, If you provide me with the log, I can check what’s happening. If the binding goes offline, there is an exception it can’t recover from. An od course Somfy could have changed something on their side…
Is the token lifetime not longer than 10 seconds?
A separate scheduler thread could be started to just keep the token alive, when the token is received, set the scheduler to refresh it just before it expires. In that way the status update and the token calls are separated, giving more flexibility.
wow, that was faster then any servicecenter. Thanks for the fast reply.
I set up my binding like yours and now there is no toggle between on- and offline. Thanks.
Unfortunately I wasn’t able to set up the logging and some investigations > I will do that next week.
Many thanks so far - I will come back with some further information.
over the lasts couple of days I saw some “offline/online” toggles, but not that often.
I set the Log Level on TRACE and can’t see any failure or mis-behaviour right now.
I will come back, if something changes.
Or do you have any other assumption?
