Fehler beim Empfang über wmbus - tty buffersize

Begonnen von ert77, 17 November 2023, 00:22:05

Vorheriges Thema - Nächstes Thema

ert77

Hallo zusammen,
ich habe einen nanoCul 868 von smart-home-komponente.de mit einer für wmbus angepassten Firmware.
Damit möchte ich einen WMZ Sensostar 2 U auslesen.
Der WMZ sendet im CMODE. Die Verschlüsselung ist ausgeschaltet.
Es kommen, wie unten zu sehen, auch Daten an, aber es kommt immer eine Fehlermeldung:
WMBUS Error during LinkLayer parse:message too short, expected 160, got 148 bytes

Scheinbar hat der nanocul einen 300byte Buffer.

Könnt Ihr mir sagen, wie ich das Problem lösen kann?
Leider bin ich in Sachen FHEM, nanCul und wmbus noch sehr unerfahren.


2023.11.16 23:56:45 5: CUL_Read: CUL868 /CMODE

2023.11.16 23:56:45 4: CUL_Parse: CUL868 CMODE
2023.11.16 23:56:45 5: CUL868: dispatch CMODE
2023.11.16 23:56:45 3: CUL868: Unknown code CMODE, help me!
2023.11.16 23:57:34 2: AttrTemplates: got 260 entries
2023.11.16 23:59:10 5: CUL_Read: CUL868 /bYA044C5149750753300047A310000002F2F046D3B37F02B84401300000000426C0000C4401300000000C4411300000000C4421300000000C44313000
2023.11.16 23:59:11 5: CUL_Read: CUL868 bYA044C5149750753300047A310000002F2F046D3B37F02B84401300000000426C0000C4401300000000C4411300000000C4421300000000C44313000/00000C4441300000000C4451300000000C4461300000000C4471300000000C4481300000000C4491300000000C44A1300000000C44B1300000000C44C1300000000C483A94D1300000000C44E1300000000C44F1300000000

2023.11.16 23:59:11 4: CUL_Parse: CUL868 bYA044C5149750753300047A310000002F2F046D3B37F02B84401300000000426C0000C4401300000000C4411300000000C4421300000000C4431300000000C4441300000000C4451300000000C4461300000000C4471300000000C4481300000000C4491300000000C44A1300000000C44B1300000000C44C1300000000C483A94D1300000000C44E1300000000C44F1300000000
2023.11.16 23:59:11 5: CUL868: dispatch bYA044C5149750753300047A310000002F2F046D3B37F02B84401300000000426C0000C4401300000000C4411300000000C4421300000000C4431300000000C4441300000000C4451300000000C4461300000000C4471300000000C4481300000000C4491300000000C44A1300000000C44B1300000000C44C1300000000C483A94D1300000000C44E1300000000C44F1300000000
2023.11.16 23:59:11 5: WMBUS raw msg bYA044C5149750753300047A310000002F2F046D3B37F02B84401300000000426C0000C4401300000000C4411300000000C4421300000000C4431300000000C4441300000000C4451300000000C4461300000000C4471300000000C4481300000000C4491300000000C44A1300000000C44B1300000000C44C1300000000C483A94D1300000000C44E1300000000C44F1300000000
2023.11.16 23:59:11 2: WMBUS Error during LinkLayer parse:message too short, expected 160, got 148 bytes
2023.11.16 23:59:11 2: Please make sure that TTY_BUFSIZE in culfw is at least two times the message length + 1
2023.11.16 23:59:11 3: CUL868: Unknown code bYA044C5149750753300047A310000002F2F046D3B37F02B84401300000000426C0000C4401300000000C4411300000000C4421300000000C4431300000000C4441300000000C4451300000000C4461300000000C4471300000000C4481300000000C4491300000000C44A1300000000C44B1300000000C44C1300000000C483A94D1300000000C44E1300000000C44F1300000000, help me!



