HomeMatic CCU - Homematic Devices need to be resettet after reboot of CCU

[DunklerPhoenix]

The problem

All my HomeMatic devices (not the gateway) need to be resetted after a restart of CCU otherwise the devices can't connect to CCU.
There is no re-learning needed because after the reset of the devices they connect themself again.

Environment

Used devices:
2x HmIP-SRH
1x HMIP-SWDO
Gateway: HmIP-RFUSB

• Add-on with the issue: HomeMatic CCU
• Add-on release with the issue: <=11.0.6
• Last working add-on release (if known): -
• Operating environment (OS/Supervised): Hassio 5.10 | core-2021.1.5 | supervisor-2021.01.7 | HA Blue

Problem-relevant configuration

rf_enable: false
wired_enable: false
hmip_enable: true
rf:
  - type: CCU2
    device: >-
      /dev/serial/by-id/usb-Silicon_Labs_eQ-3_HmIP-RFUSB_3014F738C3-if00-port0
wired:
  - serial: xy
    key: abc
    ip: 192.168.0.0
hmip:
  - type: HMIP_CCU2
    device: /dev/ttyUSB0
regahss_reset: false

[miktin]

Same Problem hear. After restart all Devices Not work. You can see them in Devices but not work anymore.

[awehmeier]

Same behavior here and on a friends HA. ELV HMIP usb stick and Hass.io. Only homematic device reset helps. Until the next reboot. The last time it happened when I updated the homematic plug-in.

[B1ob]

I have the same problem. I noticed the following:
Every time the addon is booting it tries to update the firmware of my USB stick and fails.

[INFO] Performing update with firmware file '/firmware/HmIP-RFUSB/hmip_coprocessor_update-2.8.6.eq3' ...
ERROR: HmIP update 2.8.6 fails!

I guess that this maybe resets the USB stick, resulting in a loss of the connection.
In my case I have a "HmIP-RFUSB-TK" which is not compatible with the flashing according to this post:
https://homematic-forum.de/forum/viewtopic.php?f=56&t=47158&start=60#p483636

Can you confirm that you really have a "HmIP-RFUSB" and not the Telekom "-TK" Version?

[DunklerPhoenix]

@B1ob I have the real one and not the TK version

[awehmeier]

I can confirm as well. Not the Telekom one. Ordered directly. Am 9. Feb. 2021, 11:46 +0100 schrieb B1ob <notifications@github.com>:

…

I have the same problem. I noticed the following: Every time the addon is booting it tries to update the firmware of my USB stick and fails. [INFO] Performing update with firmware file '/firmware/HmIP-RFUSB/hmip_coprocessor_update-2.8.6.eq3' ... ERROR: HmIP update 2.8.6 fails! I guess that this maybe resets the USB stick, resulting in a loss of the connection. In my case I have a "HmIP-RFUSB-TK" which is not compatible with the flashing according to this post: https://homematic-forum.de/forum/viewtopic.php?f=56&t=47158&start=60#p483636 Can you confirm that you really have a "HmIP-RFUSB" and not the Telekom "-TK" Version? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[miktin]

Is Original from ELV

[rabesocke]

I have the same problem and opened already an issue for that (#1743).

I have the Telekom version of the USB-stick.

[koslo]

I also bought the telekom stick in 2019 and it did not work with OCCU. After researching in the internet the stick seems to work only with the Telekom system and the interface might be closed. After that I sent it back and bought the original.

I also have the described problem from the beginning. Sometimes the control of my radiator thermostat works and later again not.

[rabesocke]

Well, the Telekom stick itself is working. I added all my thermostats (because of the bug described here) several times and there was no problem at all with the stick.

I only get the same log message like B1ob in #1783 (comment) - but the stick is working for me until there is a restart of Home Assistant or the whole system.

Where did you find these information? At the moment I cannot agree to that.

[koslo]

Ok. Cool, it seems to work by now. In 2019 the stick wasnt recognized. So there was no way to connect devices. I read it in occu forum or the fhem forum... I don't know anymore.

[DunklerPhoenix]

With the normal stick I don't know what to do. It's shitty to reset all devices every reboot xD

[rabesocke]

With the normal stick I don't know what to do. It's shitty to reset all devices every reboot xD

It’s the same situation with the Telekom stick 😒

[koslo]

As I wrote, I have had the problems from the beginning. I always thought it had something to do with the one percent rule of the devices. That after a restart too much data is sent back and forth. Some device are connected after a few minutes or hours 😄 .

[koslo]

But it is really annoying when you want to control the device and nothing happens. Now I am at the point to test the Cloud AP i got with my last starter set.

[B1ob]

I played a little bit more with my HmIP-RFUSB-TK...
I managed to get the following addon up and running.
https://github.com/jens-maus/RaspberryMatic/wiki/Installation-HomeAssistant
Therefore I think the problem is not related to the Telekom version of the stick.
At least the first few reboots seamed to work without problem.
Only the updating of the stick also reports an error.

[DunklerPhoenix]

@B1ob Thank you for the hint.
I switched to RaspberryMatic and it works like a charm :3
All functions are reachable and the devices are active direct after reboot.

Ah and the Update Manager looks like this with the normal stick:

Identifying Homematic RF-Hardware: ....HmRF: none, HmIP: HMIP-RFUSB/USB, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: 2.8.6, OK

[awehmeier]

Same here so far. With the RaspberryMatic all stable. 👍🏻

[stale]

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.

[sh-hilden]

Please reopen, I got the same error

[DunklerPhoenix]

Use RaspberryMatic