Homematic Variables not working

[nicx]

I added homematic module to my configuration, but the "Variables" are not working. I expect them on my host ccu2 as attributes, but the host has absolutely no attributes :(

I tried this config according to https://home-assistant.io/components/homematic/:

homematic:
  interfaces:
    wireless:
      host: 192.168.0.13
      resolvenames: json
      username: Admin
      password: xxx
      primary: true
      variables: true

and I also tried this:

homematic:
  interfaces:
    rf:
      host: 192.168.0.13
      resolvenames: json
      username: Admin
      password: xxx
  hosts:
    ccu2:
      host: 192.168.0.13
      username: Admin
      password: xxx
      primary: true
      variables: true

and this:

homematic:
  interfaces:
    wireless:
      host: 192.168.0.13
      resolvenames: json
      username: Admin
      password: xxx
      primary: true
      variables: true

and different other possibilities for the option "variables", but none is working. I always get the error

2018-01-11 10:17:34 ERROR (MainThread) [homeassistant.config] Invalid config for [homematic]: [variables] is an invalid option for [homematic]. Check: homematic->homematic->hosts->ccu2->variables. (See /config/configuration.yaml, line 73). Please check the docs at https://home-assistant.io/components/homematic/

[nicx]

In addition I get the message:

2018-01-11 11:05:53 ERROR (SyncWorker_3) [pyhomematic._hm] RPCFunctions.jsonRpcPost: Exception: Invalid \escape: line 1 column 58 (char 57)

Semms like there is something generally broken :(

[pvizeli]

homematic:
  interfaces:
    rf:
      host: 192.168.0.13
      resolvenames: json
      username: Admin
      password: xxx
  hosts:
    ccu2:
      host: 192.168.0.13
      username: Admin
      password: xxx
      primary: true
      variables: true

remove the primary and variables

[danielperna84]

The exception you see within the logs is actually a bug in the CCU itself. If you're using RaspberryMatic there has been a fix added recently: jens-maus/RaspberryMatic#239
To fix this in the CCU eq3 would need to take care of this.

[nicx]

@pvizeli I already tried your configuration as mentioned in my post, but I just tried it again: I get this error:

2018-01-15 08:58:11 ERROR (MainThread) [homeassistant.config] Invalid config for [homematic]: [primary] is an invalid option for [homematic]. Check: homematic->homematic->hosts->ccu2->primary. (See /config/configuration.yaml, line 73). Please check the docs at https://home-assistant.io/components/homematic/

if I remove the "primary" option I get this error:

2018-01-15 09:01:28 ERROR (MainThread) [homeassistant.config] Invalid config for [homematic]: [variables] is an invalid option for [homematic]. Check: homematic->homematic->hosts->ccu2->variables. (See /config/configuration.yaml, line 73). Please check the docs at https://home-assistant.io/components/homematic/

I think there is a bug in the component regarding to the changes in the last weeks:
https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/homematic
#11156

[danielperna84]

You have to remove primary AND variables. Both options are deprecated.

[nicx]

@danielperna84 I have already tried that and the errors are gone. But how can I get the variables of the CCU2 back to HA?

[danielperna84]

Have a look at the entity overview in the Home Assistant UI. There you should have an entity called homematic.ccu2. You can use that entity to access the variables. This part of the documentation give a similar example for doing this with thermostats. The same can be done with you ccu-entity.

[nicx]

@danielperna84 unfortunately its not working as describedmin the linked documentation. I tried it as described in your article https://community.home-assistant.io/t/homematic-modul-read-write-system-variables/3577/12 too, but I cannot see any variable in the frontend if I click on the ccu2 entity and even the template test: {{ states.homematic.ccu.attributes.Test }} is not working with a Test boolean variable defined on my ccu.

What could I else do to find the problem?

[danielperna84]

Which Home Assistant version are you running at currently?
I have 0.60.1 and I get this:

So just like in the linked thread in the forum. I would also suggest to move this discussion to the forum, since it's not really an issue if it's working for others.

[nicx]

@danielperna84 I use 0.60.1 too. Any other ideas? Ay possibility to get more logs?
will move the discussion to the forum tomorrow, that is a good idea.

[nicx]

In addition here is the messages log of my CU2:

Jan 16 08:48:32 homematic-ccu2 user.err rfd: XmlRpc fault calling system.listMethods({"homeassistant-wireless"}) on http://192.168.0.10:53184/RPC2:[faultCode:1,faultString:"<class 'TypeError'>:system_listMethods() takes 1 positional argument but 2 were given"]
Jan 16 08:48:33 homematic-ccu2 user.err rfd: XmlRpc fault calling system.listMethods({"homeassistant-ccu2"}) on http://192.168.0.10:53184/RPC2:[faultCode:1,faultString:"<class 'TypeError'>:system_listMethods() takes 1 positional argument but 2 were given"]
Jan 16 08:48:34 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=GAS_POWER failed getting physical value.
Jan 16 08:48:34 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=POWER failed getting physical value.
Jan 16 08:48:34 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=ENERGY_COUNTER failed getting physical value.
Jan 16 08:48:34 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=GAS_ENERGY_COUNTER failed getting physical value.
Jan 16 08:48:35 homematic-ccu2 user.err rfd: XmlRpcClient error calling newDevices({"homeassistant-ccu2",{[ADDRESS:"BidCoS-RF",CHILDREN:{"BidCoS-RF:0","BidCoS-RF:1","BidCoS-RF:2","BidCoS-RF:3","BidCoS-RF:4","BidCoS-RF:5","BidCoS-RF:6","BidCoS-RF:7","BidCoS-RF:8","BidCoS-RF:9
Jan 16 08:48:35 homematic-ccu2 user.err rfd: XmlRpc fault: [faultCode:1,faultString:"<class 'KeyError'>:'resolvenames'"]

[nicx]

still no solution, the community thread you can find here: https://community.home-assistant.io/t/homematic-variables-not-working/39449/6

[danielperna84]

As mentioned in the community-thread, this is a known bug of the CCU, not Home Assistant or pyhomematic. Closing the issue here.