HomeMatic MISSING ACK

[mflammia1]

Hi There,

Recently installed an additional USB CUL device that successfully detected and installed an new Homematic device:

define FileLog_MAX_1a002c FileLog ./log/MAX_1a002c-%Y.log MAX_1a002c
attr FileLog_MAX_1a002c logtype text
attr FileLog_MAX_1a002c room MAX
define HM_302DB1 CUL_HM 302DB1
attr HM_302DB1 room CUL_HM
define FileLog_HM_302DB1 FileLog ./log/HM_302DB1-%Y.log HM_302DB1
attr FileLog_HM_302DB1 logtype text
attr FileLog_HM_302DB1 room CUL_HM

The problem I am having is that I can't seem to get the Homematic remote switch to work as it keeps coming up with the following error:

2015-11-01_08:59:06 HM_302DB1 D-firmware: 2.5
2015-11-01_08:59:06 HM_302DB1 D-serialNr: LEQ1211862
2015-11-01_08:59:48 HM_302DB1 set_off
2015-11-01_08:59:51 HM_302DB1 set_on
2015-11-01_09:00:03 HM_302DB1 ResndFail
2015-11-01_09:00:03 HM_302DB1 MISSING ACK

The CUL device is configured as such:

define CUL_1 CUL /dev/ttyACM0@9600 1234
attr CUL_1 rfmode HomeMatic
define cn CUL_HM 112233
attr cn IODev CUL_1
attr cn autoReadReg 4_reqStatus
attr cn expert 2_full

The only bit I am not sure is a contributing factor is that both CUL_0 and CUL_1 show initialised. CUL_0 (CUL_MAX) has cm shown as 'defined', but CUL_1 (CUL_HM) has cn shown as '??'

Many thanks in advance

[UliM]

Hi,
can't answer regarding the CUL-state because I'm using a HM-CFG-USB.
But apparently it does work, otherwise you wouldn't see any feedback from your HM-device.

However it seems the device is not paired successfully.

Have you followed the following procedure:
fhem-command

Code Auswählen Erweitern

set CUL_HM hmPairForSec 30
Then within those 30 seconds, hold the button on the device for min. 5 seconds.

After that, issue fhem-command

Code Auswählen Erweitern

set <devicename> getConfig

You should then see a device-reading like

Code Auswählen Erweitern

PairedTo  0x34F25F
Unless you see this reading with a value other than 000000, the device is not paired yet and will not accept commands from fhem.
So keep retrying until you get that reading. Once you have this done, you'll be able to issue any fhem-command to the device.

Best,
Uli

[mflammia1]

Thanks very much for posting back.

I wasn't fully aware of the paring process, although I did come across it when researching the problem but I think I might have misinterpreted the syntax

When enter the following command, and then hold down the device button for 5 seconds:

Code Auswählen Erweitern

set CUL_HM hmPairForSec 30

I get the following message, although to the best of my knowledge it is already defined?

Code Auswählen Erweitern

Please define CUL_HM first

Then I next put the command in as you detailed:

Code Auswählen Erweitern

set HM_302DB1 getConfig

The state seems to have changed from missing ack to

Code Auswählen Erweitern

RESPONSE TIMEOUT:RegisterRead

Also turned on verbose logging and have the following messages:

