@Cereal2nd : is it better to only post those here, log an issue on your Github repo and/or add an issue in Home Assistant Core repo; just to be sure that it’s most convenient for you of course!
I’ve mentioned this before in this thread, but we didn’t come to any solutions back then.
I’m not sure if I’m the only one with this issue or if there are others.
It’s regarding the covers always having the state “open” even though the position is changed correctly between 0 and 100 and the state does say “closed” while the covers closes but gets set to “open” once it is fully closed.
for example the issue with the config flow not working is something for the homeassistant repo, the issue with the covers is something for the velbusaio repo as this is probably caused by the parsing of the messages.
about the covers, this is indeed known, but as i do not own the covermodules is har for me to debug/fix.
what modules are having this issue? for the covers there are 2 different implementations in the protocol, so i really need the modle type.
Regarding the config flow: might be fixed by deleting that second Velbus record in the core.config_entries file. I’m testing this right now, will update this message if indeed that’s the fix for it.
Update: this seems to fix it indeed; I’m able to create a new Velbus integration.
Regarding the covers: I’ve closed the Home Assistant repo issue and opened one in Velbusaio repo
I have 5 Velbus “cover” modules of the same type “VMB2BLE”, with Velbus build “1935”
Update: I updated these to build “2205” (latest as of now) and still the same behavior.
I also have the VMB2BLE build 1935 in my system. In the entities card on the gui, the state is shown correctly, open / close / and in between. But now I checked the state in the developers tools and there it has always the open state. I do not use automations on the cover state, so I never noticed.
What version of Home Assistant do you have? I’m also on the entities card and it changes from open to closed to open again when the Velbus relay opens again I notice. It is closed, until the full interaction for the cover is done.
Anyone ever saw this?
I’m having all sorts of issues apparently with this new HA version… not sure what happened vs 2022.6.x but I haven’t seen these messages before as far as I know
Logger: root
Source: deps/lib/python3.9/site-packages/velbusaio/raw_message.py:72
First occurred: 11:41:40 PM (144 occurrences)
Last logged: 11:53:04 PM
Could not parse the message b'0ffb3707e62f0200b8e07f00000f'. Truncating invalid data.
Could not parse the message b'0ffb3707e62fe00200b8e07f000f'. Truncating invalid data.
Could not parse the message b'0f0200b8e07f0000010000000000'. Truncating invalid data.
Could not parse the message b'0ffb3707e62fe000000000000000'. Truncating invalid data.
Could not parse the message b'0ffb3707e62fe0210200b8e07f0f'. Truncating invalid data.
Update: the fix for this btw is to disable the Velbus integration for a bit; then re-enable it. You could also restart Velserv (if you’re using that) while doing the integration was disabled.
After re-enabling, it did a full scan and worked after that was done.
I do have a very long scan though; it is always “waiting for module 32” and after a while it just gives up. All modules seems to work though, so not sure what the issue is…
Didn’t you have the ‘Not all modules are loaded within…’ error before ? On your the HA 2022.6 version for example ? There have not been any changes to the scanning of the velbus since a long time.
What module do you have on address 32 ?
Can you do this to debug the issue:
add this to your configuration.yaml somewhere in the beginning
I modified velserv because I use the TCP server with CAN interface directly on the Velbus, skipping the use of the USB interface. But I don’t think the problem is in there.
in one of my installations one of the modules thermostat just dissapeared… its nowhere to be found… I’ve changed the address already and reloaded the integration to force a new scan… but still nothing shows up… I’ve even checked .storage/core.entity_registry but nothing listed there either… any hints & tips?
I also noticed that the Velbus integration loads the USB as well as the tcp modules at the same time… given i have velbus-tcp loaded on the same computer, once the USB kicks in… it actually kills the connection completely… and I had to forcefully put down the USB integration and restart velbus-tcp… (i’m guessing my problem has to do with that…)
Did you loose only the thermostat or all entities of the module ? Which module type is it ?
You can always try to clear the velbus cache in the config folder, not sure if it will help. First stop the HASS service before you clear the cache, then restart it.
No idea about the USB.
Did you get this after an update ? From which version ?
I think its about sending the temperature of a module, do you know which module type has a failing temperature readout in HA ?
If you get this error every second, try reducing the temperature transmit rate of the module in Velbuslink, you probably will still get errors but less frequent.
If you know which module is failing, can you share all its used addresses from Velbuslink ?
Home Assistant 2022.12.8, Frontend 20221213.1 - latest running on Docker on a synology NAS
I got this issue right after installing the Velbus Integration
I do not have any temperature reading in HA… will look into that. But in Velbus Link, all temp readings look normal.
I don’t think I can reduce the temperature transmit rate of any module in velbus link, it gives me the following error ‘‘For additional temperature settings you need to assign an address to the thermostat’’
I see. I do use the temperature sensors of all my Velbus switches for my heating (but that’s done in a custom made application). So I do not need a Velbus thermostat, but if it helps me clear my logs…
Everything still runs perfectly fine though, so Is it still OK to run like this, even though I have tens of thousands of errors every hour? (hardware wise…)
