Pairing nanoCUL 868 mit MAX! Heizkörperthermostat basic geht nicht

[copystring]

Hallo,

vor einiger Zeit habe ich mit FHEM angefangen. Lief bisher super.
Seitdem ich die Batterien vom Thermostat wechseln musste, lässt sich das Thermostat nicht mehr mit meinem nanoCUL verbinden bzw. anlernen.
Als das Thermostat noch neu war, lief alles sauber durch.
Bisher habe ich folgendes probiert:
- Factoryreset des Thermostats
- culfw 1.66, culfw 1.67 und a-culfw 1.26.00
- alle MAX und 868 CULs aus FHEM entfernt
- Updates für FHEM und raspbian (debian 9.1) eingespielt

Wenn ich es dann doch über Umwege und nach einem Neustart vom FHEM schaffe, dass das Pairing dann doch anspringt, dann kommt folgendes:

Code Auswählen Erweitern

2017.09.17 12:05:01 3: CUL_MAX_Parse: Pairing device 145f67 of type Cube with serial
2017.09.17 12:05:01 2: Got message for undefined device 145f67, and failed to guess type from msg 'define' - ignoring
2017.09.17 12:05:01 3: CUL868: Unknown code ZERR1F1, help me!
2017.09.17 12:05:08 3: CUL868: Unknown code ZERR2F1, help me!
2017.09.17 12:05:14 3: CUL868: Unknown code ZERR1F1, help me!
2017.09.17 12:05:21 3: CUL868: Unknown code ZERR1F1, help me!
2017.09.17 12:05:24 2: CUL_MAX_SendQueueHandler: Missing ack from 145f67 for 0b010001123456145f670000
2017.09.17 12:11:42 2: CUL_MAX_Parse: Got unhandled message type 31
2017.09.17 12:14:02 3: CUL868: Unknown code Z01A1, help me!
2017.09.17 12:16:39 2: CUL_MAX_Parse: Got unhandled message type 37
2017.09.17 12:16:43 3: CUL868: Unknown code Z01A1, help me!

Meine config:

Code Auswählen Erweitern

defmod CUL868 CUL /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0@38400 0000
attr CUL868 rfmode MAX
attr CUL868 room PC Zimmer

setstate CUL868 2017-09-17 15:06:09 cmds  A B C E e F f G h i K k l M m R T t U V W X x Y Z z
setstate CUL868 2017-09-17 14:38:18 credit10ms 301
setstate CUL868 2017-09-17 15:29:12 state Initialized



Code Auswählen Erweitern

defmod cm CUL_MAX 123456
attr cm IODev CUL868
attr cm room PC Zimmer

setstate cm Defined
setstate cm 2017-09-17 14:38:30 packetsLost 6



Wie man sehen kann, steht die Verbindung zum CUL auf Initialized.

Momentan bin mit meinem Latein am Ende und habe das Gefühl, dass das Thermostat defekt ist. Vor Allem, weil das Thermostat als Cube erkannt wird und nicht als Thermostat.

Hat jemand noch eine Idee was ich (falsch) machen kann?

[RaspiLED]

Ja, nimm ne 1.23 oder die neue 1.26.1 siehe:
https://forum.fhem.de/index.php?topic=38404.msg686404#msg686404
Gruß Arnd


Raspi2 mit FHEM, CUL, Signalduino, MySensors, HomeBridge, Presence, Bravia, ...

[copystring]

Danke für den Tip. Habe heute 1.26.01 geflasht. Pairing geht leider trotzdem nicht...

[copystring]

Um einen Fehler an meinem raspbian auszuschließen habe ich kurzerhand ein frisches Ubuntu aufgesetzt und dort mit FHEM versucht eine verbindung aufzbauen. Auch dort klappt es nicht.

Code Auswählen Erweitern



