Support for Velbus Home Automation

A Velbus thermostat in HA is not needed and it will not solve the many errors you have.
If you use the temperature of your modules in another application, then I do not understand how it can work without having an address assigned for the temperature channel.
Here is an example of one of my modules configuration in Velbuslink:
image
It has 2 addresses 17 and 18 where 18 is the address for the temp channel. If this ‘18’ is not there, then the Velbus integration will also not create a channel for it and any temperature messages passing on the bus coming from this module will cause an error in the log (Don’t know if temp messages can be send out on the bus if no address is assigned for it). In case you do not have an address for the temperature channel, then its best that you do this in Velbuslink.

The fact that you get so many errors in the logs is not the intention and other people are working on the integration to catch errors like this but this is still under development.

Here is how my temperature modules look like: image

I was not the one to design the software, I have no clue how they have done it, but it does retrieve the temp for every switch.

How can I add an address for the temperature channel in VelbusLink?

In Velbuslink click/select a module then press F3 or right click and select change address from the context menu.
In my case it looks like this:
image
In your case you can’t use contiguous addresses because your modules are one next to the other in the address range. Not sure if you can use non-contiguous addresses, but you can try to select an empty address.

Just out of curiosity, what custom software do you use ?

FYI
Current temp is sent out on the module’s base address.

Thermostat “button events” like heater / boost / pump etc are sent out on the thermostat sub address.

Velbuslink really doesn’t care which sub address is used.

I can’t speak for HomeAssistant

(OpenRemote, openHAB & Control4 don’t care which is used)

Thanks for that info Stuart.

@1aranzant : I did a test on my system. I removed the thermostat address from one module and I get the same error as you in the logs. That means that you can resolve your log problem by assigning all thermostat addresses unfortunately. Later, you can remove all these unwanted thermostats in HA.
I noticed that a module will respond to a temperature request even if the thermostat address is not assigned. The temperature channel is also removed in Velbuslink when the thermostat address is removed, and this is why the HA Velbus integration generates this error.
Thanks for reporting this issue, it will help to improve the Velbus integration.

@Cereal2nd : I’ll create an issue for this in velbusaio.

2 Likes

The software is made by a Belgian company called Trigrr: Trigrr - Building Operating System

Thanks again for the help!

I’d be very interested to know how you are getting on with that.

I’ve got a meeting planned with them in the new year.

I believe it was called Bezonia.

1 Like

Hey Geert :smiley:

Yeah, Trigrr bought Bezonia a few years ago.

I thought it was a big commercial building control platform.

Apparently, Bezonia chose to only apply base addresses to Velbus modules and do all the logic centrally.

(One of the questions I’ll be asking…)

Hey Stuart. Long time no see sir. If you want info on Bezonia. Let me know. The guys who built it. I know them……

1 Like

Hi everyone,

I wanted to do the below automation; but what is the best way to send a direct % to a VMB4DC? The “automation” part only allows dim up or down but does not specify a percentage

In essence - I want to set the DIM value to 100% during the day and to 20% during the night - based on the VMBPIRO Dark Channel output… and the trigger for the light to go on

and any word on the Thermostat Mode (Heating/Cooling?)

Use ‘Turn on’, then you will have a brightness setting:

2 Likes

I see in the source code for the thermostats (climate) that we do not expose the thermostat cooling mode at all,

Is there a quick guide on programming (editting this? ) … Happy to test out some changes…

    _channel: VelbusTemp
    _attr_supported_features = (
        ClimateEntityFeature.TARGET_TEMPERATURE | ClimateEntityFeature.PRESET_MODE
    )
    _attr_temperature_unit = UnitOfTemperature.CELSIUS
    _attr_hvac_mode = HVACMode.HEAT
    **_attr_hvac_modes = [HVACMode.HEAT]**
    _attr_preset_modes = list(PRESET_MODES)

Where I think that could be: (as per hass_nibe/climate.py at master · elupus/hass_nibe · GitHub)

    _channel: VelbusTemp
    _attr_supported_features = (
        ClimateEntityFeature.TARGET_TEMPERATURE | ClimateEntityFeature.PRESET_MODE
    )
    _attr_temperature_unit = UnitOfTemperature.CELSIUS
    _attr_hvac_mode = HVACMode.HEAT
   **_attr_hvac_modes = [HVACMode.HEAT, HVACMode.COOL]**
    _attr_preset_modes = list(PRESET_MODES)

This will be fixed in 2023.2

2 Likes

the port on my Velbus Server has changed - how can I easily change the port in the HomeAssistant / Velbus configuration?

below ar the steps:

  • stop hass
  • go to the config folder
  • find the .storage dir the config_entries file
  • in this file search for velbus and udpate the connection string
  • restart hass
3 Likes

thanks!.. just for the ones that want to do this, make sure to do it from a direct SSH console - not the web interface SSH add-on (:wink: )

and on HA OS, you need to go to cd ./config/.storage

1 Like

Hello Danny, I just tried your fix, i.e. adding a thermostat adress to a module (I know sorry it’s almost been a month…) and saddly it does not solve my issue.
image
(I also tried with contiguous adresses, e.g. A6 and A7)

Even with a Thermostat adress assigned, the following error still appears every 10 seconds


Note: I only get that error when selecting “Periodically (every 10sec) request values of unfolded modules”.

Furthermore, it also does not add a temperature sensor/reading entity in home assistant…

PS: I “reload” the velbus integration in HA and restart after every change, I do not need to delete it and add it again… right?

You also need to clear the Velbus cache when changing/adding addresses.

  • stop the HA service
  • clear the velbuscache folder in home-assistant/config/.storage
  • restart the HA service (Velbus startup will take long because the cache needs to be rebuild)
2 Likes

It was indeed as simple as that ! just needed to clear the velbuscache with HA stopped.
thanks a lot for your help.