-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Telldus Live does not work in 0.57 #10326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi! Similar or same issue. Always had errors due to tellduslive, but now only some of my stuff works. Motion sensors, z-wave, do but switches, 433 and z-wave, do not. Regards,
|
No, sorry, my sensors don't work either. I just see them in the frontend since they're customized... |
Returned to .56.2, everything back to normal including old errors.
|
@pappajohan - the WARNING about Unidentified device type you report in #10326 (comment) is probably resolved by #10106 The other issue (the requests library) seems to be a dependency problem. |
Thanks @molobrakos, that's why I was excited to try .57 to see if the warnings disappeared. Anything I could do? BTW, did you see #8747? |
Hi, same issue on 0.57.1 here. BR
|
Could perhaps be related to #9876 ? |
It seems that upgrading to Python 3.6 is a workaround (see #10353). |
Great news, will absolutely try after work! Thanks! /Johan |
Sorry @molobrakos, I just realized I'm not sure what "a dependency problem" means. My most common error lately, I think, is:
which I think is the same as #8130, but I'm not sure. I thought that was connected to the warnings regarding "Unidentified device type", probably without reason. Is that what You meant? |
Same error in 57.2
|
@pappajohan, the |
Has anyone verified that upgrading to Python 3.6 will help? |
Have you tested to update all required packages i.e.
Or rather, revert requests (2.18.4) to version 2.14.2 according to: #10353 (comment)
|
Dunno where to run this from, that file exists nowhere on my debian-system..
That did the trick though |
I am not sure, but a problem could be that the dependency library (tellduslive) pins specific versions of requests/requests_oauth? https://github.com/molobrakos/tellduslive/blob/27a366f3ae9bf36c75224879377d7a6e723bb19a/requirements.txt |
But good that it is working now. @molobrakos close this as |
I don't want to close it if it requires manual intervention. |
pip3 install requests==2.14.2 worked for me too. |
The
|
I've removed the version pinning of requests in the tellduslive library anyway, hoping that it will solve this issue. |
Hi! Can’t get 0.58.1 to work with or without pip3 install requests==2.14.2, but maybe I messed up something else by now..? Reverted to 0.56.2 which works. /Johan |
Even the states of lights and switches are affected and does not always update. Requires restart of HASS for the to update. I am really looking forward to this fix henice my whole system is dependant upon Tellduslive. Thanks for all the hard work @molobrakos ! (Running HASSIO 1.1 with the latest update, 0.58.1) |
Wasn’t sure if I messed up something else, so I tried again. 0.58.1 started without errors after the requests==. However, 7 hours later everything Telldus went unavailable and; Linux hassbian 4.9.59+ #1047 Sun Oct 29 11:47:10 GMT 2017 armv6l The programs included with the Debian GNU/Linux system are free software; Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent /Johan |
I have no idea why this problem occur for some users. Upstream bug seems is filed here: requests/requests-oauthlib#299 To sum it up it seems to be more of a configuration problem (I suspect it might have to do something with Hassbian). |
@molobrakos, correct! The TypeError: unsupported operand type(s) for &: 'NoneType' and 'int' is the one I was having. I am 100% tellduslive.py error free at this stage! <3 |
I’m very grateful. I cannot however see any dead sensors, only a dummy switch to control a lua script and a group besides 433- and z-wave switches and motion sensors. Two of my neo coolcam sensors don’t report lux even though they should, will remove them just in case. Or did you mean I should install Cython and DTLSSocket? Kind regards, |
Reading on my phone... Ok, yes, my error is the “packages/requests_oauthlib/init.py", line 9, in Will try what ScuttleSE said... ;-) |
@pappajohan Go to Events, create a event and drag and drop a sensor, in the drop down list, do you have many empty rows? (See pictures from my previous pose above). If so, contact support and ask Telldus to clean for you. I have informed them about this issue and the compability problems with HASS. They are aware of this issue. |
Thanks! No empty rows on my iPhone, will see tonight if it’s browser specific. Also downgraded homeassistant to 0.58.0, pip3 install Cython and DTLSSocket, pip3 — upgrade and restarted home assistant. Same errors... |
The same thing on the computer @tubalainen ... Registered a ticket with Telldus anyway. @ScuttleSE, any advice..? |
Please try to reinstall from scratch, have HASS discover your telldus unit(s) and then parse the configuration manually? If you still experiencing problems please check with Telldus Support. They are aware of HASS and the issues with the API. New firmware for the telldus units are in early beta and will be released momentarily that will address ghost sensors and other known issues. I cannot replicate your specific error, please try to do a complete reinstall and see if it helps. I have two telldus units, a "shit load" of sensors and switches, currently running "local API". It works like a charm, not a single error. Under the latest version of HASSIO (0.59.1).... It all started to "work like a charm" after telldus cleaned out the dead ghost sensors (that I had a "shitload of" as well). |
Thanks! I tried a clean install, hassbian 1.31, and also removed hass, installed Cython and installed mentioned sw before reinstalling. Tried with discovery and manually. I guess I’m doing something stupid... After upgrading tellduslive it reverts to previous version. How do you change that? |
I still have the same problem in Hassbian 0.59.1
I made a fresh install of HassIO and on 0.58.1 telldus live worked fine with old settings (public key and more), After a upgrade to 0.59.1 i had to use the new settings with OAuth and that worked fine. On my Hassbian install i never get the notification to OAuth telldus live, only the error even if i use the new setting. Just upgraded my Hassbian to latest 0.59.2 and same problem still. But now i noticed that even if i comment out "#tellduslive:" and restart HASS i still get the error. |
Thanks @mcfrojd for pointing that out, using hassio now. I would prefer hassbian, but at the moment it just doesn't work. /Johan |
@mcfrojd, Home Assistant will discover your Tellstick on the local network and automatically load the To sum it up, the problem ( |
@molobrakos , at least the mentioned error occur on Hassbian and not on hassio. I guess that could be a good reason to try "the ultimate home automation hub"for a while... :-) Really, I'm super happy at the moment, but I'll keep my Hassbian on another card and will gladly try any other idea to get it working again. Regards, |
@molobrakos At least for me, (i have not tried the tellduslive on a fresh install of hassbian) |
Same issue here as well, running Hassbian with 0.59.2 - fresh install - nothing is setup, fails from discovery. no tweaks done is configuration yet either.
If API keys is suppose to be defined in configuration.yaml, then i would strongly suggest adding that to the documentation of the component as well. |
I don't feel like installing Hassbian to debug this issue, but I am curious, what happens if you run this on your Hassbian installation, in the Hass virtual environment:
|
Hi,
On my production system, Regards PH |
If
|
Install Requests version 2.14.2: Install Requests_oauthlib version 0.8.0 Then the command printed out the versions - But this did not help with the setup. Still says:
|
Could it be that you must switch to the virtual Python environment first? I think this is how I got it to work. BR |
|
That worked for me as well! Thanks @leifmariposa ! |
Works perfect now =) |
This problem persists in 0.60. @mcfrojd solution still works. |
Upgraded from 0.59.2 to 0.60 and got this problem. Had to install requests 2.14.2 to get it working again. |
Hi. This problem still exist, but @mcfrojd fix works just fine. I would like to add they changed how HASS connects to Tellduslive. From 0.58 you dont need the keys, you get promted with this after adding only You can read more here: |
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
): 0.57.0Python release (
python3 --version
): Python 3.5.3Component/platform: Telldus Live
Description of problem: Telldus Live component throws an error when HA starts up
Expected:
Telldus Live should work...
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
The text was updated successfully, but these errors were encountered: