ha-bridge
ha-bridge copied to clipboard
couldn't access to somfy devices
hi, @bwssytems
i have the lastest version on a synology dsm6.2.2 with docker aptalca/home-automation-bridge:lastest
Now the somfy devices list is always empty (0) with an error in the log
12-26-2019 05:10:44.268 | ERROR | Could not get Somfy devices | com.bwssystems.HABridge.plugins.somfy.SomfyInfo
12-26-2019 05:10:44.267 | WARN | HTTP response code was not an expected successful response of between 200 - 299, the code was: HTTP/1.1 401 with the content of <<<
Not authenticated
Thu Dec 26 05:10:44 CET 2019>>> | com.bwssystems.HABridge.plugins.http.HTTPHandler 12-26-2019 05:10:44.196 | INFO | Making SOMFY http setup call | com.bwssystems.HABridge.plugins.somfy.SomfyInfo
12-26-2019 05:10:44.195 | WARN | HTTP response code was not an expected successful response of between 200 - 299, the code was: HTTP/1.1 400 with the content of <<<
Bad request
Thu Dec 26 05:10:44 CET 2019>>> | com.bwssystems.HABridge.plugins.http.HTTPHandler
the bridge control is filled with the same somfy/tahoma parameter for almost 1 years and the "already somfy devices configured" show 2 devices which are OK and runable:
1 | volet cuisine | SOMFY | 22fbd2ea-c39c-485c-9824-065eee665159 2 | volet salle à manger | SOMFY | c70ab644-c813-49cc-b4de-35c6d8d8a81f
my bridge control somfy parameter: https://www.tahomalink.com/enduser-mobile-web/steer-html5-client/tahoma/# and i have checked my email and password to be sure that they are available
perhaps could the previous discussion with tahoma versus somfy API is the issue ? ref to https://github.com/bwssytems/ha-bridge/issues/1078#issuecomment-498965746
Please turn on debug for the HueMulator and post the output. As far as the Somfy API, they have not implemented that yet.
i have setted log level for hue.HueMulator and all the 3 SOMFY to TRACE and gert nothing more than the previous post:
12-28-2019 17:28:47.430 | ERROR | Could not get Somfy devices | com.bwssystems.HABridge.plugins.somfy.SomfyInfo |
---|---|---|---|
12-28-2019 17:28:47.428 | WARN | HTTP response code was not an expected successful response of between 200 - 299, the code was: HTTP/1.1 401 with the content of <<< Not authenticatedSat Dec 28 17:28:47 CET 2019>>> |
com.bwssystems.HABridge.plugins.http.HTTPHandler |
12-28-2019 17:28:47.359 | INFO | Making SOMFY http setup call | com.bwssystems.HABridge.plugins.somfy.SomfyInfo |
12-28-2019 17:28:47.357 | WARN | HTTP response code was not an expected successful response of between 200 - 299, the code was: HTTP/1.1 400 with the content of <<< Bad requestSat Dec 28 17:28:47 CET 2019>>> |
com.bwssystems.HABridge.plugins.http.HTTPHandler |
Trace is not valid, use debug please
12-31-2019 18:52:34.124 | ERROR | Could not get Somfy devices | com.bwssystems.HABridge.plugins.somfy.SomfyInfo |
---|---|---|---|
12-31-2019 18:52:34.120 | WARN | HTTP response code was not an expected successful response of between 200 - 299, the code was: HTTP/1.1 401 with the content of <<< Not authenticatedTue Dec 31 18:52:34 CET 2019>>> |
com.bwssystems.HABridge.plugins.http.HTTPHandler |
12-31-2019 18:52:34.120 | DEBUG | Somfy getSetup response <<< Not authenticatedTue Dec 31 18:52:34 CET 2019>>> |
com.bwssystems.HABridge.plugins.somfy.SomfyInfo |
12-31-2019 18:52:34.053 | DEBUG | Somfy login response <<< Bad requestTue Dec 31 18:52:34 CET 2019>>> |
com.bwssystems.HABridge.plugins.somfy.SomfyInfo |
12-31-2019 18:52:34.053 | INFO | Making SOMFY http setup call | com.bwssystems.HABridge.plugins.somfy.SomfyInfo |
12-31-2019 18:52:34.052 | WARN | HTTP response code was not an expected successful response of between 200 - 299, the code was: HTTP/1.1 400 with the content of <<< Bad requestTue Dec 31 18:52:34 CET 2019>>> |
com.bwssystems.HABridge.plugins.http.HTTPHandler |
12-31-2019 18:52:33.917 | DEBUG | consolidating devices for somfy | com.bwssystems.HABridge.plugins.somfy.SomfyHome |
12-31-2019 18:52:33.917 | DEBUG | Making SOMFY http login call | com.bwssystems.HABridge.plugins.somfy.SomfyInfo |
12-31-2019 18:52:33.916 | DEBUG | HueMulator GET called on api/* with request <<</api/devices/somfy/devices>>>, and body <<<>>> | com.bwssystems.HABridge.hue.HueMulator |
12-31-2019 18:52:33.916 | DEBUG | HueMulator GET called on api/* with request <<</api/devices>>>, and body <<<>>> | com.bwssystems.HABridge.hue.HueMulator |
hello, i have asked some news directly from SOMFY support team and the respnse is the following : "Bonjour Jean-Luc, La première version de l’API Tahomalink qui était dépréciée a été arrêtée début décembre. Si c’est celle-là que vous utilisiez il est normal que vous ne puissiez plus vous connecter. Une communication a normalement été faite par nos filiales commerciales, veuillez nous excuser si vous ne l’avez pas reçu."
"Hello jean-luc the 1rst version of the tahomalink API is depreciated and has been stopped beginning of december. If you're still using this one, it's obvious that you can't no more connected to this API. A communication should have been usually done by our commercial team. Please appologize if you havn't recieved it. "
Beginning of december is exactly the date where i couldn't connect to SOMFY ? could you check ?
thanks
Alright, I will take a look. They previously had no date available for the switch.
i'm coming back with the problem, since the change of somfy API , HA-bridge doesn't work anymore with tahoma / connexoon could you check the new API ?
same problem for me, ha-bridge is not compatible Somfy since December 2019.