Problem connecting to Telldus ZNet Lite v2, localy , globaly to telldus live works

Third party integrations
1

Connecting to ZNet Lite v2 works if I connect via telldus live, but if I instead have the following in configuration.yaml:

...
tellduslive:
  host: 192.168.10.48
...

and select that ip instead of cloud, the url is:
http://192.168.10.48/tellduslive/authorize?janrain_nonce=2020-04-29T21%3A36%3A25ZvnCcmU&openid.assoc_handle={HMAC-SHA1}{5ea9f35a}{9WnhBw%3D%3D}&openid.claimed_id=http%3A%2F%2Flogin.telldus.com%2Fid%3Fi%3D11360%26h%3Ddea50860be2ae762f5d44ac3de3dad0302e8c8c3&openid.identity=http%3A%2F%2Flogin.telldus.com%2Fid%3Fi%3D11360%26h%3Ddea50860be2ae762f5d44ac3de3dad0302e8c8c3&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=2020-04-29T21%3A36%3A26ZdLSIB3&openid.return_to=http%3A%2F%2F192.168.10.48%2Ftellduslive%2Fauthorize%3Fjanrain_nonce%3D2020-04-29T21%3A36%3A25ZvnCcmU&openid.sig=nqXpYBP60gUPs%2BNFDvTMvEQyPd4%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=klas%40sehlstedt.se&openid.sreg.fullname=Klas+Sehlstedt

The authorization page fails with:

404 Not Found

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 227, in call File “/usr/lib/python2.7/site-packages/web/base/Server.py”, line 199, in handle NotFound: (404, “The path ‘/tellduslive/authorize’ was not found.”)

Is it possible to connect locally to the unit?
If yes please advice or is this a bug?

2

I have the same problem. There is also 401 unauthorized error in the logs. It used to work fine so something has changed.

I cannot even authorize local telldus anymore from HA integration wizard, that gives me 404.

3

I managed to get this working by removing the telldus lines from configuration.yaml, and then reconfiguring the integration.