Closed phellarv closed 11 months ago
Hey there @fredrike, mind taking a look at this issue as it has been labeled with an integration (tellduslive
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
tellduslive documentation tellduslive source (message by IssueLinks)
Had the same problem. used the browser inkognito and that worked.
Heads-up: pa-api.telldus.com is unavailable due to Telldus blocking requests <10 requests / minute https://telldus.com/driftinformation/
Truly a sh*t show. Lets hope telldus gets their shit together then.
/ Nicklas Andersson
Den mån 4 dec. 2023 15:38William @.***> skrev:
Heads-up: pa-api.telldus.com is unavailable due to Telldus blocking requests <10 requests / minute https://telldus.com/driftinformation/
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104968#issuecomment-1838770302, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACDGWG3PY5SJ7OD24RWODB3YHXN6ZAVCNFSM6AAAAABAFDVS7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZYG43TAMZQGI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Isn't it possible to use this device fully local somehow? Isn't "local API" supposed to be just that? I added the "host" parameter with local IP for it but it seems it is still affected by telldus stuff they are doing right now :( I guess, even if it had a fullt local way to communicate with it we still have to manage the devices on the telldus live interface so if that too goes away too for free users we can't use this device anyway :(
In local mode only authentication should be using the Internet so it should work for months at the time without a connection. I think scheduling and stuff is local to.
But I'm not investing anymore in to this system I don't trust it. 433mhz stuff will probably have to stay on it but I will get a separate z-wave device.
/ Nicklas Andersson
Den mån 4 dec. 2023 17:40dnordenberg @.***> skrev:
Isn't it possible to use this device fully local somehow? Isn't "local API" supposed to be just that? I added the "host" parameter with local IP for it but it seems it is still affected by telldus stuff they are doing right now :( I guess, even if it had a fullt local way to communicate with it we still have to manage the devices on the telldus live interface so if that too goes away too for free users we can't use this device anyway :(
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104968#issuecomment-1839035243, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACDGWGZE5NOONOSCOO5OUKDYHX4H7AVCNFSM6AAAAABAFDVS7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZZGAZTKMRUGM . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Isn't it possible to use this device fully local somehow? Isn't "local API" supposed to be just that? I added the "host" parameter with local IP for it but it seems it is still affected by telldus stuff they are doing right now :( I guess, even if it had a fullt local way to communicate with it we still have to manage the devices on the telldus live interface so if that too goes away too for free users we can't use this device anyway :(
Yes, there is the Telldus to mqtt local plug in tat makes the znet truly local. https://github.com/quazzie/tellstick-plugin-mqtt-hass
https://telldus.com/driftinformation/
From webb (in Swedish): Summary: Telldus API is shut down
Information till er som använder sig av Telldus API (ej Google Home-användare):
För Telldus-användare som gratis nyttjar våra API-tjänster kommer vi behöva se över omfattningen och kapaciteten av dessa tjänster i skenet av de kostnader som är kopplade till att tillhandahålla vissa tjänster med kravet på serverkapacitet, redundans och säkerhet.
pa-api.telldus.com kommer att förbli nere för närvarande medan vi inför ytterligare funktioner för att begränsa frekvensen av inkommande trafik som orsakas av vissa användare. Vi kommer så fort vi kan att öppna det igen när implementering och tester har gjorts. Om du använder våra API-tjänster, vänligen notera följande:
Vi kommer uppdatera vår driftinformation när pa-api.telldus.com är tillgängligt igen.
Dags att lägga ner hela tellstick
Isn't it possible to use this device fully local somehow? Isn't "local API" supposed to be just that? I added the "host" parameter with local IP for it but it seems it is still affected by telldus stuff they are doing right now :( I guess, even if it had a fullt local way to communicate with it we still have to manage the devices on the telldus live interface so if that too goes away too for free users we can't use this device anyway :(
Yes, there is the Telldus to mqtt local plug in tat makes the znet truly local. https://github.com/quazzie/tellstick-plugin-mqtt-hass
Oh I have not seen that, thanks :) But I guess Telldus might not be so helpful with that now with their new direcition :( But that is only a guess...
https://x.com/telldus_status/status/1731822152326803461?s=46&t=0rVhb-4GzOAEng8axsH5bw
We have been busy working on the configurations and it looks like we have found the sweet spot. We are observing the performance and stability. If everything goes fine, we could re-open api access (via pa-api.telldus.com) soonest tomorrow. Stay tuned.
I'm curious to know why their API servers even matters when entering the host parameter in the integration? What is the point with it if it still needs to talk to Telldus API server?
I'm curious to know why their API servers even matters when entering the host parameter in the integration? What is the point with it if it still needs to talk to Telldus API server?
It just needs to talk to their servers once for auth then its local until the token expires.
Same as #104376
@home-assistant close
I finally managed to get local access working (again) by using Firefox instead of Safari or Brave.
I'm still having issues logging into the tellstick, after trying to accessing the ip address, getting the telldus login screen, logging in, it keeps returning 404 not found "The path '/tellduslive/authorize' was not found." 😞
EDIT: @CNjord, your trick worked for me using incognito mode on Google chrome. Thanks!
It was some strange cache issue for me. Solved it by pasting the link directly to an incognito tab.
/ Nicklas Andersson
Den tors 21 dec. 2023 14:51yflorack @.***> skrev:
I'm still having issues logging into the tellstick, after trying to accessing the ip address, getting the telldus login screen, logging in, it keeps returning 404 not found "The path '/tellduslive/authorize' was not found." 😞
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104968#issuecomment-1866288260, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACDGWGY3K4N7PK6TU2ACQEDYKQ5GTAVCNFSM6AAAAABAFDVS7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRWGI4DQMRWGA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
For me the solution was very simple. I deleted the cookies for Telldus in the browser and then it was fine to configure and local API now works.
The problem
When I try to authenticate (Link accounts) on the TellStick I get an 404 error for /tellduslive/authorize This was working some time ago, but I have been using the Cloud until now recently when Telldus had some problems, ref #104376
What version of Home Assistant Core has the issue?
core-2023.11.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tellduslive
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tellduslive/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response