define CUL868 CUL /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0@38400 0000
attr CUL868 rfmode WMBus_C
attr CUL868 room Heizung
attr CUL868 verbose 5
#   CMDS       BbCeFGKlMRTtVWXx
#   CUL868_MSGCNT 2
#   CUL868_TIME 2023-11-16 23:59:11
#   Clients    :WMBUS:HMS:CUL_IR:STACKABLE_CC:TSSTACKED:STACKABLE:
#   DEF        /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0@38400 0000
#   DeviceName /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0@38400
#   FD         11
#   FHTID      0000
#   FUUID      65569d7b-f33f-d9e0-ae31-f1fc0d9f5d29a703
#   MessageEncoding CUL
#   NAME       CUL868
#   NR         68
#   PARTIAL   
#   RAWMSG     bYA044C5149750753300047A310000002F2F046D3B37F02B84401300000000426C0000C4401300000000C4411300000000C4421300000000C4431300000000C4441300000000C4451300000000C4461300000000C4471300000000C4481300000000C4491300000000C44A1300000000C44B1300000000C44C1300000000C483A94D1300000000C44E1300000000C44F1300000000
#   STATE      Initialized
#   TYPE       CUL
#   VERSION    V 1.67 nanoCUL868_r568
#   devioNoSTATE 1
#   eventCount 4
#   initString X21
#brc
#   MatchList:
#     8:HMS      ^810e04....(1|5|9).a001
#     D:CUL_IR   ^I............
#     H:STACKABLE_CC ^\*
#     J:WMBUS    ^b.*
#     M:TSSTACKED ^\*
#     N:STACKABLE ^\*
#   READINGS:
#     2023-11-16 23:55:21   ccconf          freq:868.950MHz bWidth:325KHz rAmpl:33dB sens:8dB
#     2023-11-16 23:56:44   cmds             B b C e F G K l M R T t V W X x
#     2023-11-16 23:59:11   state           Initialized
#     2023-11-17 00:10:32   uptime          0 00:13:49
#     2023-11-16 23:55:31   version         V 1.67 nanoCUL868_r568
#   internal:
#     rawMsg     bYA044C5149750753300047A310000002F2F046D3B37F02B84401300000000426C0000C4401300000000C4411300000000C4421300000000C4431300000000C4441300000000C4451300000000C4461300000000C4471300000000C4481300000000C4491300000000C44A1300000000C44B1300000000C44C1300000000C483A94D1300000000C44E1300000000C44F1300000000
#
setstate CUL868 2023-11-16 23:55:21 ccconf freq:868.950MHz bWidth:325KHz rAmpl:33dB sens:8dB
setstate CUL868 2023-11-16 23:56:44 cmds  B b C e F G K l M R T t V W X x
setstate CUL868 2023-11-16 23:59:11 state Initialized
setstate CUL868 2023-11-17 00:10:32 uptime 0 00:13:49
setstate CUL868 2023-11-16 23:55:31 version V 1.67 nanoCUL868_r568


Vielen Dank,
Jan

Ralf9

nanoCUL_r568_mbus_c1t1_bufsize300Auf dem nanocul ist demnach eine spezielle Firmware für mbus mit einer TTY_BUFSIZE von 300 drauf.
WMBUS Error during LinkLayer parse:message too short, expected 160, got 148 bytes
Please make sure that TTY_BUFSIZE in culfw is at least two times the message length + 1
Du benötigst aber eine Firmware mit einer TTY_BUFSIZE von mindestens 321.

Du kannst ja mal bei smart-home-komponente nachfragen.

Gruß Ralf
FHEM auf Cubietruck mit Igor-Image, SSD und  hmland + HM-CFG-USB-2,  HMUARTLGW Lan,   HM-LC-Bl1PBU-FM, HM-CC-RT-DN, HM-SEC-SC-2, HM-MOD-Re-8, HM-MOD-Em-8
HM-Wired:  HMW_IO_12_FM, HMW_Sen_SC_12_DR, Selbstbau IO-Module HBW_IO_SW
Maple-SIGNALduino, WH3080,  Hideki, Id 7