VMBPIRO not taking temperature parameter into account

English
1

Hi,

I’m having 4 VMBPIRO devices in my Velbus installation. However it looks like only one unit is not correctly behaving.
The issue I’m seeing is that this one unit is sending very often (I believe when the temperature is changing) his data and not taking into consideration it’s parameters
I’ve tried to change the parameters to only send it once a minute (which did work out for the other 3)
Do you know if you can force the configuration to be applied?

I’ve noticed in the VelbusLink program that this parameter is not read out form the VMBPIRO module, since after a readout of the module the field “Auto-Send of temperature” is always unknown (also for the 3 working modules)

I’ve checked if there were any firmware update required but this is all ok for these modules

Log output from the SensorTemperature (faulty unit is the address: 15)
Screenshot from VelbusLink with VMBPIRO address 15 and the unknown parameter
Screenshot from VelbusLink with VMBPIRO address 0x11 and the unknown parameter

Screenshot 2021-11-30 at 13.46.06
Screenshot 2021-11-30 at 13.46.061246×725 43.5 KB

Screenshot 2021-11-30 at 13.47.57
Screenshot 2021-11-30 at 13.47.571247×729 45.3 KB

SensorTemp.log (4.5 KB)

2

a full rewrite might help… (clear the just changes only checkbox)

3

Just tried a full rewrite
steps followed:

  • First read module
  • Full write (unchecked write only changes)

But still same issue

2021-11-30 17:35:31 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 8.375, “min”: 127.5, “max”: 8.5625}

2021-11-30 17:35:41 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 8.375, “min”: 127.5, “max”: 8.5625}

2021-11-30 17:35:47 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 8.375, “min”: 127.5, “max”: 8.5625}

2021-11-30 17:35:54 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 8.375, “min”: 127.5, “max”: 8.5625}

2021-11-30 17:35:57 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 8.375, “min”: 127.5, “max”: 8.5625}

2021-11-30 17:35:57 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 42, “rtr”: false, “cur”: 8.875, “min”: 127.4375, “max”: 19.4375}

2021-11-30 17:36:03 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 8.375, “min”: 127.5, “max”: 8.5625}

Now I have noticed at the moment you change the parameter"Auto-send of temperature" I see data written on the CAN bus

4

Try changing the autosend value from “unknown” to the value you want. I think it is sent immediately without synchronizing.

5

Indeed, this is already what I’ve tried. But I don’t see any difference in behaviour

Next to that I think that this setting is also incorrectly read from the VelbusLink program (since it’s always set as ‘unknown’)

Is there a way to ‘factory reset’ the module?

6

Yes there’s a factory reset in the module. But this will remove all the settings you’ve made in that module.
Can you send us your velbus project (vlp) in a private message? We’ll have a look at what the value is for autosend.

7

We will investigate this further.

It looks like the problem may be resolved if you set the lightsensor autosend to “whenever it changes”. That’s the only difference we found between the VMBPIRO that sends too many packets comparing with the other VMBPIRO’s which are welbehaving.

8

Ok, let me change these parameters. I’ll post an update later today with the feedback

9

I’ve changed the parameters (from all my VMBPIRO devices) to the following partakers:
Temperature: Send when changed
Light Value: Send when changed

Now when I look to the output in the log file then I see still a lot of changes for the 0x0F
Just a wild guess, but could it be that the resolution for the temperature reading is too sensitive? Since looking what I have receive this is only temperature data from the 0x0F modules.

Do you want me to make the changes to only transmit x seconds?
admin@nasstation:/volume1/@appdata/homeassistant$ tail -f homeassistant.log | grep SensorTemperatureMessage
2021-12-07 14:58:23 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 14:58:38 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 14:58:54 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.375, “min”: 127.4375, “max”: 9.0}
2021-12-07 14:59:10 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 14:59:25 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.375, “min”: 127.4375, “max”: 9.0}
2021-12-07 14:59:41 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 14:59:57 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:00:12 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:00:28 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:00:44 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:00:59 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:01:15 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:01:31 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:01:46 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:02:02 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:02:18 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:02:33 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:02:49 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:03:05 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:03:20 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:03:36 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 9.0}

10

Just quickly changed the parameters (only for the Temperature) to sending every 30sec.
Still I see the 0x0F being sending data more often than the other once
So looks like this unit is still having somewhere some issue:

