With the latest jar from dropbox, the HTTP header error seems to be fixed, at least, my system can initialize the binding again (I went directly for the dockered setup)
Now I see in my logs the “skipping login due to too many requests” error, and after some minutes “Enabling login”. Now I can send messages again. I’ll continue to observe for some more days, hopefully the dreaded “too many logins” will never happen again…
I must admit that I lost track what the current state of the binding is. Is the jar from your dropbox still the most current one or did we get the changes merged in the meantime?
Not pushing or anything, I just want to know the current state of things
proper updating of thing states (less communication with the same result)
proper managing of executions (less communication with the same result)
improved detection of gateway type (Tahoma, Connexoon, …)
overall better performance
According to my opinion the V1 version is still more stable and the recommended one, since the V2 had caused weird issues to some users.
I plan to request merging of the V1 version to the master soon, but other commits (bringing support for new things) still wait for merging…
Thank you, I guess I will stay with V1 for the time being. In two days, a big remodeling of my home will be done (switching 4 RTS motors to 9 iocontrol ones), so I want to get things working nicely first before experimenting with new APIs
I have now also bought the connexoon. But like some before me here, I also have the problem that I can’t register on https://www.tahomalink.com I get the error message Wrong username or password. I have already changed my password several times, but I just can’t log in.
Somehow Somfy seems to me to be very error-prone with its products, if I had known that, I would have left my fingers off it…
I would like to draw your attention to a mail I received from Somfy stating that I still use an old version of the API and that it will expire on Dec 3. Since I’m using OpenHab 2.4, I guess the binding version in this release still contains the old API. Is there any way to upgrade to the new API (within the stable OpenHAB 2.4? Someone opened a dedicated post for this: Somfy / Tahoma old API
I’ve noticed Somfy’s registrations are by locality. Where did you buy your box from vs. where are you living?
For reference I’m in Australia but bought my box in the UK and had to register it as a UK box with a UK address.
Hello, I have copied the new version to the directory Addons. After I restarted the system, the addon in the Paperui under Configuration / Bindings is no longer displayed and things show an error. Version V1 continues to work without any problems.
Hi, sorry - I haven’t emphasized that for OH 2.4 you need either
upgrade to OH2.5 first
to manually install a newer gson jar
edit the MANIFEST.MF file in META-INF dir in the provided jar, so the newer gson is not required (the code works with the bundled gson in OH 2.4 as well)
change com.google.gson;version="[2.8,3)"
to com.google.gson;version="[2.4,3)"
Thanks, please create an issue, so I can add support for the Camera thing.
Regarding the warning - type id switch has been replaced by system.power, I guess you need to restart OH2 and if it does not work out, clear the caches…
I’ve updated to the latest Somfy Tahoma 2.5.0 binding snapshot. @Ondrej_Pecta I used your 3rd method to get the binding to work on OH2.4 Stable.
So far all good, all blinds (roller shutters x 9) have initialised and are online but will await until my rules kick in to check if everything is behaving as expected.
Hello Ondrej,
I installed also the newest tahoma binding after the update of the TahomaBox.
The binding works for my rollershutters, roofwindowblinds, roofwindow and enocean windowhandle.
I wanted to ask, if it is possible to see the status of the rollershutters (and others) via the binding? (when i use the switch next to the windows or the remote control)
thanks for your effort and your answers in advance
sure, this should be working.
The Bridge thing has configuration param Status timeout, which defines the timeout for syncing the status. It forces all the things to send the current status.
Try lowering the value and see if it works. If not or not sure, just PM me the debug log of the binding (enable the debug first)
Thanks.
Ondrej