Issue teaching Hm-Lc-Dim1PWM-CV to CCU2 V 2.15.5

[nitramsen]

I only started installing Homematic in my home 1 week ago (My first home automation system) so below could be my issue but I do not think so.

I cannot get the Hm-Lc-Dim1PWM-CV paired with the CCU2 ( I have paired multiple other wireless and wired units without issues), I have followed the manual to the point but it refuses to show up in the CCU2 postbox.

Steps I did to teach the actor to the CCU:

1. Connected all wires to the actor (I tried with and without led strip connected)
2. Powered on the actor (tested with 12V and 24V from different power supplies and a lab power supply)
3. Waited anywhere from 5 seconds – minutes
4. Started the teaching mode on the CCU2 WebUI
5. Waited from 1-30 second (trying 10+ times) and then held the button on the actor down for 4-10 seconds (Until the led on the actor started blinking red )
6. Waited, waited, waited but result is always 0 new devices in the CCU

I have tried teaching the actor to the CCU using the Serial number and then the red LED on the dimmer starts blinking but after a while the webui shows a messagebox saying that the teaching failed and that I should check the serial number.

I have enabled all logging on the CCU2 and checked the log file but there is no mention of the device, the pairing or any errors.

I have directly paired the Hm-Lc-Dim1PWM-CV with a wireless toggle switch and that works (I can dim, switch it on and off)…. I tried resetting the actor but same results when trying to pair with the CCU after the reset.

Just to check that the CCU2 works, I paired an unused wireless toggle switch and a 8 button remote to the CCU2 and that works without issues, so not a general issue on the CCU.

Have tested with a short and a long distance (2m-15m) between CCU and actor but same result.

I have 3 new preassembled Hm-Lc-Dim1PWM-CV units and they all behave in the same way, so I think this is an issue with the CCU2, a general issue with the Hm-LC-DimPWM-CV Or I am doing something wrong.

Is there any known issue with the Hm-LC-DimPWM-CV and pairing it to the CCU2?

Does anyone have any idea what to try next?

Thanks
Martin

[Familienvater]

Hi Martin,