admin@nasstation:/volume1/@appdata/homeassistant$ tail -f homeassistant.log | grep SensorTemperatureMessage
2021-12-07 15:09:57 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 42, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 22.6875}
2021-12-07 15:10:03 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 17, “rtr”: false, “cur”: 4.1875, “min”: 127.375, “max”: 22.625}
2021-12-07 15:10:10 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:10:13 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:10:15 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 23, “rtr”: false, “cur”: 5.0625, “min”: 127.9375, “max”: 9.875}
2021-12-07 15:10:26 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:10:27 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 42, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 22.6875}
2021-12-07 15:10:33 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 17, “rtr”: false, “cur”: 4.1875, “min”: 127.375, “max”: 22.625}
2021-12-07 15:10:37 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.1875, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:10:41 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:10:43 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:10:45 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 23, “rtr”: false, “cur”: 5.125, “min”: 127.9375, “max”: 9.875}
2021-12-07 15:10:51 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 17, “rtr”: false, “cur”: 4.1875, “min”: 127.375, “max”: 22.625}
2021-12-07 15:10:57 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 42, “rtr”: false, “cur”: 4.3125, “min”: 127.4375, “max”: 22.6875}
2021-12-07 15:10:57 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:11:03 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 17, “rtr”: false, “cur”: 4.1875, “min”: 127.375, “max”: 22.625}
2021-12-07 15:11:13 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:11:13 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 15, “rtr”: false, “cur”: 4.25, “min”: 127.4375, “max”: 9.0}
2021-12-07 15:11:15 INFO (velbus-process-reader) [velbus] New message: {“name”: “SensorTemperatureMessage”, “priority”: 251, “address”: 23, “rtr”: false, “cur”: 5.0625, “min”: 127.9375, “max”: 9.875}

11

ok, last guess

Now I have changed back all settings to be sending when changed. Also I did a “Factory Defaults” on the module 0x0F
But still seeing same behaviour.

Please also see below the log form velbusLink
07/12/2021 15:17:00.352 RECV 0F FB 0F 02 E5 00 00 04
07/12/2021 15:17:00.352 RECV 0F FB 0F 07 E6 08 60 08 40 08 80 C2 04
07/12/2021 15:17:16.009 RECV 0F FB 0F 02 E5 00 00 04
07/12/2021 15:17:16.024 RECV 0F FB 0F 07 E6 08 40 08 40 08 80 E2 04
07/12/2021 15:17:31.602 RECV 0F F8 0F 04 00 00 14 00 D2 04
07/12/2021 15:17:31.681 RECV 0F FB 0F 02 E5 00 00 04
07/12/2021 15:17:31.681 RECV 0F FB 0F 07 E6 08 60 08 40 08 80 C2 04
07/12/2021 15:17:47.337 RECV 0F FB 0F 02 E5 00 00 04
07/12/2021 15:17:47.337 RECV 0F FB 0F 07 E6 08 60 08 40 08 80 C2 04
07/12/2021 15:18:02.993 RECV 0F FB 0F 02 E5 00 00 04
07/12/2021 15:18:03.009 RECV 0F FB 0F 07 E6 08 60 08 40 08 80 C2 04
07/12/2021 15:18:18.915 RECV 0F FB 0F 02 E5 00 00 04
07/12/2021 15:18:18.915 RECV 0F FB 0F 07 E6 08 60 08 40 08 80 C2 04

12

Your last log indicates that something else is requesting the temperature to be sent.

13

In my last log file I had fully disabled the home assistant, so it should have been something from the Velbus itself.
Is there a way to see this in the log file of the VelbusLInk program?
Do you think it’s useful to have the VelbusLink running for some minutes and if I share the log file?

14

I’ve disabled HA for now and see in the VelBusLink if I’m still receiving the data from the modules with address 0x0F, looks like I’m still receiving it very frequently (where I don’t have it from the other modules).
I would image seeing the request (as you stated) from another module to request the temperature.

Can you indicate me which module would be requesting the temperature of module 0x0F?

velbuslink_10-12-2021.log (4.2 KB)

15

Looks like multiple modules are doing so. Check the VMBGPOD’s > Configuration > Temperature. The temperature is listed there. Please note, these modules request the temperature to dipslay the temperature on one of the pages.

16

You are correct that they are shown on the VMBGPOD, but why is this based on polling if the module can send the data (or on time interval or when changed)