Telldus live integration - can't authenticate to local Tellstick ZNet API

Configuration
1

I am trying to integrate with my TellStick ZNet Lite v2 (fw 1.3.2) using the Telldus Live integration (integrations/tellduslive)

I have modified my configuration.yaml to provide the LAN address of my tellstick, and it shows up in my config/integrations/dashboard as a discovered integration.

I chose to direct connect to the local device, specifying its’ ip address (rather than fully integrating with telldus live)
Then I get a modal box asking me to authenticate against telldus live
This modal box has a hyperlink to ‘link to tellduslive account’ - this sends me to:
https://login.telldus.com/openid/server?openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.mode=checkid_setup&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.ns.sreg=http%3A%2F%2Fopenid.net%2Fextensions%2Fsreg%2F1.1&openid.realm=http%3A%2F%2F192.168.1.138&openid.return_to=http%3A%2F%2F192.168.1.138%2Ftellduslive%2Fauthorize%3Fjanrain_nonce%3D2024-03-27T12%253A14%253A15ZiE99dV&openid.sreg.required=fullname%2Cemail
I login, and get redirected to
http://192.168.1.138/tellduslive/authorize?janrain_nonce=2024-03-27T12%3A14%3A15ZiE99dV&openid.assoc_handle={HMAC-SHA1}{66040de7}{vH1qtQ%3D%3D}&openid.claimed_id=http%3A%2F%2Flogin.telldus.com%2Fid%3Fi%3D71642%26h%3D4d1d484ec8b4e696a6ca07441a453c9f1a255701&openid.identity=http%3A%2F%2Flogin.telldus.com%2Fid%3Fi%3D71642%26h%3D4d1d484ec8b4e696a6ca07441a453c9f1a255701&openid.mode=id_res&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.ns.sreg=http%3A%2F%2Fopenid.net%2Fextensions%2Fsreg%2F1.1&openid.op_endpoint=https%3A%2F%2Flogin.telldus.com%2Fopenid%2Fserver&openid.response_nonce=2024-03-27T12%3A15%3A35ZJfDTtb&openid.return_to=http%3A%2F%2F192.168.1.138%2Ftellduslive%2Fauthorize%3Fjanrain_nonce%3D2024-03-27T12%253A14%253A15ZiE99dV&openid.sig=AluOKlSryX7F5YJSH145i%2FC2rN0%3D&openid.signed=assoc_handle%2Cclaimed_id%2Cidentity%2Cmode%2Cns%2Cns.sreg%2Cop_endpoint%2Cresponse_nonce%2Creturn_to%2Csigned%2Csreg.email%2Csreg.fullname&openid.sreg.email=XXXXXXXX%40gmail.com&openid.sreg.fullname=XXX+XXXXXXXX
And it is here that I get a 404 error with the following body:

The path ‘/tellduslive/authorize’ was not found.

Traceback (most recent call last):
File “/usr/lib/python2.7/site-packages/cherrypy/_cprequest.py”, line 670, in respond
File “/usr/lib/python2.7/site-packages/cherrypy/lib/encoding.py”, line 217, in call
File “/usr/lib/python2.7/site-packages/cherrypy/_cpdispatch.py”, line 61, in call
File “/usr/lib/python2.7/site-packages/web/base/Server.py”, line 230, in call
File “/usr/lib/python2.7/site-packages/web/base/Server.py”, line 202, in handle
NotFound: (404, “The path ‘/tellduslive/authorize’ was not found.”)

Powered by CherryPy 3.7.0

I have read that some users on here have been able to get past this using incognito / inprivate - I have tried this using chrome/firefox/edge but always end up with the same 404 error.

I really don’t understand how to resolve this, I wonder if the openid.return_to url incorrect? And if so, what should it be?

Btw I am able to integrate if I use the Telldus cloud offering instead, but I would greatly prefer to be able to interact directly with my local device.

2

same issue here. Still looking for a fix

3

I know this isn’t an ideal answer for you, but I just got it working now. Using safari on my wife’s mac. I think it followed the same url flow, I couldn’t work out how to get developer tools on that thing unfortunately, and I don’t have access to it right now. Even after I got HA working, I was still unable to browse the local API anywhere else, not even on the mac in windows bootcamp and chrome.

So it seems the http 404 error is very subjective. As I said before, I’d already tried on different browsers on different windows pcs without success, and had even used Safari on my mobile. Maybe trying a browser in Linux might give better results.

Just before I had my little success, I was considering using this nodejs client to try to get an auth token - GitHub - mifi/telldus-local-auth: Node CLI for assisting set up of local auth for Telldus Live local devices - don’t know whether it would have worked, or exactly what I’d have done with the token if successful, but it may be useful.

I hope this helps somewhat, btw I had contacted Telldus support a week ago, if I get anything useful in a reply, I’ll share it here.

4

I had the same issue, did not work with Chrome but i just tried with Pale Moon and there it worked! :slight_smile:

5

