[SOLVED] MaxCul cannot pair: Not enough credit

Add-ons Bindings
, ,
1

Hi. I am new to openHAB and struggling with connecting my Max-Radiator-Heating-Controllers to my Cul. The log tells me that I have zero credit. What can I do?
Regards from Germany.

16:58:52.788 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - MaxCulSender Received Z170004001AB876000000001101A14F45513139353739353132
16:58:52.791 [DEBUG] [binding.maxcul.internal.MaxCulBinding] - Received data from CUL: Z170004001AB876000000001101A14F45513139353739353132
16:58:52.793 [DEBUG] [binding.maxcul.internal.MaxCulBinding] - Got PAIR_PING message
16:58:52.795 [DEBUG] [binding.maxcul.internal.MaxCulBinding] - Found 4 configs for OEQ1957951
16:58:52.798 [DEBUG] [g.maxcul.internal.MaxCulBindingConfig] - Successfully wrote pairing info for OEQ1957951
16:58:52.800 [DEBUG] [g.maxcul.internal.MaxCulBindingConfig] - Successfully wrote pairing info for OEQ1957951
16:58:52.801 [DEBUG] [g.maxcul.internal.MaxCulBindingConfig] - Successfully wrote pairing info for OEQ1957951
16:58:52.802 [DEBUG] [g.maxcul.internal.MaxCulBindingConfig] - Successfully wrote pairing info for OEQ1957951
16:58:52.803 [DEBUG] [binding.maxcul.internal.MaxCulBinding] - Using default temperature configuration from config 0
16:58:52.804 [DEBUG] [binding.maxcul.internal.MaxCulBinding] - Creating pairing sequencer
16:58:52.805 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Starting sequence
16:58:52.805 [DEBUG] [uencers.PairingInitialisationSequence] - Sequence State: INITIAL_PING
16:58:52.806 [DEBUG] [uencers.PairingInitialisationSequence] - Sending PONG
16:58:52.807 [DEBUG] [ding.maxcul.internal.messages.BaseMsg] - Reconfiguring message to FAST
16:58:52.808 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Fast Send? true, preambleCredit = 0, requiredCredit = 10, availableCredit = 0, enoughCredit? false
16:58:52.809 [DEBUG] [ding.maxcul.internal.messages.BaseMsg] - Reconfiguring message to SLOW
16:58:52.811 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Added message to queue to be TX'd at Fri Jan 25 17:01:53 CET 2019
16:58:52.812 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Message 4 is part of sequence. Adding to register.
...
17:00:01.889 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Checking credit
17:00:01.892 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Fast Send? false, preambleCredit = 100, requiredCredit = 10, availableCredit = 0, enoughCredit? false
17:00:01.894 [ERROR] [ding.maxcul.internal.MaxCulMsgHandler] - Not enough credit after waiting. This is bad. Queued command is discarded
17:01:53.889 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Checking credit
17:01:53.891 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Fast Send? false, preambleCredit = 100, requiredCredit = 10, availableCredit = 0, enoughCredit? false
17:01:53.894 [ERROR] [ding.maxcul.internal.MaxCulMsgHandler] - Not enough credit after waiting. This is bad. Queued command is discarded
17:03:45.889 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Checking credit
17:03:45.892 [DEBUG] [ding.maxcul.internal.MaxCulMsgHandler] - Fast Send? false, preambleCredit = 100, requiredCredit = 10, availableCredit = 0, enoughCredit? false
17:03:45.894 [ERROR] [ding.maxcul.internal.MaxCulMsgHandler] - Not enough credit after waiting. This is bad. Queued command is discarded
2

Just guessing: wait.
Any 868MHz range device is permitted to transmit a well-defined fraction of the available time only by law and all implementations should be honoring that. You probably try to send too many messages in a short period of time so you’re “out of credit”.

3

I only want to add a single device. How can i archieve it?
I think it seem that i never had credits.

4

Well as I said I was just guessing, I don’t own a CUL.
The CUL driver is not popular at all among openHAB users, it’s usually only people migrating from FHEM who want to use it. Most others are going for the max binding (with a cube).

5

OK. Thanks for your replies. I did a work-araound and installed Homegear with the Homematic-binding. Works like a charm with CUL.

6

I have the same problem, I know the 1% rule and I did wait, but it didn’t help.
So I checked the credit with a serial connection directly on my nanoCUL. Dispite what the MAX! CUL Binding said, it was not zero.

So, I chased this error through the Java Code and the logs and what I found so far is that the credit is not requested from the CUL. Really strange. I found some log entries where the credit was requested 5 days ago.

2019-10-13 18:54:03.529 [DEBUG] [port.cul.internal.AbstractCULHandler] - Requesting credit report

But no such request recently.

I consider this as a bug.