some F429 dimmers are not discovered

[weltraumbagger]

i´ve serveral dimmers, connected to two f429 dali-interface on different interfaces (8 dimmers in ..#4#01 and seven dimmers in ..#4#02.

if i start device discovery (meanwhile several times) some dimmers are not found (all in ..#4#01), even not as switch if powered off. if i add them manually they work.

but all dimmers (enen the discovered) do not work quite correct:

under "paper ui / control" i can see the dimmer and slide light on, off and dimm it. but if i control from another point (light switch or domotica-app for example) the state will not be updated here.

as in improvement i suggest not only a slider for dimmers, a additionally switch would be great go enable switching light on and automatically use last dimmer-state. so if automatic discovery woudl find both, switch and dimmer, i think would be a good thing.

[m4rky-m4rk]

Ah so I am not the only one. I have one dimmer module that refuses to be discovered even though the others on the same F429 are found. If I add it manually it works. The F429 config seemed OK even so I resent it to be sure but it didn't help. I have informed Massi about this and sent him the logs.

M

[mvalla]

Do you also experience problems with feedback from the network? If you take one of the configured (auto or manually) dimmers and change it from the light switch (on/off/dimm) can you see it change in the "paper ui / control" ??

[weltraumbagger]

no matter if i try auto discovered or manual added dimmers, they work in "paper ui / control" (and the states are updated in domotica-app) but if i use a physical switch or domotica-app to change level or set on/off then the states are not updated under "paper ui / control"

(for normal switches for example i can see the changes in "paper ui / control")

is use openhabian with openhab 2.3.0-1 (release build)

[mvalla]

@weltraumbagger regarding the "states not updated" (when using physical switch) problem, is this still an existing issue?
Otherwise I ask you to create another issue about the not discovered F429 Dali dimmers, and I will close this one.

[weltraumbagger]

@mvalla:
i just played around a little and now i found out:
i have a myhomescreen 4893 and several touchscreens 4890. if i switch my (dali-) dimmers on/off with a physical switch 4652-2 the states are beeing updated in openhab. but if i switch the dimmers trough myhomescreen or touchscreen then the states are not updated. this problem is only with dali-dimmers. switches and rollershutters work everywhere proberly.
i think the other issue with some not discovered dali-dimmers is independent from this.

[mvalla]

Ok could you then switch or change dimmer level from myhomescreen , and send me (here or via PM on the community) the openHAB log (better if set, before doing the test, in DEBUG mode)
Tell me also the WHERE address of the dimmer that you have changed during the test

[mvalla]

after some tests, we have two issues that can be separated: discovery and states not updated. I modify here this issue to be related to discovery and create new issue for states updates

[weltraumbagger]

now i tried around several things with my dali-device (f-429), as:

switched polarity of the physical wires
switched the physical wires from discovered to not discovered ports
added a new device in myhomesuite and set quite different (and not used) addresses for all ports

… all with the same result: channes 2,3 and 4 will never be discovered. so i think the reason must be the dali device is not working quite correct.

because this seems to be hardware-fault an ins´t caused by the software i suggest to close this issue, thanks

[m4rky-m4rk]

I have same issue so I am not so sure it is a hardware fault

[mvalla]

@m4rky-m4rk and @weltraumbagger I think this is a very old issue and it was never unerstood if the problem was with hw or with the binding. I think I will close this one as no more evidence is available that is a problem with the binding.

[weltraumbagger]

I totally agree. This happened a long time ago, meanwhile i do not use autodiscovery but have textual config and so never seen this issue again thank you 13.04.2023 22:15:51 M Valla ***@***.***>:

…

@m4rky-m4rk[https://github.com/m4rky-m4rk] and @weltraumbagger[https://github.com/weltraumbagger] I think this is a very old issue and it was never unerstood if the problem was with hw or woth the binding. I think I will close this one as no more evidence is available that is a problem with the binding. — Reply to this email directly, view it on GitHub[#14 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AJ5E7ZW6XWKD2NBCE365NW3XBBNHNANCNFSM4GDBR5QQ]. You are receiving this because you were mentioned.[Verfolgungsbild][https://github.com/notifications/beacon/AJ5E7ZU7N37ZY7MHDV5GEYTXBBNHNA5CNFSM4GDBR5Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOLHNYSHY.gif]