Since upgrade to 0.60 Homematic is not working anymore...?!

Configuration
1

Just did an update to 0.60. I managed after hours to set up a config that seems to be valid (after all the changes in the chnagelog of 0.60)
But it’s not recognizing any of my devices…if I try to activate in th config resolvenames:json, I always receive an error. Also I had to change IP -> host in the config…
Does anybody know how I will get my devices back in homeassistant?

Any help is appreciated!

2

I also loose my homematic devices. Perhaps my config is not correct.

homematic:
  interfaces:
    wireless:
      host: 192.168.0.6
      resolvenames: json
#      username: Admin
#      password: !secret homematic_hhs_pw
#      primary: true
#      variables: true
  hosts:
    ccu2:
      host: 192.168.0.6
      username: Admin
      password: !secret homematic_hhs_pw
3

There was a breaking change in .60.

4

Hi atomicpapa,
I also read there’s a change in the chnaglog. But it really seems that I’m too dumb to get the settings changed in acorrect way, so that it’s working again…Could you please help me on that?
I have one single CCU2 and want it connected to my hassio. Sounds not too complex… But I don’t get it managed…?!
Here my config:

# homematic:
  interfaces:
    wireless:
      host: 192.168.1.6
      resolvenames: json
    hosts:
      CCU2:
        host: 192.168.1.6
#        port: 2001
        username: *****
        password: *****
#      variables: true 
#      path: /groups

Additional info: this is in a separted inculde file. not directly in the configuration.yaml. Therefore homematic is set to a comment.

5

I have the same issue since 0.60

6

This one is working for me:

   #homematic:
  interfaces:
    CCU2:
      host: 192.168.1.6
      port: 2001
      resolvenames: json
#      username: ******
#      password: *****
  hosts:
    Zentrale CCU2:
      host: 192.168.1.6
      username: ******
      password: *****

IT seems that for

interfaces

user/password isn’t implemented, yet? Seems that it was already fixed for the next version:
https://github.com/home-assistant/home-assistant/pull/11214

If the name of the CCU2 is the same for interfaces and hosts, then no devices will be shown in the hassio…this is the reason why I have different names for that.
What I dont really understand is, what are the possibilities with the devices below “hosts”. Is it just for “monitoring” the CCU2? because some interactions seems not to be possible?

2 Likes
7

Thanks for the hints @RainyHome.

Too bad this got released in this state - it completely wrecked my setup due to the missing user/pw for json based name resolving… sigh Hope they push 0.60.1 soon.

1 Like
8

Since every try with HA Version > 0.59.2 i have problems with the variables of the homematic component.

The Configuration Validation is invalid when i put the parameter primary and variables in my configuration.yaml. (hassio 0.60.1)

I hope for a hint!
Thanx Oliver

homematic:
  interfaces:
    rf_hhs:
      host: 192.168.0.6
      resolvenames: json
      username: Admin
      password: !secret homematic_hhs_pw
#      primary: true
#      variables: true
9

Try it like this:

homematic:
  interfaces:
    rf_hhs_rpc:
      host: 192.168.0.6
      resolvenames: json
      username: Admin
      password: !secret homematic_hhs_pw
  hosts:
    rf_hhs_ccu:
      host: 192.168.0.6
      username: Admin
      password: !secret homematic_hhs_pw

I still haven’t upgraded to 0.60 yet, so I’m not sure if this is correct. But from looking at the code that should be what is required. The main change is, that within the interfaces-block you have hosts that provide the XML-RPC API, and in the hosts-block you optionally can add higher level devices (CCU) for extended functionality (variables).

10

Thank you. I didn’t realized that the config variable (variable: true) is no longer needed.

My last problem was the change in the automation (service: homematic.set_variable_value instead service: homematic.set_var_value)

11

Perhaps it is a problem i my specific environment. I have 2 homematics (CCU2 and raspberrymatic) each in one location. The networks are linked per vpn. Since i update to HA 0,60,1 my HA/Homematic combination is unstable, because HA loose the „contact“ to some not all homematic devices.

How stable ist your HA/homematic system?

12

Stability shouldn’t be impacted. Under the hood everything is working still pretty much the same as before. If the CCU or Raspberrymatic stop working, then this sounds like a networking issue. You haven’t mentioned it, but my guess would be, that the one connected via VPN is the problem. If your internet connection is dropped (it’s quite common to have reconnects with german providers), that can interrupt the connection which is established across the tunnel. But that should have been a problem even before 0.60.

13

The problem homematic is the raspberrymatic and is in the same network. The ccu2 at the other location has no problem but control only some homematic devices.

The raspberrymatic with the problems is connected to a netgear orbi satellite. i test to connect the raspberry to a wired network.

We will see.

Thank you for the support and tips.
Oliver

14

Yes, a wired connection is definitely preferred. It’s not the first time I’ve heard of people having problems with wireless connections. And maybe 0.60 introduced something that puts more load on the wifi chip and therefore interrupts the connection. When that happens you can try to use the homematic.reconnect service to reconnect to raspberrymatic. That way you may not have to restart HA completely.

15

One thing I just discovered:
For some reason events seem to not arrive at the CCU when I set the log level for pyhomematic less verbose than INFO. So for example motion sensors work without any issues when logging at INFO, but when reducing to WARNING they stop working.