I think you've tried a lot of possibilities, even with near and far distance of the actor to the ccu.
One "little" possiblity I can imagine:
With which letter the serial of the Actors are starting (each first letter represents a different production year (K must be 2013, L 2014, M 2015).
May be you have a really old actor with an very old firmware.
Other thing:
Do you entered a personal security key? Maybe the actor will not pair, if not the factory default security key is used.

Greets,

The Family-Father

[nitramsen]

Hi Familienvater ,

The serial number starts with MEQ.

I even tried downgrading the CCU but it refuses (WeBUI says illegal firmware image, so I guess downgrading cannot be done) because I thought it could be a firmware compatibility issue, but now I know that the actors are from 2015 so that cannot be the issue. (Seems like all my devices are MEQ so that is good news, I hope )

No I have not add a security code yet to avoid issues.....

thanks
Martin

[Familienvater]

Hi,

sorry, this was my only ideas, where the problems may reside.

Another last try:
switch the log-Level of the central bidcos-RF to the "log all?" level (Settings-Menu, first Button (central...?), try to teach the actor with the serial number, and then download the logfile from the same menu, and paste the content here, maybe there is a hint in the log.

Der Familienvater

[Roland M.]

Hello Martin, welcome to the forum!


Seems you did your homework and tried every possibility...

3. Waited anywhere from 5 seconds – minutes

I'd recommend to start shortly after the LED stops blinking, because after (default) 5 minutes the button can only be used to dim up/down instead of entering the teaching mode.

I have tried teaching the actor to the CCU using the Serial number

Please be aware that the s/n have to be entered in capital letters ("MEQ..." instead of "meq...").

Have tested with a short and a long distance (2m-15m) between CCU and actor but same result.

2 m should be sufficient.

I have 3 new preassembled Hm-Lc-Dim1PWM-CV units and they all behave in the same way

My English isn't developed high enough, what do you mean by "preassembled"?
Did you bought the actor(s) new to use out of the box, or as a kit (and assembled by another person)? Or even used?

Another approach could be to try a different browser. Chrome and Firefox seems to be the most reliable browsers for Homematic.


Roland

[Familienvater]

Hi,

Roland gives me a new idea, maybe you could try to reset the dimmer-actor back to factory defaults (chapter 8 of the actor-manual) and then give it another try to teach the actor to the ccu.

Der Familienvater

[nitramsen]

Thanks

Here is the logfile : (MEQ0xxxx7 = Dimmer, MEQ0xxxxxx5 = CCU2 )
Jan 7 00:19:03 homematic-ccu2 user.debug rfd: TX: @423397039 0x2B9D41 -> 0x000000 CONFIG_ENTER [MEQ0xxxxxx5]: CNT=0,RPTEN=1,RPTED=0,BIDI=0,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=1,TYPE=0x01 CONFIG_CHANNEL = 1 CONFIG_SERIAL = MEQ0874337
Jan 7 00:19:03 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:03 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Jan 7 00:19:03 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:03 homematic-ccu2 user.debug rfd: (MEQ0xxxxxx5) Response status: Telegram sent successfully.
Jan 7 00:19:05 homematic-ccu2 user.debug rfd: TX: @423399040 0x2B9D41 -> 0x000000 CONFIG_ENTER [MEQ0xxxxxx5]: CNT=0,RPTEN=1,RPTED=0,BIDI=0,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=1,TYPE=0x01 CONFIG_CHANNEL = 1 CONFIG_SERIAL = MEQ0xxxx7
Jan 7 00:19:05 homematic-ccu2 user.debug rfd: (MEQ0xxxxxx5) Response status: Telegram sent successfully.
Jan 7 00:19:07 homematic-ccu2 user.debug rfd: TX: @423401041 0x2B9D41 -> 0x000000 CONFIG_ENTER [MEQ0xxxxxx5]: CNT=0,RPTEN=1,RPTED=0,BIDI=0,BURST=1,WAKEUP=0,WAKEMEUP=0,BCAST=1,TYPE=0x01 CONFIG_CHANNEL = 1 CONFIG_SERIAL = MEQ0xxxx7
Jan 7 00:19:07 homematic-ccu2 user.debug rfd: (MEQ0xxxxxx5) Response status: Telegram sent successfully.
Jan 7 00:19:11 homematic-ccu2 user.debug rfd: TX: @423405042 0x2B9D41 -> 0x000000 CONFIG_ENTER [MEQ0xxxxxx5]: CNT=0,RPTEN=1,RPTED=0,BIDI=0,BURST=1,WAKEUP=0,WAKEMEUP=0,BCAST=1,TYPE=0x01 CONFIG_CHANNEL = 1 CONFIG_SERIAL = MEQ0xxxx7
Jan 7 00:19:11 homematic-ccu2 user.debug rfd: (MEQ0xxxxxx5) Response status: Telegram sent successfully.
Jan 7 00:19:15 homematic-ccu2 user.debug rfd: RX for MEQ0xxxxxx3: @423406248 RSSI=-82dB 0x3F1B5B -> 0x000000 WEATHER [MEQ0xxxxxx5]: CNT=97,RPTEN=1,RPTED=0,BIDI=0,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=1,TYPE=0x70 LOWBAT = 0 TEMP = 234 HUMIDITY = 44 RAINING = 0 RAINCNT =
Jan 7 00:19:15 homematic-ccu2 user.debug rfd: Event: MEQ0xxxxxx3:1.TEMPERATURE=23.400000
Jan 7 00:19:15 homematic-ccu2 user.debug rfd: Event: MEQ0xxxxxx3:1.HUMIDITY=44
Jan 7 00:19:15 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 2 events
Jan 7 00:19:15 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 2 events
Jan 7 00:19:15 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:15 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:19 homematic-ccu2 user.debug rfd: RX for MEQ0xxxxxx4: @423413491 RSSI=-68dB 0x3F1B49 -> 0x000000 WEATHER [MEQ0xxxxxx5]: CNT=43,RPTEN=1,RPTED=0,BIDI=0,BURST=0,WAKEUP=0,WAKEMEUP=0,BCAST=1,TYPE=0x70 LOWBAT = 0 TEMP = 240 HUMIDITY = 39 RAINING = 0 RAINCNT =
Jan 7 00:19:19 homematic-ccu2 user.debug rfd: Event: MEQ0xxxxxx4:1.TEMPERATURE=24.000000
Jan 7 00:19:19 homematic-ccu2 user.debug rfd: Event: MEQ0xxxxxx4:1.HUMIDITY=39
Jan 7 00:19:19 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 2 events
Jan 7 00:19:19 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 2 events
Jan 7 00:19:19 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:19 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: RX for MEQ0xxxxxx7: @423418316 RSSI=-77dB 0x3F1BBA -> 0x000000 Generic [MEQ0xxxxxx5]: CNT=118,RPTEN=1,RPTED=0,BIDI=0,BURST=0,WAKEUP=0,WAKEMEUP=1,BCAST=1,TYPE=0x5A DATA = A8 E4 2C
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: Event: MEQ0xxxxxx8:2.ACTUAL_TEMPERATURE=22.800000
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: Event: MEQ0xxxxxx8:2.ACTUAL_HUMIDITY=44.000000
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: Event: MEQ0xxxxxx8:2.SET_TEMPERATURE=21.000000
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send 1 events
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: HSSXmlRpcEventDispatcher::Handle send completed
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: (MEQ0xxxxxx5) Response status: OK.
Jan 7 00:19:24 homematic-ccu2 user.debug rfd: Leaving install mode.

There is never a reply from MEQ0xxxx7.....

[nitramsen]

Hi Familienvater and Roland M.


I already tried the reset numerous times and that always results in the same (Can pair with wireless toggle button but not CCU2).

By preassembled I mean new and assembled (kein Bausatz......) from the factory (VOID seal sticker intact)

I have also tried teaching mode right after LED stops blinking on the actor but same issue. I tried both lower case and upper case MEQ same result except with lower case the red LED on the actor does not start to blink as it does with the correct case serial number.

Tried from IE 11, EDGE, Chrome same result. (I tried from German and English CCU interface )

thanks
Martin

[Familienvater]

Hi,

sorry, I'm helpless... It is strange, that if you try to teach with serial, the actor starts blinking, so the actor obviously receives the start-to-teach datagram, but the central does not get any response from the actor (which let's me think, that the transmitter on the actor is receiving, but not transmitting).
But you say, you can pair the actor with a simple remote control, and toggle the actor with the remote.
Normally if you press a key on the remote control, the orange LED will light, and then acknowledge with green color on the remote, when the actor has acknowleged and switched.
Do you get the green light on the remote if toggling with a paired remote-control? (That means, that the transmitter of the actor is ok, and I never tried to pair devices with a not transmitting actor, if this will work for some reasons).

But since you have 3 actors that behave in that way, it's very unlikely that all three have the same defect...

I do not have a PWM-Dimmer, so I can not try to reproduce.

Maybe another guru here will have some more ideas...

Der Familienvater

[nitramsen]

Hi,


It was a 4 Channel wireless Push-Button (Hm-PBI-4-FM) that I paired it with and it does not flash the Led when I push the button ( But it works).

I just paired it with a remote and it behaves as you descripted (When I click the button on the remote to turn on the led strip the remote led goes orange immediately followed by green).

So all of this means, if I understand correctly, that the actor is both sending and receiving so it is most likely a problem with the CCU receiving the reply from the actor.


Thanks,
Martin