You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have moved 200 HmIP devices from a CCU3 to the RaspberryMatic. The reason was the desired connection to a Synology NAS for data backup, the provision of a second system and curiosity. The move and the connection to the NAS worked without any major problems. Our house is quite large and unfortunately the ceilings are insulated with silver foil. That's why I use several FBs and Hue Bridges.
Now my question: I linked the CCU3 to the main bridge a long time ago. Over time, I have put two more Hue Bridges into operation. Unfortunately, I no longer know whether the devices registered on these bridges were added to Homematic as devices after a restart of the CCU3 or during operation, I mean they simply appeared in the inbox. In any case, I can now also control the Hue devices via the CCU3. When I reassigned my IP addresses, I noticed that a manual pairing did not find any Hue bridges other than the main bridge and that the bridges already found had to keep their original IP address so that their devices would continue to work, they were also displayed with changed IP addresses. This feature was not lost during backups and restores.
I can still see these devices in the RaspberryMatic, but it is no longer possible to control them.
How can I manage to control these devices under the RaspberryMatic in the same way as under the CCU3?
A side note on another topic. When restoring to the RaspberryMatic, I used an automatic backup rather than a specially created one. This was already a few days old and during the device firmware update (which has been running for months) a device had been updated by the CCU3 between the backup and restore of this backup. The RaspberryMatic took the old value as the number of pending updates - I would have thought that the devices themselves would know their firmware status and the CCU3/RaspberryMatic would query this status.
The text was updated successfully, but these errors were encountered:
I have moved 200 HmIP devices from a CCU3 to the RaspberryMatic. The reason was the desired connection to a Synology NAS for data backup, the provision of a second system and curiosity. The move and the connection to the NAS worked without any major problems. Our house is quite large and unfortunately the ceilings are insulated with silver foil. That's why I use several FBs and Hue Bridges.
Now my question: I linked the CCU3 to the main bridge a long time ago. Over time, I have put two more Hue Bridges into operation. Unfortunately, I no longer know whether the devices registered on these bridges were added to Homematic as devices after a restart of the CCU3 or during operation, I mean they simply appeared in the inbox. In any case, I can now also control the Hue devices via the CCU3. When I reassigned my IP addresses, I noticed that a manual pairing did not find any Hue bridges other than the main bridge and that the bridges already found had to keep their original IP address so that their devices would continue to work, they were also displayed with changed IP addresses. This feature was not lost during backups and restores.
I can still see these devices in the RaspberryMatic, but it is no longer possible to control them.
How can I manage to control these devices under the RaspberryMatic in the same way as under the CCU3?
A side note on another topic. When restoring to the RaspberryMatic, I used an automatic backup rather than a specially created one. This was already a few days old and during the device firmware update (which has been running for months) a device had been updated by the CCU3 between the backup and restore of this backup. The RaspberryMatic took the old value as the number of pending updates - I would have thought that the devices themselves would know their firmware status and the CCU3/RaspberryMatic would query this status.
The text was updated successfully, but these errors were encountered: