Home assistant addon migration: no devices with HMIP-RFUSB-TK
See original GitHub issueDescribe the issue you are experiencing
After migrating from the official home assistant addon I don’t see any homematic-ip devices. Restoring the backup complains about a missing *.apkx file
Describe the behavior you expected
All my homematic-ip devices in the new addon
Steps to reproduce the issue
- Create backup in old homematic addon
- Stop old addon
- install new addon
- import backup
What is the version this bug report is based on?
3.61.7.20220115
Which base platform are you running?
ha-addon (HomeAssistant Add-on)
Which HomeMatic/homematicIP radio module are you using?
HmIP-RFUSB
Anything in the logs that might be useful for us?
Mounting /data as /usr/local (Home Assistant Add-On): OK
Identifying onboard hardware: oci, OK
Initializing RTC Clock: onboard, OK
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: OK: backup successfully restored
Initializing System: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.3, OK
Identifying Homematic RF-Hardware: ....HmRF: none, HmIP: HMIP-RFUSB-TK/USB, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: 2.8.4=>4.4.16, ERROR (2.8.4 != 4.4.16); HMIP-RFUSB-TK: 2.8.4, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: not required
Starting rfd: no BidCos-RF hardware found
Starting HMIPServer: ............OK
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: OK
Starting Third-Party Addons: OK
Starting crond: OK
Setup onboard LEDs: booted, OK
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (8 by maintainers)
Top Results From Across the Web
Addons not connected after migration to SSD - Configuration
So I installed a new Home Assistant on the SSD via RPI Imager. ... But when I got to the addon log there...
Read more >How to migrate to ESPHome add-on?
From release notes 2022.4: The ESPHome Home Assistant addon repository is added by default to new Home Assistant installations.
Read more >Migrating to new hardware - Addons won't start!
I'm trying to move from an RPi3 to an RPi4. I made a backup and powered off the old system. When powering on...
Read more >How to migrate to ESPHome add-on? - #21 by gaz99
Change the addon not the integration. The addon you use to create ESPHome devices is the only thing that has moved.
Read more >Hassio - Migration to Fresh Installation - Zigbee2Mqtt Addon ...
Hello, i wanted to migrate from a Hassio SD Card Installation on the RPI4 ... The Addon has the same config, the same...
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
Feel free to edit the documentation yourself. That’s exactly why this is a wiki!
@Nokius Try to ignore that message and reboot the Add-on right away. Then have a look if everything is back. This error can occur if you don’t have any homematic rf module connected to the Add-on while restoring the backup.