Hallo zusammen,
Ich hab letztes Wochenende die 16GB des Pis gegen eine 64GB ausgetauscht (die 16GB 1:1 auf die 64GB geklont und erweitert).
Danach musste ich ein paar Module (Netatmo, Fritzbox und GoogleAssistant) neu einrichten, bzw neu einloggen.
Zudem hab ich bei dieser Aktion auch den Pi und Fhem upgedatet.
Nun werden alle vier Thermometer (1) nicht mehr mit den Werten ausgefüllt. Der Sduino funktioniert mit den Steckdosen ganz gut.
Ebenso wie ein Thermostat (2) und ein Fensterkontakt (3) von Max.
Löschen und per define neu eintragen hat lieder nichts gepracht. Ebenso wie autocreate und neustart.
Hat mir jemand einen Tipp?
1) Thermometer: renkforce
defmod Paul.Temperatur SD_WS SD_WS_58_TH_4
attr Paul.Temperatur event-on-change-reading .*
attr Paul.Temperatur genericDeviceType thermometer
attr Paul.Temperatur room Wohnzimmer
setstate Paul.Temperatur Defined
sduino
defmod sduino SIGNALduino /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0@57600
attr sduino blacklist_IDs 61
attr sduino flashCommand avrdude -c arduino -b 57600 -P [PORT] -p atmega328p -vv -U flash:w:[HEXFILE] 2>[LOGFILE]
attr sduino group X_Technik
attr sduino hardware nano328
attr sduino verbose 5
setstate sduino opened
setstate sduino 2019-06-20 20:07:24 ping OK
setstate sduino 2019-06-20 19:29:23 state opened
setstate sduino 2019-06-20 19:33:53 uptime 0 00:04:55
setstate sduino 2019-06-20 19:29:23 version V 3.3.1-dev SIGNALduino - compiled at Jan 3 2017 23:59:32
2) CUL: MAX
CUL
defmod cm CUL_MAX 123456
attr cm IODev CUL0
attr cm room Technik
setstate cm Defined
setstate cm 2019-06-20 19:04:36 packetsLost 58
Theermostat: MAX
defmod Kueche.Thermostat MAX HeatingThermostat 1aab85
attr Kueche.Thermostat IODev cm
attr Kueche.Thermostat room GoogleAssistant,MAX
setstate Kueche.Thermostat off °C
setstate Kueche.Thermostat 2019-06-20 11:44:12 RSSI -78
setstate Kueche.Thermostat 2019-06-15 01:01:11 TimeInformationHour 1
setstate Kueche.Thermostat 2019-06-20 11:44:12 battery ok
setstate Kueche.Thermostat 2019-06-20 11:44:12 batteryState ok
setstate Kueche.Thermostat 2019-06-20 11:44:12 desiredTemperature off
setstate Kueche.Thermostat 2019-06-15 01:01:08 groupid 0
setstate Kueche.Thermostat 2019-06-20 11:44:12 mode manual
setstate Kueche.Thermostat 2019-06-20 19:04:13 msgcnt 104
setstate Kueche.Thermostat 2019-06-20 11:44:12 state off °C
setstate Kueche.Thermostat 2019-06-20 11:44:12 valveposition 0
3) Fensterkonakt: MAX
defmod Wohnzimmer.Fenster1 MAX ShutterContact 189eac
attr Wohnzimmer.Fenster1 userattr room_map structexclude
attr Wohnzimmer.Fenster1 IODev cm
attr Wohnzimmer.Fenster1 event-on-change-reading state
attr Wohnzimmer.Fenster1 genericDeviceType window
attr Wohnzimmer.Fenster1 room GoogleAssistant,MAX
setstate Wohnzimmer.Fenster1 2019-06-20 17:42:09 msgcnt 2
Gruß Dominik
Ich hab nun Fhem komplett neu aufgesetzt.
Alle Thermostate und ein Fensterkontakt auf Werkseinstellung gesetzt.
Es funktioniert immer noch nicht.
Und auch die Thermometer werden nicht automatisch angelernt.
Hat mir wirklich niemand einen Tipp, wo ich anfangen kann den Fehler zu suchen?
Bitte poste mal vom sduino einen kurzen log Auszug mit verbose 4.
Gruß Ralf
Zu deinem Max-Problem, beim cul fehlt
attr rfmode MAX
Poste mal bitte ein list von CUL und vom sduino, mich interessiert vor allem wie diese eingebunden sind. Nicht das bloß die ports vertauscht sind.
Zitat von: bartman121 am 24 Juni 2019, 18:41:03
Zu deinem Max-Problem, beim cul fehlt
attr rfmode MAX
Jup, das war es bei den Thermostaten und den Fensterkontakten.
Nun funktionieren diese wieder.
## Edit: Oder doch nicht. Weiter unten sind mehr Infos ##
Die Thermometer funktionieren noch nicht.
List Sduino:
Internals:
Clients :IT:CUL_TCM97001:SD_RSL:OREGON:CUL_TX:SD_AS:Hideki:SD_WS07:SD_WS09: :SD_WS:RFXX10REC:Dooya:SOMFY:SD_BELL:SD_UT:SD_WS_Maverick:FLAMINGO:CUL_WS:Revolt: :FS10:CUL_FHTTK:Siro:FHT:FS20:CUL_EM:Fernotron:SIGNALduino_un:
DEF /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0@57600
DMSG P7#5B81E5F13
DevState initialized
DeviceName /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0@57600
FD 7
FUUID 5d0e8c2a-f33f-39e8-3935-4048067fb6c5a03b
IDsNoDispatch 2,72.1,82
ITClock 250
LASTDMSG P7#5B81E5F13
MSGCNT 535
NAME sduino
NR 16
NR_CMD_LAST_H 16
PARTIAL
RAWMSG MS;P0=553;P1=-976;P2=-1939;P3=-3876;D=03010201020201020202010101010101020202020101020102020202020101010201010202;CP=0;SP=3;
STATE opened
TIME 1561573838
TYPE SIGNALduino
sendworking 0
version V 3.3.1-dev SIGNALduino - compiled at Jan 3 2017 23:59:32
versionmodul v3.3.3
DoubleMsgIDs:
MatchList:
10:SD_WS07 ^P7#[A-Fa-f0-9]{6}F[A-Fa-f0-9]{2}(#R[A-F0-9][A-F0-9]){0,1}$
11:SD_WS09 ^P9#F[A-Fa-f0-9]+
12:SD_WS ^W\d+x{0,1}#.*
13:RFXX10REC ^(20|29)[A-Fa-f0-9]+
14:Dooya ^P16#[A-Fa-f0-9]+
15:SOMFY ^Ys[0-9A-F]+
16:SD_WS_Maverick ^P47#[A-Fa-f0-9]+
17:SD_UT ^P(?:14|29|30|34|46|69|76|81|83|86|90|91|91.1|92)#.*
18:FLAMINGO ^P13\.?1?#[A-Fa-f0-9]+
19:CUL_WS ^K[A-Fa-f0-9]{5,}
1:IT ^i......
20:Revolt ^r[A-Fa-f0-9]{22}
21:FS10 ^P61#[A-F0-9]+
22:Siro ^P72#[A-Fa-f0-9]+
23:FHT ^81..(04|09|0d)..(0909a001|83098301|c409c401)..
24:FS20 ^81..(04|0c)..0101a001
25:CUL_EM ^E0.................
26:Fernotron ^P82#.*
27:SD_BELL ^P(?:15|32|41|42|57|79)#.*
2:CUL_TCM97001 ^s[A-Fa-f0-9]+
3:SD_RSL ^P1#[A-Fa-f0-9]{8}
4:OREGON ^(3[8-9A-F]|[4-6][0-9A-F]|7[0-8]).*
5:CUL_TX ^TX..........
6:SD_AS ^P2#[A-Fa-f0-9]{7,8}
7:Hideki ^P12#75[A-F0-9]+
9:CUL_FHTTK ^T[A-F0-9]{8}
X:SIGNALduino_un ^[u]\d+#.*
QUEUE:
READINGS:
2019-06-26 20:14:56 ping OK
2019-06-25 22:22:54 state opened
2019-06-25 22:22:54 version V 3.3.1-dev SIGNALduino - compiled at Jan 3 2017 23:59:32
XMIT_TIME:
1561572034
1561572036
1561572038
1561572041
1561572283
1561572285
1561572290
1561572610
1561572612
1561572615
1561572830
1561573044
1561573045
1561573047
1561573249
1561573420
getcmd:
keepalive:
ok 0
retry 0
mcIdList:
10
11
12
18
43
47
52
57
58
msIdList:
0
0.1
0.2
0.3
0.4
1
3
3.1
4
6
7
13
13.2
14
15
17
23
25
33
35
41
51
55
65
90
91.1
muIdList:
8
9
13.1
16
17.1
19
21
22
24
26
27
28
29
30
31
32
34
36
37
38
39
40
42
44
44.1
45
46
48
49
50
56
59
60
61
62
64
66
67
69
70
71
72
74
76
79
80
81
83
84
85
86
89
91
92
Attributes:
verbose 4
Logauszug
2019.06.26 20:31:48 3: sduino: setting Verbose to: 4
2019.06.26 20:31:56 4: sduino/keepalive ok, retry = 0
2019.06.26 20:32:32 4: sduino/msg READ: MS;P0=-1925;P1=537;P2=-3902;P3=-947;P4=94;P5=-120;P6=-420;P7=-1432;D=121310131010131010101313131313131010104513101013164710101010101313131013131010;CP=1;SP=2;
2019.06.26 20:32:32 4: sduino: Matched MS Protocol id 7 -> weather
2019.06.26 20:32:32 4: sduino/msg READ: MS;P1=515;P2=-1909;P3=-978;P4=-3869;P5=-1436;D=14131213121213121212131313131315121212131212131212121212121313131213131212;CP=1;SP=4;O;
2019.06.26 20:32:32 4: sduino: Matched MS Protocol id 7 -> weather
2019.06.26 20:32:32 4: sduino: Matched MS Protocol id 91.1 -> Atlantic security
2019.06.26 20:32:32 4: sduino/msg READ: MS;P1=-955;P2=550;P3=-1944;P4=-3894;D=24212321232321232323212121212121232323212323212323232323232121212321212323;CP=2;SP=4;
2019.06.26 20:32:32 4: sduino: Matched MS Protocol id 7 -> weather
2019.06.26 20:32:32 4: sduino: Decoded MS Protocol id 7 dmsg P7#5B81DBF13 length 36
2019.06.26 20:32:32 4: sduino: SD_WS07_Parse SD_WS07 (P7#5B81DBF13) length: 9
2019.06.26 20:32:32 4: sduino: SD_WS07_Parse SD_WS07 converted to bits 01011011 1000 000111011011 1111 00010011
2019.06.26 20:32:32 4: sduino: Wohnzimmer.Temperatur id=5B, channel=1, temp=47.5, hum=19, bat=ok
2019.06.26 20:32:32 4: sduino: Matched MS Protocol id 91.1 -> Atlantic security
2019.06.26 20:32:56 4: sduino/keepalive ok, retry = 0
2019.06.26 20:33:29 4: sduino/msg READ: MS;P1=-1923;P2=515;P3=-956;P4=-3889;D=24232123212123212121232323232323212121232121212323212121212323232123232121;CP=2;SP=4;O;
2019.06.26 20:33:29 4: sduino: Matched MS Protocol id 7 -> weather
2019.06.26 20:33:29 4: sduino: Decoded MS Protocol id 7 dmsg P7#5B81DCF13 length 36
2019.06.26 20:33:29 4: sduino: SD_WS07_Parse SD_WS07 (P7#5B81DCF13) length: 9
2019.06.26 20:33:29 4: sduino: SD_WS07_Parse SD_WS07 converted to bits 01011011 1000 000111011100 1111 00010011
2019.06.26 20:33:29 4: sduino: Wohnzimmer.Temperatur id=5B, channel=1, temp=47.6, hum=19, bat=ok
2019.06.26 20:33:29 4: sduino: Matched MS Protocol id 91.1 -> Atlantic security
2019.06.26 20:33:56 4: sduino/keepalive ok, retry = 0
2019.06.26 20:34:26 4: sduino/msg READ: MS;P1=-978;P3=487;P5=-1943;P6=-3900;D=36313531353531353535313131313131353535313535313531353535353131313531353131;CP=3;SP=6;O;
2019.06.26 20:34:26 4: sduino: Matched MS Protocol id 7 -> weather
2019.06.26 20:34:26 4: sduino: Decoded MS Protocol id 7 dmsg P7#5B81DAF14 length 36
2019.06.26 20:34:26 4: sduino: SD_WS07_Parse SD_WS07 (P7#5B81DAF14) length: 9
2019.06.26 20:34:26 4: sduino: SD_WS07_Parse SD_WS07 converted to bits 01011011 1000 000111011010 1111 00010100
2019.06.26 20:34:26 4: sduino: Wohnzimmer.Temperatur id=5B, channel=1, temp=47.4, hum=20, bat=ok
2019.06.26 20:34:26 4: sduino: Matched MS Protocol id 91.1 -> Atlantic security
2019.06.26 20:34:26 4: sduino/msg READ: MS;P0=-953;P1=532;P2=-1948;P3=-3882;D=13101210121210121212101010101010121212101212101210121212121010101210121010;CP=1;SP=3;
2019.06.26 20:34:26 4: sduino: Matched MS Protocol id 7 -> weather
2019.06.26 20:34:26 4: sduino: Decoded MS Protocol id 7 dmsg P7#5B81DAF14 length 36
2019.06.26 20:34:26 4: sduino Dispatch: P7#5B81DAF14, Dropped due to short time or equal msg
2019.06.26 20:34:26 4: sduino: Matched MS Protocol id 91.1 -> Atlantic security
2019.06.26 20:34:26 4: sduino/msg READ: MS;P0=-964;P1=535;P2=-1925;P4=-3910;D=14101210121210121212101010101010121212101212101210121212121010101210121010;CP=1;SP=4;
2019.06.26 20:34:26 4: sduino: Matched MS Protocol id 7 -> weather
2019.06.26 20:34:26 4: sduino: Decoded MS Protocol id 7 dmsg P7#5B81DAF14 length 36
2019.06.26 20:34:26 4: sduino Dispatch: P7#5B81DAF14, Dropped due to short time or equal msg
2019.06.26 20:34:26 4: sduino: Matched MS Protocol id 91.1 -> Atlantic security
2019.06.26 20:34:56 4: sduino/keepalive ok, retry = 0
2019.06.26 20:35:56 4: sduino/KeepAlive not ok, retry = 1 -> get ping
2019.06.26 20:35:56 4: sduino/msg READ: OK
2019.06.26 20:35:57 4: sduino/HandleWriteQueue: nothing to send, stopping timer
2019.06.26 20:36:56 4: sduino/keepalive ok, retry = 0
2019.06.26 20:37:56 4: sduino/KeepAlive not ok, retry = 1 -> get ping
2019.06.26 20:37:56 4: sduino/msg READ: OK
2019.06.26 20:37:57 4: sduino/HandleWriteQueue: nothing to send, stopping timer
2019.06.26 20:38:56 4: sduino/keepalive ok, retry = 0
Das Wohnzimmer.Temperatur Devise, hatte ich am Anfang als mein Devise im verdacht. Aber ist nicht meins.
Alle meine Thermostate liegen aktuell bei 35°C, 31°C, 28°C und -18°C.
Gruß Flipper
###### Ergänzung ####
Heute morgen gab es wieder Neue MAX Geräte und die normalen würden nicht mehr Angepasst. Zudem wurde mein Log mit folgendem geflutet:
2019.06.27 06:30:00 3: sentMsgIdByPeerId return value: _sentMsgId: 8507
2019.06.27 06:30:00 2: CUL_MAX_SendQueueHandler: Missing ack from 000000 for 0b0f00011234560000000000
2019.06.27 06:30:00 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 5, but we need 110. Waiting 105 seconds. Currently 6 messages are waiting to be sent.
2019.06.27 06:31:46 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:31:52 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 6 messages are waiting to be sent.
2019.06.27 06:33:34 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:33:41 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 6 messages are waiting to be sent.
2019.06.27 06:35:24 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:35:30 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 6 messages are waiting to be sent.
2019.06.27 06:37:12 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:37:16 2: CUL_MAX_SendQueueHandler: Missing ack from 000000 for 0b1000011234560000000000
2019.06.27 06:37:16 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 6, but we need 110. Waiting 104 seconds. Currently 5 messages are waiting to be sent.
2019.06.27 06:38:35 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 8914
2019.06.27 06:39:01 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:39:07 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 5 messages are waiting to be sent.
2019.06.27 06:40:03 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 06:40:08 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 06:40:50 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:40:54 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 9645
2019.06.27 06:40:57 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 06:42:39 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:42:45 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 06:44:28 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 06:44:28 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:44:32 2: CUL_MAX_SendQueueHandler: Missing ack from 000000 for 0b1100011234560000000000
2019.06.27 06:44:32 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 6, but we need 110. Waiting 104 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 06:46:17 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:46:23 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 06:48:06 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:48:12 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 06:48:57 1: RMDIR: ./restoreDir/save/2019-06-24
2019.06.27 06:49:15 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 06:49:55 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:50:02 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 8 messages are waiting to be sent.
2019.06.27 06:51:44 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:51:47 2: CUL_MAX_SendQueueHandler: Missing ack from 000000 for 0b1200011234560000000000
2019.06.27 06:51:47 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 6, but we need 110. Waiting 104 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 06:53:32 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:53:39 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 06:55:22 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:55:28 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 06:56:41 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 14724
2019.06.27 06:56:59 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 06:57:10 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:57:15 1: Timeout for XiaomiBTLESens::ExecGatttool_Run reached, terminated process 14925
2019.06.27 06:57:17 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 8 messages are waiting to be sent.
2019.06.27 06:59:00 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 06:59:03 2: CUL_MAX_SendQueueHandler: Missing ack from 000000 for 0b1300011234560000000000
2019.06.27 06:59:03 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 6, but we need 110. Waiting 104 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 07:00:48 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 07:00:55 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 7 messages are waiting to be sent.
2019.06.27 07:01:08 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 07:01:13 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 07:02:37 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 07:02:43 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 8, but we need 110. Waiting 102 seconds. Currently 9 messages are waiting to be sent.
2019.06.27 07:04:26 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 07:04:33 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 9 messages are waiting to be sent.
2019.06.27 07:06:15 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 07:06:18 2: CUL_MAX_SendQueueHandler: Missing ack from 000000 for 0b1400011234560000000000
2019.06.27 07:06:18 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 5, but we need 110. Waiting 105 seconds. Currently 8 messages are waiting to be sent.
2019.06.27 07:08:04 3: CUL0: Unknown code ZERR100, help me!
2019.06.27 07:08:10 2: CUL_MAX_SendQueueHandler: Not enough credit! credit10ms is 9, but we need 110. Waiting 101 seconds. Currently 8 messages are waiting to be sent.
2019.06.27 07:08:15 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 07:08:19 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 07:08:22 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
2019.06.27 07:08:29 3: CUL_MAX_Parse: Pairing device 000000 of type with serial
## Und dann viel hiervon: ##
2019.06.27 08:07:39 3: cm: Unknown code MAX,0,define,000000,Cube,,0, help me!
2019.06.27 08:07:39 1: ERROR: empty name in readingsBeginUpdate
2019.06.27 08:07:39 1: stacktrace:
2019.06.27 08:07:39 1: main::readingsBeginUpdate called by ./FHEM/14_CUL_MAX.pm (362)
2019.06.27 08:07:39 1: main::CUL_MAX_Parse called by fhem.pl (3950)
2019.06.27 08:07:39 1: main::Dispatch called by ./FHEM/00_CUL.pm (948)
2019.06.27 08:07:39 1: main::CUL_Parse called by ./FHEM/00_CUL.pm (832)
2019.06.27 08:07:39 1: main::CUL_Read called by fhem.pl (3754)
2019.06.27 08:07:39 1: main::CallFn called by fhem.pl (748)
2019.06.27 08:07:39 1: readingsUpdate(,firmware,0.0) missed to call readingsBeginUpdate first.
2019.06.27 08:07:39 1: stacktrace:
2019.06.27 08:07:39 1: main::readingsBulkUpdate called by ./FHEM/14_CUL_MAX.pm (363)
2019.06.27 08:07:39 1: main::CUL_MAX_Parse called by fhem.pl (3950)
2019.06.27 08:07:39 1: main::Dispatch called by ./FHEM/00_CUL.pm (948)
2019.06.27 08:07:39 1: main::CUL_Parse called by ./FHEM/00_CUL.pm (832)
2019.06.27 08:07:39 1: main::CUL_Read called by fhem.pl (3754)
2019.06.27 08:07:39 1: main::CallFn called by fhem.pl (748)
2019.06.27 08:07:39 1: readingsUpdate(,testresult,0) missed to call readingsBeginUpdate first.
2019.06.27 08:07:39 1: stacktrace:
2019.06.27 08:07:39 1: main::readingsBulkUpdate called by ./FHEM/14_CUL_MAX.pm (364)
2019.06.27 08:07:39 1: main::CUL_MAX_Parse called by fhem.pl (3950)
2019.06.27 08:07:39 1: main::Dispatch called by ./FHEM/00_CUL.pm (948)
2019.06.27 08:07:39 1: main::CUL_Parse called by ./FHEM/00_CUL.pm (832)
2019.06.27 08:07:39 1: main::CUL_Read called by fhem.pl (3754)
2019.06.27 08:07:39 1: main::CallFn called by fhem.pl (748)
List CUL
Internals:
CMDS ABCEeFfGhiKklMmRTtUVWXxYZz
CUL0_MSGCNT 653
CUL0_TIME 2019-06-27 08:17:02
Clients :CUL_MAX:HMS:CUL_IR:STACKABLE_CC:TSSTACKED:STACKABLE:
DEF /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0@38400 0000
DeviceName /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9M9DV3R-if00-port0@38400
FD 27
FHTID 0000
FUUID 5d113eaf-f33f-39e8-5f52-2a981ca1714ba158
NAME CUL0
NR 157
NR_CMD_LAST_H 34
PARTIAL
RAWMSG ZERR100
RSSI -74
STATE Initialized
TYPE CUL
VERSION V 1.67 nanoCUL868
initString X21
Zr
MatchList:
1:CUL_MAX ^Z........................
8:HMS ^810e04....(1|5|9).a001
D:CUL_IR ^I............
H:STACKABLE_CC ^\*
M:TSSTACKED ^\*
N:STACKABLE ^\*
READINGS:
2019-06-25 22:22:42 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
2019-06-27 08:17:08 credit10ms 8
2019-06-27 08:17:02 state Initialized
XMIT_TIME:
1561612628.89342
1561612737.39737
1561612846.91071
1561612955.46256
1561613064.96478
1561613173.47173
1561613281.98299
1561613391.52286
1561613500.03086
1561613608.6063
1561613718.11355
1561613826.63225
1561613936.1575
1561614044.66245
1561614153.17256
1561614262.6975
1561614371.20735
1561614480.72062
1561614589.27259
1561614697.75935
1561614807.2749
1561614915.78659
1561615025.30069
1561615133.83366
1561615242.33293
1561615351.84273
1561615460.35611
1561615569.88474
1561615677.82572
1561615787.33834
1561615895.86368
1561616005.39152
1561616113.91295
1561616222.42304
Attributes:
rfmode MAX
room Technik
List cm
Internals:
CUL0_MSGCNT 287
CUL0_RAWMSG Z0B9400000000000000000000
CUL0_RSSI -74
CUL0_TIME 2019-06-27 08:10:58
DEF 123456
FUUID 5d0f4c81-f33f-39e8-2081-22bd428fb58d9aaf
IODev CUL0
LASTInputDev CUL0
MSGCNT 287
NAME cm
NR 118
STATE Defined
TYPE CUL_MAX
addr 123456
cnt 0
pairmode 0
retryCount 0
READINGS:
2019-06-27 08:18:55 packetsLost 92
sendQueue:
HASH(0x583b3d0)
HASH(0x5d31850)
HASH(0x58294e0)
HASH(0x5baa7a8)
HASH(0x5f22868)
HASH(0x5d21fa0)
HASH(0x57fa450)
HASH(0x5d364b8)
HASH(0x5e29388)
HASH(0x5ae6c98)
HASH(0x5836a30)
HASH(0x5e4f6e8)
HASH(0x5ad9cc0)
HASH(0x5d1e8d0)
HASH(0x5d4a1b8)
HASH(0x5e4a4d0)
HASH(0x5e27bc8)
HASH(0x5e9ab38)
HASH(0x5d3bcb8)
HASH(0x5ac92c0)
HASH(0x5d6b610)
HASH(0x5857c68)
HASH(0x4d12478)
HASH(0x5d47bf0)
Attributes:
IODev CUL0
room MAX
######### Nachtrag Abend #######
jetzt funktionieren alle MAX Geräte nicht mehr :-/
Bitte mach mal ein
get sduino config
dies müsste so aussehen:
config: MS=1;MU=1;MC=1;...
Gruß Ralf
Zitat von: Ralf9 am 27 Juni 2019, 22:27:59
Bitte mach mal ein
get sduino config
dies müsste so aussehen:
config: MS=1;MU=1;MC=1;...
Sieht etwas anders aus:
config: MS=1;MU=0;MC=0
Hab nun die anderen auch aktiviert. Jetzt:
config: MS=1;MU=1;MC=1
Gruß Flipper
ZitatHab nun die anderen auch aktiviert. Jetzt:
config: MS=1;MU=1;MC=1
jetzt sollten die renkforce Temperatursensoren wieder erkannt werden.
Gruß Ralf
Zitat von: Ralf9 am 27 Juni 2019, 22:48:29
jetzt sollten die renkforce Temperatursensoren wieder erkannt werden.
Gruß Ralf
Ja, sie sind wieder da :-)
So, dann ist der Sduino soweit wieder am laufen.
Der CUL funktioniert aktuell (nach einem Stromlos vom Pi) auch wieder. Werde es weiter beobachten.