2017.09.20 22:12:01 1: Including fhem.cfg
2017.09.20 22:12:01 3: telnetPort: port 7072 opened
2017.09.20 22:12:02 3: WEB: port 8083 opened
2017.09.20 22:12:02 3: WEBphone: port 8084 opened
2017.09.20 22:12:02 3: WEBtablet: port 8085 opened
2017.09.20 22:12:02 1: Including fhem.cfg
2017.09.20 22:12:02 3: telnetPort: port 7072 opened
2017.09.20 22:12:02 3: WEB: port 8083 opened
2017.09.20 22:12:02 3: WEBphone: port 8084 opened
2017.09.20 22:12:02 3: WEBtablet: port 8085 opened
2017.09.20 22:12:02 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2017.09.20 22:12:02 1: Including ./log/fhem.save
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Initialize redefined at ./FHEM/92_FileLog.pm line 31.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_dailySwitch redefined at ./FHEM/92_FileLog.pm line 75.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Define redefined at ./FHEM/92_FileLog.pm line 90.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Undef redefined at ./FHEM/92_FileLog.pm line 126.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Delete redefined at ./FHEM/92_FileLog.pm line 135.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Switch redefined at ./FHEM/92_FileLog.pm line 145.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Log redefined at ./FHEM/92_FileLog.pm line 172.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Attr redefined at ./FHEM/92_FileLog.pm line 232.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Set redefined at ./FHEM/92_FileLog.pm line 255.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_loadSVG redefined at ./FHEM/92_FileLog.pm line 357.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_fhemwebFn redefined at ./FHEM/92_FileLog.pm line 367.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_toSVG redefined at ./FHEM/92_FileLog.pm line 457.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_logWrapper redefined at ./FHEM/92_FileLog.pm line 481.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine expandFileWildcards redefined at ./FHEM/92_FileLog.pm line 614.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_Get redefined at ./FHEM/92_FileLog.pm line 576.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine seekBackOneLine redefined at ./FHEM/92_FileLog.pm line 933.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_seekTo redefined at ./FHEM/92_FileLog.pm line 955.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_addTics redefined at ./FHEM/92_FileLog.pm line 999.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_sampleDataFn redefined at ./FHEM/92_FileLog.pm line 1007.
2017.09.20 22:12:02 1: PERL WARNING: Subroutine FileLog_regexpFn redefined at ./FHEM/92_FileLog.pm line 1066.
2017.09.20 22:12:02 1: Including ./log/fhem.save
2017.09.20 22:12:02 1: configfile: autocreate already defined, delete it first
eventTypes already defined, delete it first
initialUsbCheck already defined, delete it first

