Homematic TRVs showing as n/a after restart

Configuration
1

Hi all,
I have installed Raspberrymatic and have successfully added 5 TRVs.
They are visible and accessible on my Lovelace dashboard where I can control their setpoint temperature, see the current temperature or select programs.
However, after each restart they are unavailable in Lovelace, showing N/A everywhere.

Only after I go to Raspberrymatic and select one of them and for example change the temperature they become available in Lovelace as well. Sometimes they also seem to loose the connection when switching from manual to auto mode. But this does not happen every time.

Does this have to do with the V_last_reboot script and automation? I have followed the instructions (even the latest update where homematic was replaced with raspberrymatic in the template) but either this has got nothing to do with the solution or something is not working.
Also the sensor which should show the time and date of the last reboot always shows 01.01.1970 00:00. Is this the way it should be?

I love the integration but would like to fix this. Would very much appreciate your help.

Thanks and regards,

Merc

2

Looks like your V_last_reboot script is not working correctly and therefore the update after a restart is not happening.
You need to check all the steps again.

I am now using debmatic instead of raspberrymatic, where this script does not seem to be needed, so can’t help you more specific.

3

Hi WallyR,
yes…something is not right…but I (thought I had) copied over everything just as in the descriptions…

So…here is what I have.
In Raspberrymatic this is what I see in the system variables table:

V_Last_Reboot
V_Last_Reboot1439×577 16.1 KB

To me this means that the scrip in RaspberryMatic does, what it should.

Now, in Homeassistant I have got the following entry in configuration.yaml:

template:
    sensor:
    - name: Raspberrymatic last reboot
      state: "{{ state_attr('homematic.raspberrymatic', 'V_Last_Reboot') or '01.01.1970 00:00:00' }}"
      icon: "mdi:clock"

and this automation:

- id: 'raspberrymatic_reboot_detection'
  alias: Raspberrymatic CCU Reboot
  description: ''
  trigger:
  - platform: state
    entity_id: sensor.raspberrymatic_last_reboot
  action:
  - service: homematic.reconnect
    data: {}
  mode: single

What am I doing wrong?

Thanks,

Merc

4

Check the entity homematic.raspberrymatic in your developer tools and see if the timestamp for last reboot is correct.
It might be that HA does not like capital letters in the names, but its just a guess.

5

Hi WallyR,
well that is what confuses me a bit.
First of all there is no entity called homematic.raspberrymatic. There is one though that is called “sensor.raspberrymatic_last_reboot” and this one shows the value of 01.01.1970 00:00:00.

So I wonder why it has that name and also why it does not pick up the right time stamp…

6

Do you have a service called homematic.reconnect and does bring back the TRVs when you call it?

7

The service exists and is called through an automation. but I do not have the feeling that this has an effect.
To improve the situation I am now setting the TRV mode to manual on every startup of HA. That seems to move them into active mode.

8

Can you call it manually?
You have to do successive test and find out which parts that are working and try to box in the error.

9

When I call it manually the TRVs still show n/a. On the other hand when I use the automation to set them all to manual heating the get active, and stay.

10

Your service call to reconnect seems to fail somehow.
Try and look at the logs right after you called itlook at both the logs in HAs configuration menu and in the HACS logs too.