Open MTrab opened 4 years ago
Huh, I tested the add-on on my NUC without i2c as well and didn't run into problems there. Anyway, I put up a hot fix for this that just removes the mapping until I can figure this out. You will need to uninstall the add-on, refresh the add-on store and then re-install it again. Don't forget to copy your config if you already had something setup.
Still same error - tried both stable and beta.
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.
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.
@MTrab Got the same error. Can you describe the steps you have taken to make it work? Thanks.
fyi: I talked with the Home Assistant Supervisor devs and currently there is no way to make an add-on that supports both machines with and without i2c device. While ultimately I would like to help them get this developed I think for now the easiest solution is to just offer a new add-on version (like the beta) that also maps the i2c device.
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.
I can't start this in my HassIO (x86) install, just getting this in HassIO system logs:
Any ideas?