This is probably the breaking point for me moving away from Telldus after all the recent troubles. If anyone has any interesting alternatives to share that would be great. I have a Tellstick Net, so local access is not possible.
Well i guess it´s time to start migrating my Zwave devices.
But i do not know of a good replacement to handle my 333 MHz plugs. Just a few so maybe the best is to replace them with zwave.
They tell us API access will stop working as well for basic subs.
I´m using the Telldus live with local set up. Do you think that will make a difference? i just need it as a bridge actually.
After ten plus years I’ve been moving away from Telldus for some years now. With new owners the race downhill started. I’m not sure how much of a solution this may bring; Bypass Telldus Live in Home Assistant – Lucas TechBlog but I’m prepared to test it for the few devices still left in Telldus Live. Worst case, repair the few remaining devices.
Almost all my old 433 MHz temp sensors are replaced with Zigbee ditto plus a few more. The outdoor sensors was the hardest to find replacement for so it had to be Hue Motions Sensors.
I got the same email about Teldus shutting down api access for non premium subscribers and thought local api access might still work. But as was said before it is possible this could be disabled to. That would be a very mean move. I like my tele stick v2 it does 443 and zwave. I have around 8 built in zwave dimmers around the house and multiple 443 plugs that are all working great with IOS Integration in homeassistant. I don’t want to change the in wall dimmers or the plugs so I started looking at building a zwave and 443 solution for raspberry pi. With zwave I found a simple hat that will take care of that. 443 was a different animal though. It seems (to me at least) the easiest way will be to repurpose an old remote for the 443 devices
To follow up on my last post there also maybe a hardware hack for the telestick to connect it directly to the gpio of a raspberry pi. I only just thought of this will see in April what happens. If they disable local api I hope not
Telldus has made a serious misstep by believing that they can charge their customers 36 euros per year for products that, let’s be honest, don’t work all that well. At the same time, a revolution is taking place with new players that Telldus will never be able to match, who are introducing new products with vastly different quality and user interfaces than Telldus. I am left with the same feeling as when an unnamed despot invaded Ukraine; don’t they understand the consequences? Do they really think anything good will come of it, and will the people of Ukraine embrace this new policy? This is definitely the death knell for Telldus, and it’s sad, but that’s just how it is. All of my searches are now focused on how to get away from the company with as little loss as possible, because it cannot be denied that I have already invested a lot in poor Telldus equipment.
So the 24th came and went. Before this I downloaded all configuration from Teldus api in the hope I may be able to use it in the future. Up until this point I had been taking the easy route and had HA running in a container. I had been lazy and left all scheduling to the Teldus app. Knowing what was going to happen I made some time to migrate to a full HAOS installation. This did not go as expected however I try raspberry pi imager would not write a working HAOS SD card. I gave up on this and installed Debian instead and did a HA core install on this. Then installed a scheduling integration and this works exactly how I want. I probably should have done this sooner. So now I have Teldus to thank for upgrading there API to subscribers only this encouraged me to take the time and do a full HAOS install
For what is worth, the local API still works perfectly fine. In fact I haven’t noticed any difference with automations so far. I can still control the smart plugs both in HA and in the Google Home app.
One stopped for me, but one still works … but the one not updating works fine locally (it shows temp and humidity on the little screen). So probably just a faulty unit or something. Haven’t looked into it further as I’m replacing all Telldus related objects
Hmm, even though they stated April 24th 2023 as the cutoff date, my Telldus integration in Home Assistant was working fine up until now… I tried reloading the integration in an effort to get stuff working but I think that was the final nail in the coffin as I now seem to be completely shut off from their API.
There is however if anyone’s interested a project to intercept sensor values still:
It was a bit tricky to set up but that’s still working for me at least. So if anyone’s reading this and your Telldus integration is still working - do not reload it