Fibaro dimmer 2 autocalibration wont stop

[Ph0tonblast]

Hi all,

New here so pardon my lack of knowledge.

I have a number of dimmer v2's with dimmer bypass. My house is engulfed in 2 wire installations, and these would seem like a nice fit. The dimmers worked absolutely fantastic for about 6 months. Then suddenly 3 dimmers started some kind of continuous autocalibration (at least that's what I think it is). If i switch them on, they are fine for some time and then start dimming down with 1 sec interval, until theyre at 0%. Afterwards, some seemingly random time, but never before 30 minutes, they will start increasing to some random percentage and after a while, this process repeats.

I run domoticz and I've done manual calibration with bypass on 1 dimmer, autocalibration on another dimmer, numerous times, but it never solves the issue. As soon as I cycle the switch, it repeats itself yet again.

I run domoticz (on a rpi3b+) with an aeotec zwave plus stick (gen 5). When it starts autocalibration, domoticz shows no logging, so no scripts or dz system initiates the autocalibration process.

Now I dont know if the dimmers are faulty.. which would seem unlikely, because why would 3 dimmers simultaneously start acting up? Could it be the aeotec zwave stick? I've resetted it, along with all the dimmers to completely start over, but that didn't solve anything. And last but not least it could be the raspbian/domoticz installation. But it would seem unlikely since the os doesnt talk do zwave devices itself.

I'm looking for any advice you experts could give me. So thanks in advance!

[petergebruers]

About calibration:

In 2-wire setup, auto calibrations sometimes is a bit too optimistic about parameter "2. Maximum brightness level (parameter is set automatically during the calibration process)". On the OZW Hardware page, select the dimmer and press "Request current stored values from device". Refresh browser page after 5 seconds. Make a note of the value right after calibration then reduce it by 5 or even 10. See what happens.

If that doesn't help, check if "35. Auto-calibration after power on" isn't accidentally set to "2 - Auto-calibration performed after each power on". Try "0 - no auto-calibration of the load after power on" or "1 - Auto-calibration performed after first power on"

About random dimming up or down... Please check firmware aka "application version", improvements have been made on 3.3 and 3.4. Current FW is 3.5. It might be caused by running long wires (most likely when switch input wire and load output wire run in the same conduit)... Before fw 3.3 I could simulate this with a mere 5m of wire. That fw update (and possibly later fw improved) increased the limit in my test setup to 10-15 meter. If there is leakage between the switch wires or in the switch, that might get detected as a a "button hold".

[Ph0tonblast]

Hi and thank you for your reply! Much appreciated!
Param 35 was set to 'perform autocalibration at power on', so this might explain the recurrence. I've set it to 'no auto calibration', just for the sake of the test. in addition, I've already set the threshilds to safer values: the values that were stable before (1-32). Given the fact these are moos lights, 32 is actually very comfy.

You speak about firmware versions, are these the firmware versions for the dimmers? If so: how do I check (and upgrade) these? Do dimmer bypasses also have any firmware by the way?

Thanks!

[Ph0tonblast]

Ok so an update is in order: last night, after reconfiguring the dimmers, they all started showing this unwanted behavior of auto calibration. I want to exclude the possibility of my dz being the culprit, so I'm reinstalling that and closely following the hardware reset guide from fibaro and aeotec to get things back up. See what happens afterwards.. if this doesn't work, i really don't know what to do next

[Ph0tonblast]

Another update: reinstalling dz from scratch didn't solve it either. I'm literally lost!