Can't start in HassIO x86 (can't find I2C)
See original GitHub issueI can’t start this in my HassIO (x86) install, just getting this in HassIO system logs:
20-02-21 22:08:16 INFO (SyncWorker_18) [hassio.docker.interface] Clean addon_6e66619d_room_assistant application
20-02-21 22:08:16 ERROR (SyncWorker_18) [hassio.docker] Can't start addon_6e66619d_room_assistant: 500 Server Error: Internal Server Error ("error gathering device information while adding custom device "/dev/i2c-1": no such file or directory")
Any ideas?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[add-on] HassOS I2C Configurator - Home Assistant OS
HassOS I2C Configurator This project enables the Raspberry Pi I2C bus from an addon. ... Hey, sorry getting this in the logs, cant...
Read more >Can't use folder_watcher · Issue #1599 · home-assistant ...
At start up I get an error: OSError: [Errno 28] inotify watch limit reached (relevant journalctl part pasted above). I get no events...
Read more >How to Install Home Assistant Supervised - OFFICIAL WAY
The big cons in Home Assistant Container is that you won't get the ... First start of the Home Assistant supervised will take...
Read more >How To Find Unknown I2C Addresses Several Ways - YouTube
After struggling to get a 128x64 OLED display working over I2C, I learned many things about I2C ... Your browser can't play this...
Read more >Lakshan – Latest Open Tech From Seeed
But this does not mean you have to buy them at launch if you already have smart ... X86 machine into a Matter...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh - just tried again, now it starts. Perhaps I was too fast and it hadn’t cleaned up completely before I started a new instance.
There hasn’t been any activity on this issue recently. In an effort to provide a better overview of current issues we automatically clean some of the old ones. Many of them may already be resolved in newer versions of room-assistant. This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.