2017.09.20 22:12:02 1: usb create starting
2017.09.20 22:12:02 1: usb create end
2017.09.20 22:12:02 2: Messages collected while initializing FHEM: configfile: autocreate already defined, delete it first eventTypes already defined, delete it first initialUsbCheck already defined, delete it first
2017.09.20 22:12:02 0: Featurelevel: 5.8
2017.09.20 22:12:02 0: Server started with 9 defined entities (fhem.pl:13447/2017-02-19 perl:5.022001 os:linux user:fhem pid:5646)
2017.09.20 22:12:15 0: Server shutdown
2017.09.20 22:12:18 1: Including fhem.cfg
2017.09.20 22:12:18 3: telnetPort: port 7072 opened
2017.09.20 22:12:18 3: WEB: port 8083 opened
2017.09.20 22:12:18 3: WEBphone: port 8084 opened
2017.09.20 22:12:18 3: WEBtablet: port 8085 opened
2017.09.20 22:12:18 2: eventTypes: loaded 0 events from ./log/eventTypes.txt
2017.09.20 22:12:18 1: Including ./log/fhem.save
2017.09.20 22:12:18 1: usb create starting
2017.09.20 22:12:18 1: usb create end
2017.09.20 22:12:18 2: SecurityCheck:  WEB,WEBphone,WEBtablet has no associated allowed device with basicAuth. telnetPort has no associated allowed device with password/globalpassword.  Restart FHEM for a new check if the problem is fixed, or set the global attribute motd to none to supress this message.
2017.09.20 22:12:18 0: Featurelevel: 5.8
2017.09.20 22:12:18 0: Server started with 9 defined entities (fhem.pl:13447/2017-02-19 perl:5.022001 os:linux user:fhem pid:5748)
2017.09.20 22:13:24 2: wrong syntax: define <name> CUL {none | devicename[@baudrate] | devicename@directio | hostname:port} <FHTID>
2017.09.20 22:13:24 1: define CUL868 CUL: wrong syntax: define <name> CUL {none | devicename[@baudrate] | devicename@directio | hostname:port} <FHTID>
2017.09.20 22:14:33 3: Opening CUL868 device /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0
2017.09.20 22:14:33 3: Can't open /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0: No such file or directory
2017.09.20 22:15:14 3: Opening CUL868 device /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0
2017.09.20 22:15:14 3: Can't open /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0: No such file or directory
2017.09.20 22:15:40 3: Opening CUL868 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0
2017.09.20 22:15:40 3: Setting CUL868 serial parameters to 9600,8,N,1
2017.09.20 22:15:49 1: Cannot init /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0, ignoring it (CUL868)
2017.09.20 22:16:01 3: Opening CUL868 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0
2017.09.20 22:16:01 3: Setting CUL868 serial parameters to 38400,8,N,1
2017.09.20 22:16:04 3: CUL868: Possible commands: ABCEeFfGiKlMNRTtUVWXxZ
2017.09.20 22:16:04 3: CUL868 device opened
2017.09.20 22:16:56 1: define cm CUL_MAX: wrong syntax: define <name> CUL_MAX <srcAddr>
2017.09.20 22:17:07 1: The adress must be 6 hexadecimal digits
2017.09.20 22:17:07 1: define cm CUL_MAX 12345: The adress must be 6 hexadecimal digits
2017.09.20 22:17:45 3: No I/O device found for cm
2017.09.20 22:17:45 1: cm: did not find suitable IODev (CUL etc. in rfmode MAX)! You may want to execute 'attr cm IODev SomeCUL'
2017.09.20 22:18:59 2: Switched CUL868 rfmode to MAX
2017.09.20 22:19:35 3: CUL_MAX_Parse: Pairing device 000000 of type Cube with serial
2017.09.20 22:19:35 2: Got message for undefined device 000000, and failed to guess type from msg 'define' - ignoring
2017.09.20 22:19:35 2: CUL868: unknown message ZERR100
2017.09.20 22:19:40 3: CUL_MAX_Parse: Pairing device 000000 of type Cube with serial
2017.09.20 22:19:40 1: ERROR: empty name in readingsBeginUpdate
2017.09.20 22:19:40 1: stacktrace:
2017.09.20 22:19:40 1:     main::readingsBeginUpdate           called by ./FHEM/10_MAX.pm (642)
2017.09.20 22:19:40 1:     main::MAX_Parse                     called by fhem.pl (3515)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/14_CUL_MAX.pm (357)
2017.09.20 22:19:40 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:40 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:40 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:40 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:40 1: PERL WARNING: Use of uninitialized value in string ne at ./FHEM/10_MAX.pm line 645.
2017.09.20 22:19:40 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/10_MAX.pm line 645.
2017.09.20 22:19:40 1: Device changed type from  to Cube
2017.09.20 22:19:40 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at fhem.pl line 4189.
2017.09.20 22:19:40 1: readingsUpdate(,groupid,0) missed to call readingsBeginUpdate first.
2017.09.20 22:19:40 1: stacktrace:
2017.09.20 22:19:40 1:     main::readingsBulkUpdate            called by ./FHEM/10_MAX.pm (652)
2017.09.20 22:19:40 1:     main::MAX_Parse                     called by fhem.pl (3515)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/14_CUL_MAX.pm (357)
2017.09.20 22:19:40 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:40 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:40 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:40 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:40 1: readingsUpdate(,state,waiting for data) missed to call readingsBeginUpdate first.
2017.09.20 22:19:40 1: stacktrace:
2017.09.20 22:19:40 1:     main::readingsBulkUpdate            called by ./FHEM/10_MAX.pm (883)
2017.09.20 22:19:40 1:     main::MAX_Parse                     called by fhem.pl (3515)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/14_CUL_MAX.pm (357)
2017.09.20 22:19:40 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:40 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:40 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:40 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:40 1: readingsUpdate(,RSSI,-74) missed to call readingsBeginUpdate first.
2017.09.20 22:19:40 1: stacktrace:
2017.09.20 22:19:40 1:     main::readingsBulkUpdate            called by ./FHEM/10_MAX.pm (884)
2017.09.20 22:19:40 1:     main::MAX_Parse                     called by fhem.pl (3515)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/14_CUL_MAX.pm (357)
2017.09.20 22:19:40 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:40 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:40 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:40 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:40 3: cm: Unknown code MAX,0,define,000000,Cube,,0, help me!
2017.09.20 22:19:40 1: ERROR: empty name in readingsBeginUpdate
2017.09.20 22:19:40 1: stacktrace:
2017.09.20 22:19:40 1:     main::readingsBeginUpdate           called by ./FHEM/14_CUL_MAX.pm (362)
2017.09.20 22:19:40 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:40 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:40 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:40 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:40 1: readingsUpdate(,firmware,0.0) missed to call readingsBeginUpdate first.
2017.09.20 22:19:40 1: stacktrace:
2017.09.20 22:19:40 1:     main::readingsBulkUpdate            called by ./FHEM/14_CUL_MAX.pm (363)
2017.09.20 22:19:40 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:40 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:40 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:40 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:40 1: readingsUpdate(,testresult,0) missed to call readingsBeginUpdate first.
2017.09.20 22:19:40 1: stacktrace:
2017.09.20 22:19:40 1:     main::readingsBulkUpdate            called by ./FHEM/14_CUL_MAX.pm (364)
2017.09.20 22:19:40 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:40 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:40 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:40 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:40 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:40 1: PERL WARNING: Use of uninitialized value $dev in hash element at fhem.pl line 3180.
2017.09.20 22:19:41 2: CUL868: unknown message ZERR100
2017.09.20 22:19:45 3: CUL_MAX_Parse: Pairing device 000000 of type Cube with serial
2017.09.20 22:19:45 1: ERROR: empty name in readingsBeginUpdate
2017.09.20 22:19:45 1: stacktrace:
2017.09.20 22:19:45 1:     main::readingsBeginUpdate           called by ./FHEM/10_MAX.pm (642)
2017.09.20 22:19:45 1:     main::MAX_Parse                     called by fhem.pl (3515)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/14_CUL_MAX.pm (357)
2017.09.20 22:19:45 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:45 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:45 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:45 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:45 1: readingsUpdate(,groupid,0) missed to call readingsBeginUpdate first.
2017.09.20 22:19:45 1: stacktrace:
2017.09.20 22:19:45 1:     main::readingsBulkUpdate            called by ./FHEM/10_MAX.pm (652)
2017.09.20 22:19:45 1:     main::MAX_Parse                     called by fhem.pl (3515)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/14_CUL_MAX.pm (357)
2017.09.20 22:19:45 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:45 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:45 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:45 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:45 1: readingsUpdate(,state,waiting for data) missed to call readingsBeginUpdate first.
2017.09.20 22:19:45 1: stacktrace:
2017.09.20 22:19:45 1:     main::readingsBulkUpdate            called by ./FHEM/10_MAX.pm (883)
2017.09.20 22:19:45 1:     main::MAX_Parse                     called by fhem.pl (3515)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/14_CUL_MAX.pm (357)
2017.09.20 22:19:45 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:45 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:45 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:45 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:45 1: readingsUpdate(,RSSI,-74) missed to call readingsBeginUpdate first.
2017.09.20 22:19:45 1: stacktrace:
2017.09.20 22:19:45 1:     main::readingsBulkUpdate            called by ./FHEM/10_MAX.pm (884)
2017.09.20 22:19:45 1:     main::MAX_Parse                     called by fhem.pl (3515)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/14_CUL_MAX.pm (357)
2017.09.20 22:19:45 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:45 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:45 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:45 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:45 3: cm: Unknown code MAX,0,define,000000,Cube,,0, help me!
2017.09.20 22:19:45 1: ERROR: empty name in readingsBeginUpdate
2017.09.20 22:19:45 1: stacktrace:
2017.09.20 22:19:45 1:     main::readingsBeginUpdate           called by ./FHEM/14_CUL_MAX.pm (362)
2017.09.20 22:19:45 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:45 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:45 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:45 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:45 1: readingsUpdate(,firmware,0.0) missed to call readingsBeginUpdate first.
2017.09.20 22:19:45 1: stacktrace:
2017.09.20 22:19:45 1:     main::readingsBulkUpdate            called by ./FHEM/14_CUL_MAX.pm (363)
2017.09.20 22:19:45 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:45 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:45 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:45 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:45 1: readingsUpdate(,testresult,0) missed to call readingsBeginUpdate first.
2017.09.20 22:19:45 1: stacktrace:
2017.09.20 22:19:45 1:     main::readingsBulkUpdate            called by ./FHEM/14_CUL_MAX.pm (364)
2017.09.20 22:19:45 1:     main::CUL_MAX_Parse                 called by fhem.pl (3497)
2017.09.20 22:19:45 1:     main::Dispatch                      called by ./FHEM/00_CUL.pm (969)
2017.09.20 22:19:45 1:     main::CUL_Parse                     called by ./FHEM/00_CUL.pm (825)
2017.09.20 22:19:45 1:     main::CUL_Read                      called by fhem.pl (3302)
2017.09.20 22:19:45 1:     main::CallFn                        called by fhem.pl (674)
2017.09.20 22:19:48 2: CUL868: unknown message ZERR100
2017.09.20 22:19:54 2: CUL868: unknown message ZERR100
2017.09.20 22:19:58 2: CUL_MAX_SendQueueHandler: Missing ack from 000000 for 0b0100011234560000000000
2017.09.20 22:19:58 2: CUL868: unknown message ZERR100
2017.09.20 22:20:04 2: CUL868: unknown message ZERR100
2017.09.20 22:20:11 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 43, but we need 110. Waiting 67 seconds. Currently 2 messages are waiting to be sent.
2017.09.20 22:21:19 2: CUL868: unknown message ZERR2F1
2017.09.20 22:21:25 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 2 messages are waiting to be sent.

