HAOS 16.x breaks access to /dev/hidraw0 in HACS integration

[tarosk]

Describe the issue you are experiencing

After upgrading to HAOS 16.2 or 16.3, [Jablotron 100 integration] (https://github.com/kukulich/home-assistant-jablotron100) cannot read /dev/hidraw0 correctly. Either there is change in access to devices or some other process interferes the communication (e.g. writes to the device thus breaking the protocol).

Downgrade to HAOS 15.2 resolves the issue.

Error logged in HAOS 16.3 Home Assistant Core log:

Logger: custom_components.jablotron100
Source: custom_components/jablotron100/jablotron.py:468
integration: Jablotron 100 (documentation, issues)
First occurred: 6:46:10 PM (1 occurrence)
Last logged: 6:46:10 PM
Service unavailable: [Errno 5] I/O error

Traceback (most recent call last):
File "/config/custom_components/jablotron100/jablotron.py", line 468, in _detect_central_unit
self._central_unit = reader.result(STREAM_TIMEOUT)
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/concurrent/futures/_base.py", line 456, in result
return self.__get_result()
~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/jablotron100/jablotron.py", line 421, in reader_thread
raw_packet = stream.read(STREAM_PACKET_SIZE)
OSError: [Errno 5] I/O error

What operating system image do you use?

yellow (Home Assistant Yellow)

What version of Home Assistant Operating System is installed?

16.3

Did the problem occur after upgrading the Operating System?

Yes

Hardware details

Jablotron 100 Security control panel attached via USB. This was working in up to HAOS 15.2

Steps to reproduce the issue

1. Upgrade to HAOS 16.3 (from 15.2)
2. Jablotron 100 custom integration stops working

Anything in the Supervisor logs that might be useful for us?

Havent found anything related in Supervisor log.

Error logged in HAOS 16.3 Home Assistant Core log:

Logger: custom_components.jablotron100
Source: custom_components/jablotron100/jablotron.py:468
integration: Jablotron 100 ([documentation](https://github.com/kukulich/home-assistant-jablotron100), [issues](https://github.com/kukulich/home-assistant-jablotron100/issues))
First occurred: 6:46:10 PM (1 occurrence)
Last logged: 6:46:10 PM
Service unavailable: [Errno 5] I/O error

Traceback (most recent call last):
  File "/config/custom_components/jablotron100/jablotron.py", line 468, in _detect_central_unit
    self._central_unit = reader.result(STREAM_TIMEOUT)
                         ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/concurrent/futures/_base.py", line 456, in result
    return self.__get_result()
           ~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/jablotron100/jablotron.py", line 421, in reader_thread
    raw_packet = stream.read(STREAM_PACKET_SIZE)
OSError: [Errno 5] I/O error

Anything in the Host logs that might be useful for us?

no

System information

System Information

version	core-2025.11.1
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	aarch64
user	root
virtualenv	false
python_version	3.13.9
os_name	Linux
os_version	6.12.47-haos-raspi
arch	aarch64
timezone	Europe/Vienna
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	2402
Downloaded Repositories	3

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 16.3
update_channel	stable
supervisor_version	supervisor-2025.11.1
agent_version	1.7.2
docker_version	28.3.3
disk_total	234.7 GB
disk_used	54.1 GB
nameservers	192.168.11.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	yellow
supervisor_api	ok
version_api	ok
installed_addons	Advanced SSH & Web Terminal (22.0.0), File editor (5.8.0), MariaDB (2.7.2), Duck DNS (1.26.0), Home Assistant Google Drive Backup (0.112.1), Studio Code Server (5.19.3), ESPHome Device Builder (2025.10.4), Matter Server (8.1.1)

Dashboards

dashboards	3
resources	0
views	5
mode	storage

Network Configuration

adapters	lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth4e2eeef (disabled), veth474248e (disabled), veth3ed51a2 (disabled), veth6cdb25d (disabled), vethd084bd4 (disabled), veth3468da0 (disabled), veth93bf165 (disabled), vethb29a9ff (disabled), vethf6ab846 (disabled)
ipv4_addresses	lo (127.0.0.1/8), end0 (192.168.11.55/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth4e2eeef (), veth474248e (), veth3ed51a2 (), veth6cdb25d (), vethd084bd4 (), veth3468da0 (), veth93bf165 (), vethb29a9ff (), vethf6ab846 ()
ipv6_addresses	lo (::1/128), end0 (fe80::1f32:e684:d493:c705/64), docker0 (fe80::dc85:fcff:fe47:84a0/64), hassio (fe80::48e1:faff:fecc:7429/64), veth4e2eeef (fe80::ace0:40ff:febc:b7fe/64), veth474248e (fe80::f062:6bff:fe10:9aa1/64), veth3ed51a2 (fe80::e84d:c9ff:fe3f:36dc/64), veth6cdb25d (fe80::c63:ccff:fea0:7eab/64), vethd084bd4 (fe80::ecd7:7ff:feef:d5e6/64), veth3468da0 (fe80::b0f8:4cff:feda:7c76/64), veth93bf165 (fe80::b0ea:24ff:fe3c:ef79/64), vethb29a9ff (fe80::344b:84ff:fe2e:d631/64), vethf6ab846 (fe80::e00a:57ff:fe60:ba86/64)
announce_addresses	192.168.11.55, fe80::1f32:e684:d493:c705

Recorder

oldest_recorder_run	October 16, 2025 at 8:25 AM
current_recorder_run	November 9, 2025 at 6:45 PM
estimated_db_size	2083.97 MiB
database_engine	mysql
database_version	10.11.6

Additional information

No response

[sairon]

Strange, it's working fine for me on RPi 5 🤔

I see in the linked issue that the integration author reports it's working fine on RPi 4 as well. Are you using CM4 or CM5 in your Yellow?

[tarosk]

I am on yellow with CM4 (CM4008032). One non standard difference is I migrated system from SD card to m2 SSD.

Is there any more diagnostic info I can provide?

[GitHubR32]

I am on yellow with CM5. I can confirm the same issue.

[sairon]

@tarosk @GitHubR32 Thank you, seems we have some pattern now. I will check if I can replicate it with Yellow and if not, let you know what's needed for further troubleshooting.