foreign-sub / ha_fbx Goto Github PK
View Code? Open in Web Editor NEWHome assistant VM image for Freebox Delta (arm64)
License: GNU General Public License v3.0
Home assistant VM image for Freebox Delta (arm64)
License: GNU General Public License v3.0
Hello, thank you for your work
I have exactly the same problem as #1
Additional context
Version: hafbx-debian-2021.6.6.zip
I start with - [ /root/init_ha.sh, --with-hacs ]
(I didn't test without --with-hacs
yet)
Edit: no issue without --with-hacs
Describe the bug
ha_fbx default user "ha" does not have access to bluetooth as such when plugging a bluetooth usb dongle, bluetooth is not accessible in the VM or in HomeAssistant
To Reproduce
Expected behavior
ha user should have access to bluetooth in order for the docker to be able to access bluetooth too
Before I was using a regular Debian with HomeAssistant manually installed on it and the default user from this Debian VM already had access to bluetooth as such I had never faced this issue.
Now that I am using ha_fbx it looks like the default ha user is missing the bluetooth group to be able to use bluetooth correctly
Resolution
To solve this problem i had to add manually the ha in the bluetooth group with the command:
sudo usermod -a -G bluetooth ha
Then i rebooted the VM
After that bluetoothctl command works in the VM & in the HomAssistant Docker
And now HomeAssistant integrations using bluetooth like MiFlora work again
Could this group could be added by default to the ha user in future releases?
i install the image
and enter with ha and password
I seems that docker is not installed
I cannot connect to home assistant
thanks for your answer
Hi
Installing Debian HA 0.116.4 VM image for arm64
At the end of the init_ha.sh script I get Unit hassio-supervisor.service has a bad unit file setting
Any Idea to solve this ?
Regards
[Info] Install supervisor Docker container
[Info] Install supervisor startup scripts
[Info] Install AppArmor scripts
[Info] Run Hass.io
Failed to start hassio-supervisor.service: Unit hassio-supervisor.service has a bad unit file setting.
See system logs and 'systemctl status hassio-supervisor.service' for details.
In syslog
Oct 24 21:55:37 hafbx cloud-init[539]: Cloud-init v. 18.3 running 'modules:final' at Sat, 24 Oct 2020 21:51:37 +0000. Up 14.19 seconds.
Oct 24 21:55:37 hafbx cloud-init[539]: 2020-10-24 21:55:37,272 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/runcmd [1]
Oct 24 21:55:37 hafbx cloud-init[539]: 2020-10-24 21:55:37,275 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
Oct 24 21:55:37 hafbx cloud-init[539]: 2020-10-24 21:55:37,276 - util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed
Describe the bug
Bluetooth dongle fails after a few minutes after boot.
When I boot the VM and HA starts bluetooth communication works for a few minutes
Then every bluetooth device is out of order
I have logs in the console that a file in /sys/kernel/debug/bluetooth/hci0 already exists
Only solution to fix the issue is:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Bluetooth USB dongle should be stable
Screenshots
Here is the error under HA when it happens:
Logger: homeassistant.components.bluetooth.scanner
Source: components/bluetooth/scanner.py:286
Integration: Bluetooth ([documentation](https://www.home-assistant.io/integrations/bluetooth), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+bluetooth%22))
First occurred: 13:20:21 (14 occurrences)
Last logged: 13:33:21
hci0 (00:01:95:6D:90:46): Failed to restart Bluetooth scanner: hci0 (00:01:95:6D:90:46): Timed out starting Bluetooth after 15 seconds
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/bluetooth/scanner.py", line 241, in _async_start
await self.scanner.start() # type: ignore[no-untyped-call]
File "/usr/local/lib/python3.10/site-packages/bleak/__init__.py", line 156, in start
await self._backend.start()
File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/scanner.py", line 191, in start
self._stop = await manager.active_scan(
File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 360, in active_scan
reply = await self._bus.call(
File "/usr/local/lib/python3.10/site-packages/dbus_fast/aio/message_bus.py", line 370, in call
await future
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/bluetooth/scanner.py", line 240, in _async_start
async with async_timeout.timeout(START_TIMEOUT):
File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 129, in __aexit__
self._do_exit(exc_type)
File "/usr/local/lib/python3.10/site-packages/async_timeout/__init__.py", line 212, in _do_exit
raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/bluetooth/scanner.py", line 374, in _async_scanner_watchdog
await self._async_start()
File "/usr/src/homeassistant/homeassistant/components/bluetooth/scanner.py", line 286, in _async_start
raise ScannerStartError(
homeassistant.components.bluetooth.scanner.ScannerStartError: hci0 (00:01:95:6D:90:46): Timed out starting Bluetooth after 15 seconds
Here is the error under the console of the VM when this happens
Additional context
Bluetooth USB dongle model: UD100-G03
Describe the bug
When installing a fresh image of ha_fbx there is an issue with network_manager
As such we are getting errors in supervisor
23-09-20 22:10:11 WARNING (MainThread) [supervisor.resolution.evaluations.base] NetworkManager is not correctly configured (more-info: https://www.home-assistant.io/more-info/unsupported/network_manager)
Also it seems that because of this installing addons is not possible because HA thinks there is no internet
To Reproduce
Steps to reproduce the behavior:
Expected behavior
NetworkManager should work normally and HA should be able to connect to internet to download addons
I am unable to restore my HomeAssistant to it's normal operation because of this. How can it be fixed?
unable to install SSH plugin, or MariaDB, or Samba Share...
Describe the bug
Since Home Assistant 2022.11.1 / Supervisor 2022.10.2 a warning "Unsupported system - Systemd Journal issues" appears.
To Reproduce
apt upgrade
)The warning appears.
Expected behavior
No warning
Screenshots
Additional context
I tried to run apt install systemd-journal-remote -y
but it won't start
ha@hafbx:~$ systemctl status systemd-journal-remote
● systemd-journal-remote.service - Journal Remote Sink Service
Loaded: loaded (/lib/systemd/system/systemd-journal-remote.service; indirect; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2022-11-04 11:54:55 CET; 38min ago
TriggeredBy: ● systemd-journal-remote.socket
Docs: man:systemd-journal-remote(8)
man:journal-remote.conf(5)
Process: 7896 ExecStart=/lib/systemd/systemd-journal-remote --listen-https=-3 --output=/var/log/journal/remote/ (code=exited, status=1/FAILURE)
Main PID: 7896 (code=exited, status=1/FAILURE)
Error: 13 (Permission denied)
Nov 04 11:54:55 hafbx systemd[1]: Started Journal Remote Sink Service.
Nov 04 11:54:55 hafbx systemd-journal-remote[7896]: Failed to read key from file '/etc/ssl/private/journal-remote.pem': Permission denied
Nov 04 11:54:55 hafbx systemd[1]: systemd-journal-remote.service: Main process exited, code=exited, status=1/FAILURE
Nov 04 11:54:55 hafbx systemd[1]: systemd-journal-remote.service: Failed with result 'exit-code'.
Bonjour,
Tout d'abord merci pour votre travail, voici le problème que je rencontre :
Describe the bug
L'installation ne dure qu'environ 15 minutes et se termine sur :
"[1326.484303] cloud-init[1518]: HA onboardind ready @ http://hafbx.local:8123"
"[1326.488954] cloud-init[1518]: Waiting for home assistant setup"
Puis un reboot looongtemps après
Mais aucune page n'est présentée sur [ipdemaVM]:8123 après le reboot
To Reproduce
Je pense avoir "bien" suivi plusieurs fois la procédure standard (sans cloud-init) avec la version 2024.2.2
Expected behavior
Je pensais que l'installation allait durer 20 minutes et se terminer par l'exposition d'une page sur l'addresse [ipdemaVM]:8123
Comment être certain que l'installation est bien terminée ?
Additional context
Je suis sur une Freebox Ultra et pas Delta
EDIT : Ca fonctionne, j'ai du gérer des problèmes de dépendances qui remontaient dans /var/log/cloud-init-output.log
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.