Bonjour,
L’un d’entre vous a t’il réussi à intégrer l’équipement SIN-4-2-20 par NodOn sous ZHA ?
J’ai fait de nombreuses tentatives (appairage) sans pouvoir finaliser !
Aucune entité de disponible.
Ma configuration
System Information
version |
core-2025.2.5 |
installation_type |
Home Assistant OS |
dev |
false |
hassio |
true |
docker |
true |
user |
root |
virtualenv |
false |
python_version |
3.13.1 |
os_name |
Linux |
os_version |
6.6.73-haos |
arch |
aarch64 |
timezone |
Europe/Paris |
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 |
1564 |
Downloaded Repositories |
14 |
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 14.2 |
update_channel |
stable |
supervisor_version |
supervisor-2025.02.4 |
agent_version |
1.6.0 |
docker_version |
27.2.0 |
disk_total |
28.0 GB |
disk_used |
7.0 GB |
healthy |
true |
supported |
true |
host_connectivity |
true |
supervisor_connectivity |
true |
ntp_synchronized |
true |
virtualization |
|
board |
green |
supervisor_api |
ok |
version_api |
ok |
installed_addons |
Samba share (12.5.0), File editor (5.8.0), Duck DNS (1.18.0), Terminal & SSH (9.16.0), Mosquitto broker (6.5.0), SQLite Web (4.3.1), VLC (0.3.0), eWeLink Smart Home (1.4.3), tydom2mqtt (3.6.0) |
Dashboards
dashboards |
5 |
resources |
8 |
views |
25 |
mode |
storage |
Network Configuration
adapters |
lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethae0693a (disabled), veth490391f (disabled), veth30f3d8f (disabled), veth8586d89 (disabled), vethebb1d1c (disabled), vethf1869f7 (disabled), vethbb73d99 (disabled), veth472c813 (disabled), vethf8dbabc (disabled), vethd1c5206 (disabled), vethf44c1e1 (disabled), veth547fdc4 (disabled), veth20a3792 (disabled) |
ipv4_addresses |
lo (127.0.0.1/8), end0 (192.168.1.23/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethae0693a (), veth490391f (), veth30f3d8f (), veth8586d89 (), vethebb1d1c (), vethf1869f7 (), vethbb73d99 (), veth472c813 (), vethf8dbabc (), vethd1c5206 (), vethf44c1e1 (), veth547fdc4 (), veth20a3792 () |
ipv6_addresses |
lo (::1/128), end0 (2a01:cb18:80c0:7c00:f6da:647e:8bc6:3242/64, fe80::1e41:28e8:cdd3:a80a/64), hassio (fe80::42:79ff:fe07:ea16/64), docker0 (fe80::42:80ff:feed:24f/64), vethae0693a (fe80::285d:39ff:fe42:c38a/64), veth490391f (fe80::bc5e:a2ff:fe5c:a0bb/64), veth30f3d8f (fe80::2c0b:e2ff:fed1:805d/64), veth8586d89 (fe80::8885:35ff:fe08:d274/64), vethebb1d1c (fe80::ec2d:cfff:fef6:247f/64), vethf1869f7 (fe80::3816:aff:fe6f:2adb/64), vethbb73d99 (fe80::482a:4cff:fe04:6103/64), veth472c813 (fe80::9c20:a9ff:fe8a:91a0/64), vethf8dbabc (fe80::a0cf:1dff:febe:7b08/64), vethd1c5206 (fe80::f440:c4ff:fe10:f41/64), vethf44c1e1 (fe80::b4a4:32ff:fedf:f73a/64), veth547fdc4 (fe80::50d6:5dff:fe5d:8d05/64), veth20a3792 (fe80::6477:b8ff:feda:4b01/64) |
announce_addresses |
192.168.1.23, 2a01:cb18:80c0:7c00:f6da:647e:8bc6:3242, fe80::1e41:28e8:cdd3:a80a |
Recorder
oldest_recorder_run |
17 février 2025 à 17:40 |
current_recorder_run |
3 mars 2025 à 17:40 |
estimated_db_size |
108.01 MiB |
database_engine |
sqlite |
database_version |
3.47.1 |
___
Au final tout est rentré dans l’ordre après avoir attendu au moins 2 à 3 heures à la suite du dernier appairage. Sauf le Micrologiciel qui lui reste toujours « Inconnu » (indisponible).
Voici toutes les entitées :
light.nodon_sin_4_2_20_lumiere
binary_sensor.nodon_sin_4_2_20_ouverture
select.nodon_sin_4_2_20_comportement_au_demarrage
light.nodon_sin_4_2_20_lumiere_2
binary_sensor.nodon_sin_4_2_20_ouverture_2
select.nodon_sin_4_2_20_comportement_au_demarrage_2
button.nodon_sin_4_2_20_identifier
button.adeo_sin_4_1_20_lex_identifier (unknown)
update.nodon_sin_4_2_20_micrologiciel (unknown)