Hi there,
today I started setting up my smart home devices in nymea. I could connect my Philips hue lights and accessories with no problem. (Although the motion sensors had generic names unlike the other devices.)
But when I tried to connect my tado account to nymea, I would go back to the things overview after typing in my credentials. No new device was found and no error message.
Not sure what I could do wrong here. Can anybody help?
no the tado account does not appear as a new thing. tado only has smart thermostats and I have two of them connected to my account. There would be no point supporting tado if thermostats are unsupported device types.
I also have problems implementing my Tado account into nymea. I always get the error message “something went wrong … wrong username or password” But with the same username / password combination, I can login via the official tado app as well as via tado homepage into my account without any problems. So the error must be definitely something else.
I remember I had a similar problem with another plugin longer time ago. The problem there was, that some special characters in the password weren’t encoded properly.
Hmm. I’ll need to look into that but I’m away for the weekend. In the meantime, it would be helpful if you could enable the tado logs ( system settings, developer tools, debug interface, in the logs tab) and see if you’re getting a better error message there.
Ok. I’ve just asked @Simon who also uses tado and it seems to work fine for him, so it’s probably again something small where they changed the initial authentication process. Shouldn’t be hard to fix. I’ll be back about this next week.
Hey, so I’ve created an account and tested the login with the plugin. Everything worked fine. Looking at the above log, which says “wrong username or password”, my guess is that your password contains a “special” special character which causes the encoding for the login to fail, perhaps a % or similar. Looking at the code I could indeed find an issue with the plugin where it would fail to properly encode such characters. I’ve filed a pull request which should fix that and it’s currently building in experimental.