Closed magickarle closed 2 months ago
sorry you can merge with https://github.com/home-assistant/addons/issues/3623. seem to be the same issue
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue you are experiencing
[12:16:09:634370] Info : Connecting to Secondary... [12:16:09:752000] Info : RX capability is 256 bytes [12:16:09:752009] Info : Connected to Secondary [12:16:09:755746] Info : Secondary Protocol v5 [12:16:09:755750] ASSERT : FATAL in function 'protocol_version_check' in file /usr/src/cpc-daemon/server_core/server_core.c at line #729 : Secondary Protocol v5 doesn't match CPCd Protocol v4 [12:16:10:756182] Info : Daemon exiting with status EXIT_FAILURE Logger buffer size = 28672, highwater mark = 2439 : 8.51%. Lost logs : 0 [12:16:10] INFO: CPC ended with exit code 1 (signal 0)...
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Silicon Labs Multiprotocol
What is the version of the add-on?
2.4.5
Steps to reproduce the issue
flashed firmware of z-station to release date 2024.04.22 Multiprotocole version on ubuntu
tested comm with sudo ./zme_cpc info -d /dev/ttyUSB1 -k my_binding_key
received: Openning port .............................. OK BINDING KEY: MY_BINDING_KEY VERSION PROTOCOL: 5.0 VERSION CPC: 4.4.2 VERSION CPC APP: UNDEFINED SECURITY: TRUE ENDPOINT: NCP ZIGBEE RCP OPEN TRED ...
unpluged and pluged to proxmox server (usb is pass-through using vendor/devince ID)
installed homeassistant addon Silicon Labs Multiprotocol
Confugured addon yaml with device: >- /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_012B7A55-if01-port0 baudrate: "115200" flow_control: false autoflash_firmware: false cpcd_trace: false otbr_enable: false otbr_log_level: notice otbr_firewall: false binding_key: my_binding_key
Got error in log.
Tested by reconfiguring zigbee radio (new serial port shows socket://core-silabs-multiprotocol:9999 - Multiprotocol add-on - Nabu Casa)
received "Unknown error occurred"
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1393 Downloaded Repositories | 15 HACS Data | okHome Assistant Cloud
logged_in | true -- | -- subscription_expiration | January 24, 2025 at 7:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | true remote_server | us-east-1-2.ui.nabu.casa certificate_status | ready instance_id | 7a33b81086bf4e0cb0e5898d6b9efe43 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.3 -- | -- update_channel | stable supervisor_version | supervisor-2024.06.0 agent_version | 1.6.0 docker_version | 25.0.5 disk_total | 30.8 GB disk_used | 18.5 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | kvm board | ova supervisor_api | ok version_api | ok installed_addons | Home Assistant Google Drive Backup (0.112.1), Z-Wave JS UI (3.7.1), flicd (2.0.3), Studio Code Server (5.15.0), Node-RED (17.0.13), Network UPS Tools (0.13.0), RPC Shutdown (2.5), ESPHome (2024.5.5), Terminal & SSH (9.14.0), eWeLink Smart Home (1.4.3), SQLite Web (4.1.2), Z-Wave.Me Add-on (v4.1.3), Silicon Labs Multiprotocol (2.4.5)Dashboards
dashboards | 2 -- | -- resources | 6 views | 13 mode | storageRecorder
oldest_recorder_run | May 27, 2024 at 1:44 PM -- | -- current_recorder_run | June 6, 2024 at 10:44 AM estimated_db_size | 445.68 MiB database_engine | sqlite database_version | 3.44.2Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
I seem to have a conflit on the protocole version. As well, can't find where i can put my UART binding key (as per log it says /etc/binding-key.key. My guess this is the path within the addon through docker)