[Esjay]

Code Auswählen Erweitern

2017.09.20 22:13:24 2: wrong syntax: define <name> CUL {none | devicename[@baudrate] | devicename@directio | hostname:port} <FHTID>
2017.09.20 22:13:24 1: define CUL868 CUL: wrong syntax: define <name> CUL {none | devicename[@baudrate] | devicename@directio | hostname:port} <FHTID>
2017.09.20 22:14:33 3: Opening CUL868 device /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0
2017.09.20 22:14:33 3: Can't open /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0: No such file or directory
2017.09.20 22:15:14 3: Opening CUL868 device /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0
2017.09.20 22:15:14 3: Can't open /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0: No such file or directory
2017.09.20 22:15:40 3: Opening CUL868 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0
2017.09.20 22:15:40 3: Setting CUL868 serial parameters to 9600,8,N,1
2017.09.20 22:15:49 1: Cannot init /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0, ignoring it (CUL868)
2017.09.20 22:16:01 3: Opening CUL868 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0
define cm CUL_MAX: wrong syntax: define <name> CUL_MAX <srcAddr>
2017.09.20 22:17:07 1: The adress must be 6 hexadecimal digits
2017.09.20 22:17:07 1: define cm CUL_MAX 12345: The adress must be 6 hexadecimal digits