Telldus live integration stopped working for me today. Error:
Log details (ERROR)
Logger: tellduslive
Source: /usr/local/lib/python3.13/site-packages/tellduslive.py:194
First occurred: 4:05:58 PM (3 occurrences)
Last logged: 4:07:53 PM
Failed to refresh access token: 401 Client Error: Unauthorized for url: http://192.168.50.122/api/refreshToken

To be able to access the Telldus locally, I also had to use Pale Moon browser. When entering Telldus Technologies, I get the message " 429 Too Many Requests".

6

Hi! Same happened to me. I need to get HA to fetch the new token from telldus through my integration, but i can’t get to the login screen. Anybody knows the answer?

7

The same happened to me yesterday. I have tried solving it today but with no luck. Where can I register a new key in for Telldus in HA?

8

It is probably a lot of people experiencing this now. It’s about a year ago this was an issue last time and I reckon a lot of people did the same as me. Bought one month of Premium to get the token/key and since then it has been ok.

I have been trying to get this to work for a long time now and my last try is to unplug the power of the Tellstick for a while. I believe it tries to get a key all the time and that makes your account run out of requests. As long as I had it plugged in I get this: "429 Too Many Requests

You have sent too many requests in a given amount of time."

in my browser if I try to go to (“https://pa-api.telldus.com/keys/index”)

When the tellstick is unplugged i can access the site.

So I will prepare everything in HA and plug in the tellstick and try again, I might be lucky.

Will get back once I’ve tried.

9

Have done this over and over and suddenly it worked, now all is back for me. Used Pale moon browser in private mode. Can’t really says what helped. Now I have some time to think about an RfxTrx and how to replace my Tellstick with that.

10

I have not been able to renew the local API token for a year now, due to “404 Not Found” during autentication. I tried again today, and it didn’t work with Firefox or Chrome, but found out it worked on Edge:

  1. Edit configuration.yaml with your local telldus IP:
tellduslive:
  host: 192.168.xxx.yyy
  scan_interval: 60
  1. Restart Home Assistant
  2. Login to your Home Assistant using Edge
  3. Go to “Notifications”, click on “newly discovered” telldus
  4. Select “local api, 192.168.1.xxx”
  5. Click on the link, and accept connection for HA.
  6. Submit
11

So now I have made the transition From Telldus to RfxTrx. RFX433XL. I have about 50 devices (switches and lights) with about 15 built in ones so I wanted to stick with 433Mhz.

It was easy, I stopped all automations, connected the RFX and installed the integration and ticked the box: “Automatically add devices”.

After that I manually sent a command for every device from one instance of my dashboard and looked in another. When the device popped up I just renamed it to what I wanted.

After all devices was done I switched of the “auto detect” function. I have some remotes that i use locally in some rooms and their commands also got discovered doing the same thing.

All works perfectly now.

I can agree that the RFX is a bit pricy for a 433 transceiver but I wanted to get rid of the token work with Telldus. It is also better response with the RFX.

I know a lot of people consider 433 ancient, but for me it works really well. If I need a built in switch today, I use sonoff or similar where I can flash tasmota, but for dimmers I still add Nexa MWMR-251. They work really well and works with the button on the wall, just add the spring. To get a wifi-dimmer with same functionality it is a lot more expensive.

12

I had the same issue here. What solved it was opening the link in private browsing in Firefox (having a clean state without being logged into the Telldus account), then completing the authentication process there.

So this seems to be some sort of cookie/browser issue.

13

Hi all,

I have seen this thread severel times - eg every time i have had problems with my Telldus integration.

Over the years i have had ’ authentication to local’ failing again and again - only to work after a few weeks.

I THINK I FOUND THE REASON FOR MY PROBLEMS. (others might have different root causes) - a simple REBOOT the telldus device (power cycle) before i went through the motions seams to have done the trick.

for others, here is my approach:

1, remove integration from ha integrations AND configuration.yaml AND from telldus live homepage (remove auth if there)
2, restart a couple of times
3, clear browser cache

4, (this is the NEW step) power cycle my Telldus ZNET V2

5, re-write ‘tellduslive:’ etc in configuration.yaml
6, restart
7, add integration (remember to select LOCAL, not cloud when doing this)
8, go through the auth process
9, DONE !

Hope this helps others - it has been anoing med for quite some time.

br

14

I changed my network and had to remove the integration and Telldus authorization. Last time I did the Telldus setup the integration authorization worked by using Firefox in private mode. Not this time though, I tried Firefox, Chrome and Edge in different modes. I fresh booted the Telldus device, followed the advices in this thread without any luck.
What worked for me just as several others here was to use Pale moon browser in private mode.

1 Like
15

Thank you, you saved me alot of testing! Similar issue like you.
This with Pale moon browser in private mode worked perfectly (Since firefox didn’t work as it usually have done).

16

Hi,

Managed to auth with Pale moon in private mode as well, thanks for the tip!

17

Pale moon in private browser mode do the trick