Closed befantasy closed 5 years ago
oh, sorry. forgot a very important information. the ubuntu was deploy in a ARM based android TV box by using linux deploy 2.07.
Not sure, but i think the python from ppa is the problem. https://community.home-assistant.io/t/warning-ubuntu-16-04-python3-6-from-ppa/52436?u=vdrainer
@VDRainer Thanks for your help. I searched and saw your post in homeassistant forum before. It's a very useful reminder. so I didn't run apt-get update & upgrade in the host environment. And I think the problem you mentioned is the host python environment changed led to the virtual environment broke down. In my case, the python virtual environment is ok so is pip.
I solved the issue above by updating broadlink separately (pip3 install --upgrade broadlink), that updates pycryptodome as well and that error disappears.
but its still not working (this is on 0.68.1), I upgraded from 0.66.x which worked fine.. please help
2018-05-09 20:23:22 ERROR (MainThread) [homeassistant.components.switch] Error while setting up platform broadlink
Traceback (most recent call last):
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\site-packages\homeassistant\helpers\entity_platform.py", line 129, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\asyncio\tasks.py", line 406, in wait_for
return fut.result()
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\asyncio\futures.py", line 294, in result
raise self._exception
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\concurrent\futures\thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\site-packages\homeassistant\components\switch\broadlink.py", line 168, in setup_platform
broadlink_device = broadlink.mp1((ip_addr, 80), mac_addr, None)
TypeError: __init__() takes 3 positional arguments but 4 were given
2018-05-09 20:23:23 ERROR (MainThread) [homeassistant.components.switch] Error while setting up platform broadlink
Traceback (most recent call last):
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\site-packages\homeassistant\helpers\entity_platform.py", line 129, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\asyncio\tasks.py", line 406, in wait_for
return fut.result()
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\asyncio\futures.py", line 294, in result
raise self._exception
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\concurrent\futures\thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "C:\Users\User\AppData\Local\Programs\Python\Python35-32\lib\site-packages\homeassistant\components\switch\broadlink.py", line 143, in setup_platform
broadlink_device = broadlink.rm((ip_addr, 80), mac_addr, None)
TypeError: __init__() takes 3 positional arguments but 4 were given
example of my mp1 config which is now failing:
- platform: broadlink
host: 192.168.0.110
mac: '00:11:22:33:44:55'
type: mp1
friendly_name: 'MP1'
slots:
# friendly name of slots - optional
# if not set, slot name will be switch's friendly_name + 'slot {slot_index}'. e.g 'MP1 slot 1'
slot_1: 'a'
slot_2: 'b'
slot_3: 'c'
slot_4: 'd'
How do hassio users solve the issue though. No pip available.
@MACscr: yes you can solve it. Just install the ssh addon and you're good to go.
Nope. Those packages are available in hassio.
On Aug 9, 2018, at 8:09 PM, effelle notifications@github.com wrote:
@MACscr: yes you can solve it. Just install the ssh addon and you're good to go.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
@MACscr, I'm a bit confused. your wrote "how do hassio user solve the issue [...]", then seems your are not on hassio. To see if I can help you would you gently tel me what hass you've installed?
Sorry, I meant are not available on hassio. The packages needed to compile the third party fixes, etc.
On Aug 10, 2018, at 6:12 AM, effelle notifications@github.com wrote:
@MACscr, I'm a bit confused. your wrote "how do hassio user solve the issue [...]", then seems your are not on hassio. To see if I can help you would you gently what hass you've installed?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Understood @MACscr. Depending on what install you've done could be an alternative solution. Yuo've installed on a Pi using the image? Pure Docker? Curl and Hypervisor?
Stock hassio install on an sd card and used within a Pi. Nothing fancy. I went with hassio as I wanted something officially supported and no hacks and workarounds that some other flavors might required or could be blamed on the OS, etc. In this case, the components came from the home-assistant team.
On Aug 10, 2018, at 6:12 AM, effelle notifications@github.com wrote:
@MACscr https://github.com/MACscr, I'm a bit confused. your wrote "how do hassio user solve the issue [...]", then seems your are not on hassio. To see if I can help you would you gently what hass you've installed?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/14310#issuecomment-412064090, or mute the thread https://github.com/notifications/unsubscribe-auth/ABVwECqB2JsbUcWPqFErtqFblEcHfVL0ks5uPXixgaJpZM4Tz7zA.
@MACscr, as far as I remember (I'm not using a Pi anymore) hassio is using python 3.x on stock SD image, then you should be able to install pip3... If you haven't already tried open a terminal and install it with
sudo apt-get update && sudo apt-get install python3-pip
Please be advice there are some issues with the newest version of broadlink package on docker version starting from 0.74 that could be affecting your install too. I filled a bug report here (with the solution too). There a second solution: give some time for the dev team, since there is a pull request opened after my report to update the offending packages.
They use a custom os. Apt isn’t available
On Aug 11, 2018, at 6:32 AM, effelle notifications@github.com wrote:
@MACscr, as far as I remember (I'm not using a Pi anymore) hassio is using python 3.x on stock SD image, then you should be able to install pip3... If you haven't already tried open a terminal and install it with
sudo apt-get update && sudo apt-get install python3-pip
Please be advice there are some issues with the newest version of broadlink package on docker version starting from 0.74 that could be affecting your install too. I filled a bug report here (with the solution too). There a second solution: give some time for the dev team, since there is a pull request opened after my report to update the offending packages.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I'm curious Mark, since I'm not on Pi but probably I'll buy one just for hass...
Is there the tab of hassio addons like on docker version?
If yes, there is the terminal with all the commands you need.
Again, I'm just curious!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍
Home Assistant release with the issue:
0.68.1 0.68
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Ubuntu 16.04 LTS python3.6.5 //ppa:jonathonf/python-3.6 python-venv pip 10.0.1
Component/platform:
Description of problem: Could not connect to boradlink RM.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
It seems that there is a dependence problem in recent releases. I tried several times with totally clean installation in venv environment for 0.68.1/0.68/0.67. "python-jose-cryptodome" 1.3.2 require "pycryptodome<3.4.0,>=3.3.1", but after I downgrade the "pycryptodome" to 3.3.1 I got the other notice: several components require "pycrytodome==3.4.11"...