Code Auswählen Erweitern

2017.09.20 22:20:11 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 43, but we need 110. Waiting 67 seconds. Currently 2 messages are waiting to be sent.
2017.09.20 22:21:19 2: CUL868: unknown message ZERR2F1
2017.09.20 22:21:25 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 2 messages are waiting to be sent.

Das nenne ich mal ne ordentliche Ansammlung von Fehlermeldungen. Kann es sein, das du in der fhem.cfg rumhantierst? An welche Anleitung hast du dich denn gehalten? Wiki oder externe Seite?

Solltest du in der config rumhantieren, wird die Bereitschaft dir zu helfen gegen 0 gehen. Da ich meine zu erkennen, das das deine Ersten Schritte in fhem sind, würde ich dir ganz klar entweder zur Pflichtlektüre raten -->

Code Auswählen Erweitern

https://fhem.de/Heimautomatisierung-mit-fhem.pdf oder auf die Youtube Reihe von hausautomatisierung.com verweisen, falls du eher der Visuelle Typ bist.

Ebenso gerne nochmal hier durchlesen -->

Code Auswählen Erweitern

https://forum.fhem.de/index.php/topic,71806.0.html

Wenn du dann ne Base hast, und deine ganzen Fehlermeldungen sich mit dem durcharbeiten der Lektüre erledigt haben, wird dir sicher gerne weitergeholfen.

Gruß

[Beta-User]

Scheint kein direktes Editieren zu sein, ist aus raw-Def, oder?

Was nicht stimmt, ist das DEF:

2017.09.20 22:14:33 3: Opening CUL868 device /dev/serial/dy-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0

dy-id sollte by-id sein, oder?

[copystring]

Scheint kein direktes Editieren zu sein, ist aus raw-Def, oder?

