You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you already mentioned yourself, the pairing process needs to be performed manually. It would be cool to have it automated.
To let other users know how to do the pairing with using the Docker components (Supervisor), do the following:
Install the "SSH & Web Terminal" component using the Supervisor frontend (Supervisor/Add-on Store, then search for it)
Configure the add-on so that you can log in
Log in via SSH or Home Assistant frontend
Execute the following command to log in to the homeassistant image: docker exec -it homeassistant /bin/bash
Now you can pair your device(s) as described here. Note that you need to either cd into the site-packages folder and then run pyhton pybecker... or you use the absolute filename, in my case python /usr/local/lib/python3.8/site-packages/pybecker.
When all the configuration is done, you should configure your configuration to be stored in the /config folder instead of the current location in the site-packages folder to be able to upgrade Supervisor without loosing your configuration. I described this in issue Configuration lost after upgrade #7
I hope this descriptions helps someone, cause it took me some time to find this out 😀.
The text was updated successfully, but these errors were encountered:
You can also do pairing using the becker.pair service call in Home Assistant, e.g. manually from the developer tools. That's likely easier for most people compared to running from the command line.
As you already mentioned yourself, the pairing process needs to be performed manually. It would be cool to have it automated.
To let other users know how to do the pairing with using the Docker components (Supervisor), do the following:
Supervisor/Add-on Store
, then search for it)docker exec -it homeassistant /bin/bash
cd
into thesite-packages
folder and then runpyhton pybecker...
or you use the absolute filename, in my casepython /usr/local/lib/python3.8/site-packages/pybecker
./config
folder instead of the current location in thesite-packages
folder to be able to upgrade Supervisor without loosing your configuration. I described this in issue Configuration lost after upgrade #7I hope this descriptions helps someone, cause it took me some time to find this out 😀.
The text was updated successfully, but these errors were encountered: