VMBDALI-20 not all devices are recognized

[kdr-19]

When scanning VMBDALI module, I have the impression that specific types are not recognized.
Devices with type 'Dimmer' in Velbuslink are not detected, when other devices with type 'LED module' are detected.

See below a snippet of the diagnostics. 37 & 39 are recognized (LED module), while 38 is not recognized (Dimmer).

It is a bit confusing, as device type 'LED Module' in Velbuslink becomes 'Dimmer' in Home Assistant. Device type 'Dimmer' in Velbuslink becomes 'channel' in Home Assistant.

After scanning, when I check the devices and entities in Home Assistant, the devices cannot be found.

[cereal2nd]

a led module should become a dimmer,

the channel on 38 is because we did not receive a channel settings message for this channel, so we have no idea what to do with this channel.
The Channel type is just there as a placeholder.

Can you clear the velbus cache and see if it still happens?

[kdr-19]

I cleared the cache, and now a new scan is running, but with constant error messages:

I have had this before, and it seems the case that the scan is stuck in an infinite loop. So I restarted Home Assistant, and the following scan ran without problems. However, still the same problem. Any idea in which case no channel settings are provided? Is this maybe an unknown type?

In the Signum Home Assistant, the entity is visible:

[cereal2nd]

it seems that only the ledmodule was implemented :(

velbus-aio/velbusaio/module.py

Line 866 in 21e4a9d

elif message.data.device_type == DaliDeviceType.LedModule:

[kdr-19]

Any idea if this can be updated to also support Device Type Dimmer?
It is a known device type, so maybe a pretty straightforward change?

velbus-aio/velbusaio/messages/dali_device_settings.py

Line 73 in 21e4a9d

class DeviceType(enum.Enum):

[cereal2nd]

maybe, the problem is that i can not test this myself, so i can make some blind changes, but without testing its hard to push this upstream.

[kdr-19]

How can these changes be tested? Does this include support of Velleman?
I also created a post on their forum, so maybe they could help?
https://forum.velbus.eu/t/home-assistant-vmbdali-20-dimmer-niet-herkend/17886

[cereal2nd]

velbusaio used in antive home-assistant had nothing todo with velleman
signum uses a completely different approach with home-assistant, and thats managed by velleman.

You can test this by cloning the repo, running a python venev en run the load_modules example
in the end it will dump all the data in the ~/.velbuscache dir, once the load finishes you can then look at the stored json files

[pvrobays]

@kdr-19 as @cereal2nd mentioned, only the LED Module is implemented in this integration, and is weirdly enough named Dimmer :)
I do think you should be able to quite easily implement the actual Dimmer functionality within this integration though if you know how to code. You can look up the actual commands within the VMBDALI documentation of velbus (https://github.com/velbus/moduleprotocol/blob/master/protocol_vmbdali_vmbdali_20.pdf) and implement those in your own ActualDimmer class (or rename the current Dimmer to LedModule; but that would break all current installations with a DALI module) which is inline with the current Dimmer class.
I also only have LED Modules, and no dimmer available in my setup; otherwise I would've had a look to try and implement it.