2015.11.02 20:58:40.194 4: CUL_send:  CUL_1As 10 02 A001 F11234 302DB1 00040000000000
2015.11.02 20:58:45.073 4: CUL_send:  CUL_1As 10 02 A001 F11234 302DB1 00040000000000
2015.11.02 20:58:49.939 4: CUL_send:  CUL_1As 10 02 A001 F11234 302DB1 00040000000000
2015.11.02 20:58:55.623 4: CUL_send:  CUL_1As 10 02 A001 F11234 302DB1 00040000000000
2015.11.02 20:59:48.511 4: CUL_send:  CUL_1As 10 03 A001 F11234 302DB1 00040000000000
2015.11.02 20:59:53.910 4: CUL_send:  CUL_1As 10 03 A001 F11234 302DB1 00040000000000
2015.11.02 20:59:58.701 4: CUL_send:  CUL_1As 10 03 A001 F11234 302DB1 00040000000000
2015.11.02 21:00:04.541 4: CUL_send:  CUL_1As 10 03 A001 F11234 302DB1 00040000000000
2015.11.02 21:01:05.771 4: CUL_send:  CUL_1As 10 04 A001 F11234 302DB1 00040000000000
2015.11.02 21:01:10.037 4: CUL_send:  CUL_1As 10 04 A001 F11234 302DB1 00040000000000
2015.11.02 21:01:15.059 4: CUL_send:  CUL_1As 10 04 A001 F11234 302DB1 00040000000000
2015.11.02 21:01:21.071 4: CUL_send:  CUL_1As 10 04 A001 F11234 302DB1 00040000000000
2015.11.02 21:07:07.066 4: CUL_send:  CUL_1As 10 05 A001 F11234 302DB1 00040000000000
2015.11.02 21:07:12.480 4: CUL_send:  CUL_1As 10 05 A001 F11234 302DB1 00040000000000
2015.11.02 21:07:16.894 4: CUL_send:  CUL_1As 10 05 A001 F11234 302DB1 00040000000000
2015.11.02 21:07:22.910 4: CUL_send:  CUL_1As 10 05 A001 F11234 302DB1 00040000000000

So apologise, but now have a new issue.

Many thanks for your support.

[mflammia1]

Could this be my problem, with my CUL_HM , myVCCU showing all question marks?

[UliM]

Hi,
ah - sorry, my mistake, based on your previous posting I thought your CUL was named CUL_HM.
Furthermore, if you have a vccu, then hmPairForSec needs to be issued against that one, hence in your case

Code Auswählen Erweitern

set myVCCU hmPairForSec 30
As this command didn't work, subsequently the rest can't work either.

In my system, the vccu shows

Code Auswählen Erweitern

STATE hmusb:ok

As yours reports an unknown status, but you linked it ok to CUL_1, it seems the CUL isn't working properly.
Can you issue fhem-command

Code Auswählen Erweitern

list CUL_1
and post the output here? I won't be able to help, but somebody else certainly can.  (please use the "code" tag when posting the list, it's easier to read then)
Otherwise, it is assumed you have run update etc.

Cheers,
Uli

[mflammia1]

Hi,

Here's the output of the command:

Code Auswählen Erweitern


Internals:
   CMDS       BbCFiAZEGMKUYRTVWXefmltux
   Clients    :CUL_HM:HMS:CUL_IR:STACKABLE_CC:
   DEF        /dev/ttyACM0@9600 1234
   DeviceName /dev/ttyACM0@9600
   FD         13
   FHTID      1234
   NAME       CUL_1
   NR         71
   PARTIAL
   STATE      Initialized
   TYPE       CUL
   VERSION    V 1.61 CUL868
   initString X21
Ar
   Matchlist:
     1:CUL_HM   ^A....................
     8:HMS      ^810e04....(1|5|9).a001
     D:CUL_IR   ^I............
     H:STACKABLE_CC ^\*
   Readings:
     2015-11-02 22:14:59   cmds             B b C F i A Z E G M K U Y R T V W X e f m l t u x
     2015-11-02 22:14:59   state           Initialized
Attributes:
   rfmode     HomeMatic
   verbose    4


Possibly my fault as I had changed the code from my original post as I've been doing some testing, it was 'cn' but changed it to myVCCU, even though its not a vccu - truth is I don't really know what my code should ideally be for the CUL_1 / Homematic configuration. This is what I have it configured to currently:

Code Auswählen Erweitern


define CUL_1 CUL /dev/ttyACM0@9600 1234
attr CUL_1 rfmode HomeMatic
attr CUL_1 verbose 4
define myVCCU CUL_HM 5C0C05
attr myVCCU IODev CUL_1
attr myVCCU autoReadReg 4_reqStatus
attr myVCCU expert 2_full


Many thanks.

[UliM]

Oh, that's misleading.
myVCCU should ne of Type vccu, Not CUL_HM. Check commandref.
And maybe post the list of all devices in the game

[mflammia1]

Sorted it. The command was:

Code Auswählen Erweitern

set CUL_1 hmPairForSec 30

Appreciate your time, you definitely helped, even though I may have confused matters some what.

Many thanks.