nachiarg
(Nachiarg)
May 15, 2017, 1:47pm
1
Hi, Im getting errors using the speedtest sensor. Same configuration in hassbian works perfectly.
“2017-05-15 02:30:01 ERROR (<concurrent.futures.thread.ThreadPoolExecutor object at 0x74d1cff0>_6) [homeassistant.components.sensor.speedtest] Error executing speedtest: Command ‘[’/usr/local/bin/python’, ‘/usr/local/lib/python3.6/site-packages/speedtest.py’, ‘–simple’]’ returned non-zero exit status 1.”
I have the same error. A call in the container gives more informations :
docker exec -ti homeassistant bash
bash-4.3# /usr/local/bin/python /usr/local/lib/python3.6/site-packages/speedtest.py --simple
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/speedtest.py", line 19, in <module>
import re
File "/usr/local/lib/python3.6/re.py", line 142, in <module>
class RegexFlag(enum.IntFlag):
AttributeError: module 'enum' has no attribute 'IntFlag'
pvizeli
(Pvizeli)
May 22, 2017, 9:51am
3
Is fix with homeassistant docker 0.45
DaleRobins
(Dale Christian Aeron Robins)
May 23, 2017, 5:09pm
5
Got speedtest working, however there is one small issue, the Raspberry Pi ethernet port is too slow!
So kind of pointless on this really
I’m still having this error in 0.45.1. Is anyone else still having it?
I had it in 0.45, and still have it in 0.46, both docker.
pvizeli
(Pvizeli)
June 6, 2017, 9:59am
8
Do you try Hass.IO docker image or the official?
Maybe try to see here:
removing enum34 worked for me. Haven’t seen anything acting up with that dependency removed yet.
Seems that removing package enum34 might fix this problem (and break something else, so be careful)
I’ve been running the homeassistant/home-assistant image.
pvizeli
(Pvizeli)
June 6, 2017, 8:59pm
11
That is not relevant to hass.io
vkorn
(Vlad Korniev)
June 29, 2017, 4:36pm
12
Any plans to include this fix into hass.io ?
1 Like
pvizeli
(Pvizeli)
June 30, 2017, 4:40pm
13
Should be fix with next hass version
1 Like
vkorn
(Vlad Korniev)
July 3, 2017, 8:03pm
14
0.48 here, still same error
pvizeli
(Pvizeli)
July 3, 2017, 8:05pm
15
You can provide a PR to fix it. If you are fast, it can go into 0.48.1 docker build
Maby the other docker build have already a temporary fix for that.
mak
(mak)
July 4, 2017, 3:01am
16