Was nicht stimmt, ist das DEF: dy-id sollte by-id sein, oder?

Ja hatte mich vertan und später korrigiert.
Sieht man auch im log

@Esjay
Habe an der config selbst nicht von hand geändert und habe mich an das WIKI von hier gehalten: https://wiki.fhem.de/wiki/MAX#Anlernen_per_CUL
In dem Ubuntu, welches ich zum Testen neu aufgesetzt habe, habe ich nur folgendes getan:

Code Auswählen Erweitern

define CUL868 CUL /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A5050UY1-if00-port0@38400 0000
attr CUL868 rfmode MAX
define cm CUL_MAX 123456
set cm pairmode

Dann tauchten die Fehler auf.

[copystring]

Habe jetzt mal geguckt, was passiert mit loglevel verbose 5

Code Auswählen Erweitern

2017.09.23 16:57:21 4: CUL_Parse: CUL868 Z17000400144F23000000000000000000000000000000000000 -74
2017.09.23 16:57:21 5: CUL868: dispatch Z17000400144F230000000000000000000000000000000000
2017.09.23 16:57:21 5: CUL_MAX_Parse: len 23, msgcnt 00, msgflag 04, msgTypeRaw PairPing, src 144f23, dst 000000, groupid 0, payload 00000000000000000000000000
2017.09.23 16:57:21 5: CUL_MAX_Parse: Got PairPing (dst 000000, pairmode 1), firmware 0, type 0, testresult 0, serial
2017.09.23 16:57:21 3: CUL_MAX_Parse: Pairing device 144f23 of type Cube with serial
2017.09.23 16:57:21 5: cm: dispatch MAX,0,define,144f23,Cube,\000\000\000\000\000\000\000\000\000\000,0
2017.09.23 16:57:21 5: Loading ./FHEM/10_MAX.pm
2017.09.23 16:57:21 5: Calling MAX_Initialize
2017.09.23 16:57:21 5: MAX_Parse MAX,0,define,144f23,Cube,,0
2017.09.23 16:57:21 2: Got message for undefined device 144f23, and failed to guess type from msg 'define' - ignoring
2017.09.23 16:57:21 5: CUL_MAX_Send: enqueuing 0b010001123456144f230000
2017.09.23 16:57:21 5: CUL_MAX_SendQueueHandler: 1 items in queue
2017.09.23 16:57:21 5: SW: X
2017.09.23 16:57:21 5: CUL/RAW (ReadAnswer): 21  519

2017.09.23 16:57:21 5: Starting notify loop for CUL868, 1 event(s), first is credit10ms: 519
2017.09.23 16:57:21 5: End notify loop for CUL868
2017.09.23 16:57:21 5: needPreamble: 1, necessaryCredit: 110, credit10ms: 519
2017.09.23 16:57:21 5: CUL868 sending Zs0b010001123456144f230000
2017.09.23 16:57:21 5: SW: Zs0b010001123456144f230000
2017.09.23 16:57:21 5: CUL/RAW: /ZERR1F1

2017.09.23 16:57:21 4: CUL_Parse: CUL868 ZERR1F1
2017.09.23 16:57:21 5: CUL868: dispatch ZERR1F1
2017.09.23 16:57:21 5: Starting notify loop for CUL868, 1 event(s), first is UNKNOWNCODE ZERR1F1
2017.09.23 16:57:21 5: End notify loop for CUL868
2017.09.23 16:57:21 3: CUL868: Unknown code ZERR1F1, help me!
2017.09.23 16:57:22 5: CUL_MAX_SendQueueHandler: 1 items in queue
2017.09.23 16:57:22 5: CUL_MAX_SendQueueHandler: 1 items in queue
2017.09.23 16:57:23 5: CUL_MAX_SendQueueHandler: 1 items in queue
2017.09.23 16:57:23 5: CUL_MAX_SendQueueHandler: 1 items in queue
2017.09.23 16:57:24 5: CUL_MAX_SendQueueHandler: 1 items in queue

[copystring]

Mittlerweile habe ich mir ein zweites Themostat gekauft. Auch damit läuft es nicht.
Dann habe ich festgestellt, dass eins von den Kabeln am nanoCUL defekt war. Nach dem Austauschen läuft wieder alles. Thema hat sich somit erledigt