Hallo,
ich wollte ein neues HM-CC-RT-Anlernen, hab dafür mein HMUSB über ein "set hmusb hmPairForSec 600" in den anlern Modus gebracht und dann am THermostat für 3 Sekunden die Boost Taste gedrückt, es wird aber kein neues Device hinzugefügt.
Im Eventmonitor steht dann nur
2022-03-05 16:44:24.661 Global global UNDEFINED HM_64B1E1 CUL_HM 64B1E1
2022-03-05 16:44:24.711 HMLAN hmusb UNKNOWNCODE A1A01840064B1E10000001400954F4551323039333132385900FFFF::-43:hmusb
und im LOg
2022.03.05 16:44:10.001 1: HMLAN_Parse: hmusb new condition init
2022.03.05 16:44:10.046 1: 127.0.0.1:1201 reappeared (hmusb)
2022.03.05 16:44:12.692 1: HMLAN_Parse: hmusb new condition ok
2022.03.05 16:44:24.673 3: Please define HM_64B1E1 first
2022.03.05 16:44:24.675 1: PERL WARNING: Use of uninitialized value $d in hash element at fhem.pl line 4683.
2022.03.05 16:44:24.676 1: stacktrace:
2022.03.05 16:44:24.676 1: main::__ANON__ called by fhem.pl (4683)
2022.03.05 16:44:24.676 1: main::AttrVal called by ./FHEM/10_CUL_HM.pm (1899)
2022.03.05 16:44:24.677 1: main::CUL_HM_Parse called by fhem.pl (4093)
2022.03.05 16:44:24.677 1: main::Dispatch called by ./FHEM/00_HMLAN.pm (787)
2022.03.05 16:44:24.677 1: main::HMLAN_Parse called by ./FHEM/00_HMLAN.pm (611)
2022.03.05 16:44:24.678 1: main::HMLAN_Read called by fhem.pl (3892)
2022.03.05 16:44:24.678 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2022.03.05 16:44:24.679 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2022.03.05 16:44:24.679 1: main::__ANON__ called by fhem.pl (775)
2022.03.05 16:44:24.680 1: PERL WARNING: Use of uninitialized value $mh{"devN"} in hash element at ./FHEM/10_CUL_HM.pm line 2102.
2022.03.05 16:44:24.680 1: stacktrace:
2022.03.05 16:44:24.681 1: main::__ANON__ called by ./FHEM/10_CUL_HM.pm (2102)
2022.03.05 16:44:24.681 1: main::CUL_HM_Parse called by fhem.pl (4093)
2022.03.05 16:44:24.681 1: main::Dispatch called by ./FHEM/00_HMLAN.pm (787)
2022.03.05 16:44:24.682 1: main::HMLAN_Parse called by ./FHEM/00_HMLAN.pm (611)
2022.03.05 16:44:24.682 1: main::HMLAN_Read called by fhem.pl (3892)
2022.03.05 16:44:24.682 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2022.03.05 16:44:24.683 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2022.03.05 16:44:24.683 1: main::__ANON__ called by fhem.pl (775)
2022.03.05 16:44:24.683 1: PERL WARNING: Use of uninitialized value $d in hash element at fhem.pl line 4683.
2022.03.05 16:44:24.684 1: stacktrace:
2022.03.05 16:44:24.684 1: main::__ANON__ called by fhem.pl (4683)
2022.03.05 16:44:24.685 1: main::AttrVal called by ./FHEM/10_CUL_HM.pm (2102)
2022.03.05 16:44:24.685 1: main::CUL_HM_Parse called by fhem.pl (4093)
2022.03.05 16:44:24.685 1: main::Dispatch called by ./FHEM/00_HMLAN.pm (787)
2022.03.05 16:44:24.686 1: main::HMLAN_Parse called by ./FHEM/00_HMLAN.pm (611)
2022.03.05 16:44:24.686 1: main::HMLAN_Read called by fhem.pl (3892)
2022.03.05 16:44:24.686 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2022.03.05 16:44:24.687 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2022.03.05 16:44:24.687 1: main::__ANON__ called by fhem.pl (775)
2022.03.05 16:44:24.688 1: PERL WARNING: Use of uninitialized value $mh{"devN"} in hash element at ./FHEM/10_CUL_HM.pm line 2103.
2022.03.05 16:44:24.688 1: stacktrace:
2022.03.05 16:44:24.688 1: main::__ANON__ called by ./FHEM/10_CUL_HM.pm (2103)
2022.03.05 16:44:24.689 1: main::CUL_HM_Parse called by fhem.pl (4093)
2022.03.05 16:44:24.689 1: main::Dispatch called by ./FHEM/00_HMLAN.pm (787)
2022.03.05 16:44:24.690 1: main::HMLAN_Parse called by ./FHEM/00_HMLAN.pm (611)
2022.03.05 16:44:24.690 1: main::HMLAN_Read called by fhem.pl (3892)
2022.03.05 16:44:24.690 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2022.03.05 16:44:24.691 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2022.03.05 16:44:24.691 1: main::__ANON__ called by fhem.pl (775)
2022.03.05 16:44:24.692 1: PERL WARNING: Use of uninitialized value $d in hash element at fhem.pl line 4683.
2022.03.05 16:44:24.692 1: stacktrace:
2022.03.05 16:44:24.692 1: main::__ANON__ called by fhem.pl (4683)
2022.03.05 16:44:24.693 1: main::AttrVal called by ./FHEM/10_CUL_HM.pm (2103)
2022.03.05 16:44:24.693 1: main::CUL_HM_Parse called by fhem.pl (4093)
2022.03.05 16:44:24.693 1: main::Dispatch called by ./FHEM/00_HMLAN.pm (787)
2022.03.05 16:44:24.694 1: main::HMLAN_Parse called by ./FHEM/00_HMLAN.pm (611)
2022.03.05 16:44:24.694 1: main::HMLAN_Read called by fhem.pl (3892)
2022.03.05 16:44:24.694 1: main::CallFn called by ./FHEM/98_freezemon.pm (1235)
2022.03.05 16:44:24.695 1: main::freezemon_callFn called by ./FHEM/98_freezemon.pm (1348)
2022.03.05 16:44:24.695 1: main::__ANON__ called by fhem.pl (775)
2022.03.05 16:44:24.712 3: hmusb: Unknown code A1A01840064B1E10000001400954F4551323039333132385900FFFF::-43:hmusb, help me!
2022.03.05 16:46:02.172 1: Error: >< has no TYPE, but following keys: >helper<
2022.03.05 16:46:02.177 1: Error: >HM_64B1E1< has no TYPE, but following keys: >IODev<
Was läuft da falsch?
Danke
Nach dem ich nun das Device komplett zurückgesetzt hab und dann nochmal versucht hab, wurde es nun eingebunden, allerdings steht es schon seit gestern auf pending...
Internals:
CFGFN
DEF 64B1E1
FUUID 6224812e-f33f-1e4d-3a51-38c644091a1da863
IODev hmusb
LASTInputDev hmusb
MSGCNT 1
NAME HeizungFenster
NR 473
NTFY_ORDER 48-HM_64B1E1
STATE CMDs_pending
TYPE CUL_HM
channel_01 HM_64B1E1_Weather
channel_02 HM_64B1E1_Climate
channel_03 HM_64B1E1_WindowRec
channel_04 HM_64B1E1_Clima
channel_05 HM_64B1E1_ClimaTeam
channel_06 HM_64B1E1_remote
disableNotifyFn 1
hmusb_MSGCNT 1
hmusb_RAWMSG E64B1E1,0000,080A2F3F,FF,FFD3,01840064B1E10000001400954F4551323039333132385900FFFF
hmusb_RSSI -45
hmusb_TIME 2022-03-07 06:12:15
lastMsg No:01 - t:00 s:64B1E1 d:000000 1400954F4551323039333132385900FFFF
protCmdPend 45 CMDs_pending
protCondBurst off
protLastRcv 2022-03-07 06:12:15
protRcv 2 last_at:2022-03-07 06:12:15
protSnd 4 last_at:2022-03-07 19:32:00
protSndB 4 last_at:2022-03-07 19:32:00
protState CMDs_pending
rssi_at_hmusb cnt:2 min:-45 max:-43 avg:-44 lst:-45
Helper:
DBLOG:
D-firmware:
myDbLog:
TIME 1646559579.41035
VALUE 1.4
D-serialNr:
myDbLog:
TIME 1646559579.41035
VALUE OEQ2093128
cfgState:
myDbLog:
TIME 1646677701.6399
VALUE updating
commState:
myDbLog:
TIME 1646677924.20492
VALUE CMDs_pending
state:
myDbLog:
TIME 1646677924.23159
VALUE CMDs_pending
READINGS:
2022-03-06 10:39:39 D-firmware 1.4
2022-03-06 10:39:39 D-serialNr OEQ2093128
2022-03-07 19:32:00 IODev hmusb
2022-03-06 10:39:39 R-pairCentral set_0x000041
2022-03-07 19:28:21 cfgState updating
2022-03-07 19:32:04 commState CMDs_pending
2022-03-07 19:32:04 state CMDs_pending
cmdStack:
++A00100004164B1E100050000000000
++A00100004164B1E1000802010A000B000C41
++A00100004164B1E10006
++A00100004164B1E100040000000000
##A00100004164B1E10103
##A00100004164B1E101040000000001
##A00100004164B1E10203
##A00100004164B1E102040000000001
##A00100004164B1E10303
##A00100004164B1E103040000000001
##A00100004164B1E10403
##A00100004164B1E104040000000001
##A00100004164B1E100040000000007
##A00100004164B1E10503
##A00100004164B1E105040000000001
##A00100004164B1E10603
##A00100004164B1E106040000000001
++A00100004164B1E100040000000000
##A00100004164B1E10103
##A00100004164B1E101040000000001
##A00100004164B1E10203
##A00100004164B1E102040000000001
##A00100004164B1E10303
##A00100004164B1E103040000000001
##A00100004164B1E10403
##A00100004164B1E104040000000001
##A00100004164B1E100040000000007
##A00100004164B1E10503
##A00100004164B1E105040000000001
##A00100004164B1E10603
##A00100004164B1E106040000000001
++A00100004164B1E100040000000000
##A00100004164B1E10103
##A00100004164B1E101040000000001
##A00100004164B1E10203
##A00100004164B1E102040000000001
##A00100004164B1E10303
##A00100004164B1E103040000000001
##A00100004164B1E10403
##A00100004164B1E104040000000001
##A00100004164B1E100040000000007
##A00100004164B1E10503
##A00100004164B1E105040000000001
##A00100004164B1E10603
##A00100004164B1E106040000000001
helper:
HM_CMDNR 4
PONtest 1
cfgStateUpdt 1
lastMsgTm 1646629935.12141
mId 0095
peerFriend -
peerOpt -:thermostat
regLst 0
rxType 140
supp_Pair_Rep 0
cmds:
TmplKey :no:1646677540.2488
TmplTs 1646677540.2488
cmdKey 0:1:0::HeizungFenster:0095:00:
cmdLst:
assignHmKey noArg
burstXmit noArg
clear [({msgErrors}|msgEvents|rssi|attack|trigger|register|oldRegs|readings|all)]
deviceRename -newName-
fwUpdate -filename- [-bootTime-]
getConfig noArg
getDevInfo noArg
getRegRaw (List0|List1|List2|List3|List4|List5|List6|List7) [-peerChn-]
inhibit [(on|{off})]
raw -data- [...]
regBulk -list-.-peerChn- -addr1:data1- [-addr2:data2-]...
regSet [(prep|{exec})] -regName- -value- [-peerChn-]
reset noArg
sysTime noArg
tplDel -tplDel-
tplSet_0 -tplChan-
unpair noArg
lst:
condition slider,0,1,255
peer
peerOpt
tplChan
tplDel
tplPeer
rtrvLst:
cmdList [({short}|long)]
deviceInfo [({short}|long)]
list [({normal}|full)]
param -param-
reg -addr- -list- [-peerChn-]
regList noArg
regTable noArg
regVal -addr- -list- [-peerChn-]
saveConfig [-filename-]
tplInfo noArg
expert:
def 1
det 0
raw 1
tpl 0
io:
flgs 2
newChn +64B1E1,02,00,00
nextSend 1646629935.2207
rxt 2
vccu vccu
p:
64B1E1
00
00
00
prefIO:
mRssi:
mNo 01
io:
hmusb:
-37
-37
peerIDsH:
prt:
awake 0
bErr 0
brstWu 0
sProc 2
q:
qReqConf
qReqStat
role:
dev 1
rssi:
at_hmusb:
avg -44
cnt 2
lst -45
max -43
min -45
shRegW:
07 04
shadowReg:
RegL_00. 02:01 0A:00 0B:00 0C:41
tmpl:
Attributes:
IOgrp vccu:hmusb
alias Wohnzimmer Heizung Fenster
autoReadReg 4_reqStatus
burstAccess 1_auto
expert defReg,rawReg
firmware 1.4
group Heizung
model HM-CC-RT-DN
room Wohnzimmer
serialNr OEQ2093128
subType thermostat
webCmd getConfig:clear msgEvents:burstXmit
Mach mal den Abstand größer, und welche cul_hm-version ist das?
Was meinst du mit Abstand größer?
Internals:
Clients :CUL_HM:
DEF 127.0.0.1:1201
DeviceName 127.0.0.1:1201
FD 4
FUUID 5c48d21f-f33f-f412-3c37-bc59854f028df6af
IFmodel USB
NAME hmusb
NR 40
NTFY_ORDER 47-hmusb
PARTIAL
RAWMSG E308BD3,0000,0B213D86,FF,FFC7,5B8610308BD30000000A98C60C0700
RSSI -57
STATE opened
TYPE HMLAN
XmitOpen 1
assignedIDsCnt 19
hmusb_MSGCNT 64
hmusb_TIME 2022-03-07 20:36:17
msgKeepAlive dlyMax:0.716 bufferMin:4
msgLoadCurrent 37
msgLoadHistoryAbs 5min steps: 37/37/43/43/39/0/0/0/0/0/0/0
nextOpenDelay 10
owner 000041
owner_CCU vccu
uptime 002 51:53:00.272
Helper:
DBLOG:
Xmit-Events:
myDbLog:
TIME 1646680716.80437
VALUE disconnected:1 ok:1 init:1
cond:
myDbLog:
TIME 1646680716.80437
VALUE ok
loadLvl:
myDbLog:
TIME 1646681054.52381
VALUE low
state:
myDbLog:
TIME 1646681629.96444
VALUE UNKNOWNCODE A1A01840064B1E10000001400954F4551323039333132385900FFFF::-47:hmusb
READINGS:
2022-03-07 20:18:36 D-HMIdAssigned 000041
2022-03-07 20:18:36 D-HMIdOriginal 37301D
2022-03-07 20:18:36 D-firmware 0.967
2022-03-07 20:18:36 D-serialNr MEQ0232057
2022-03-07 20:18:36 Xmit-Events disconnected:1 ok:1 init:1
2022-03-07 20:18:36 cond ok
2022-03-07 20:37:10 loadLvl low
2020-01-12 20:35:06 prot_ERROR-Overload last
2020-01-12 20:40:04 prot_Warning-HighLoad last
2022-03-07 20:18:08 prot_disconnected last
2022-03-07 20:18:24 prot_init last
2020-01-04 20:21:01 prot_keepAlive last
2022-03-07 20:18:36 prot_ok last
2022-03-07 20:18:24 state opened
helper:
assIdCnt 19
assIdRep 19
info 03C7,MEQ0232057,37301D,000041
setTime 50252
cnd:
0 1
253 1
255 1
ids:
1F1596:
cfg +1F1596,00,00,00
name Fenster_neben_Couch
1F15F2:
cfg +1F15F2,00,00,00
name Fenster_ueber_Heizung
1F15FF:
cfg +1F15FF,00,00,00
name Terassen_Tuer
222529:
cfg +222529,00,00,00
name Heizung_Tuer
2236F8:
cfg +2236F8,00,00,00
name Kueche
2237AA:
cfg +2237AA,00,00,00
name Heizung_Flur
22FC89:
cfg +22FC89,00,00,00
chn 01
flg 0
msg
name Kinderzimmer_Mila
to 1646680722.41288
23021F:
cfg +23021F,00,00,00
chn 01
flg 0
msg
name Keller
to 1646680721.34411
230224:
cfg +230224,00,00,00
chn 01
flg 0
msg
name Flur_EG
to 1646680719.12547
237437:
cfg +237437,00,00,00
chn 01
flg 0
msg
name Funkschalter_Keller_Licht
to 1646680720.2134
287160:
cfg +287160,00,00,00
name Bewegungsmelder
308BD3:
cfg +308BD3,00,00,00
name Heizung_Kinderzimmer
3A4BC6:
cfg +3A4BC6,00,00,00
name Kinderzimmer_Laya
3BC6EE:
cfg +3BC6EE,00,00,00
chn 01
flg 0
msg
name Rauchmelder_Kinderzimmer_Laya
to 1646680723.58178
589C90:
cfg +589C90,02,00,00
name Mila_Fenster
589CE2:
cfg +589CE2,00,00,00
name Gaeste_WC_Fenster
58AFA5:
cfg +58AFA5,00,00,00
name Fenster_Laya
64B1E1:
cfg +64B1E1,02,00,00
flg 0
msg
name HM_64B1E1
to 1646681553.08991
71374E:
cfg +71374E,00,00,00
name Gaeste_WC
k:
BufMin 4
DlyMax 0.716
Next 1646681855.21255
Start 1646681830.21255
loadLvl:
bl 40
a:
99
90
40
0
h:
0 low
40 batchLevel
90 high
99 suspended
log:
all 0
sys 0
ids:
ARRAY(0x29e5620)
q:
HMcndN 0
answerPend 0
hmLanQlen 1
keepAliveRec 1
keepAliveRpt 0
loadLastMax 37
loadNo 7
scnt 7
sending 0
ald:
37
37
43
43
39
0
0
0
0
0
0
0
apIDs:
ref:
hmtL 186780272
kTs 0
Attributes:
event-on-change-reading .*
group Hardeware
hmId 000041
hmLanQlen 1_min
loadLevel 0:low,40:batchLevel,90:high,99:suspended
room Wohnzimmer
Der rssi-Wert ist uU. zu groß => Mehr Abstand zw. dem Stick und dem RT-DN.
version CUL_HM?
bei conditional burst devices gibt es aktuell diverse probleme.
eventuell hilft löschen vom attribut burstAccess
und pending cmds immer manuell abarbeiten.
edit:
datei entfernt
wenn dein fhem up-to-date ist, kannst du meine aktuelle 10-cul_hm version aus dem anhang probieren.
mit gesetztem attr autoreadreg=5_missing werden wahrscheinlich keine pending blockaden mehr auftauchen und alles wird früher oder später abgearbeitet werden.
attr burstaccess kannst du auch wieder setzen.
Hallo,
ich hab das Thermostat mittlerweile am laufen, hab es noch zweimal komplett auf Werkseinstellungen gesetzt und in Fhem wieder entfernt, und dann mit der VCCU gepeert und nun wird alles sauber abgearbeitet, so wie es aussieht, auch mit der Version die übers Fhem Update verteilt wird.
Internals:
DEF 64B1E1
FUUID 62265e1a-f33f-1e4d-c3ed-7e1cc65de12c8a50
IODev hmusb
LASTInputDev hmusb
MSGCNT 290
NAME HeizungFenster
NR 384
NTFY_ORDER 48-HeizungFenster
STATE CMDs_done
TYPE CUL_HM
channel_01 HM_64B1E1_Weather
channel_02 HM_64B1E1_Climate
channel_03 HM_64B1E1_WindowRec
channel_04 HM_64B1E1_Clima
channel_05 HM_64B1E1_ClimaTeam
channel_06 HM_64B1E1_remote
disableNotifyFn 1
hmusb_MSGCNT 290
hmusb_RAWMSG R6CF059AE,0001,122FAC25,FF,FFC6,25800264B1E1000041010429003700
hmusb_RSSI -58
hmusb_TIME 2022-03-09 05:29:25
lastMsg No:25 - t:02 s:64B1E1 d:000041 010429003700
protCmdDel 3
protCondBurst on
protLastRcv 2022-03-09 05:29:25
protRcv 287 last_at:2022-03-09 05:29:25
protResnd 3 last_at:2022-03-08 20:08:22
protResndFail 1 last_at:2022-03-08 20:08:26
protSnd 30 last_at:2022-03-09 05:29:25
protSndB 11 last_at:2022-03-09 05:29:24
protState CMDs_done
rssi_at_hmusb cnt:290 min:-62 max:-47 avg:-57.13 lst:-58
rssi_hmusb cnt:4 min:-55 max:-53 avg:-54 lst:-55
Helper:
DBLOG:
actuator:
myDbLog:
TIME 1646800125.5024
VALUE 0
battery:
myDbLog:
TIME 1646800165.25893
VALUE ok
batteryLevel:
myDbLog:
TIME 1646800125.5024
VALUE 3.1
cfgState:
myDbLog:
TIME 1646766857.01183
VALUE RegMiss
commState:
myDbLog:
TIME 1646800165.25893
VALUE CMDs_done
desired-temp:
myDbLog:
TIME 1646800165.25893
VALUE 20.5
measured-temp:
myDbLog:
TIME 1646800125.5024
VALUE 18.0
motorErr:
myDbLog:
TIME 1646800125.5024
VALUE ok
state:
myDbLog:
TIME 1646800165.25893
VALUE CMDs_done
time-request:
myDbLog:
TIME 1646763965.43207
VALUE -
READINGS:
2022-03-09 05:29:24 CommandAccepted yes
2022-03-07 20:40:30 D-firmware 1.4
2022-03-07 20:40:30 D-serialNr OEQ2093128
2022-03-09 05:29:24 IODev hmusb
2022-03-07 20:40:23 PairedTo invalid: not supported by FW version
2022-03-07 20:40:15 R-backOnTime 10 s
2022-03-07 20:40:15 R-burstRx on
2022-03-07 20:40:15 R-cyclicInfoMsg on
2022-03-07 20:40:15 R-cyclicInfoMsgDis 0
2022-03-07 20:40:15 R-pairCentral 0x000041
2022-03-09 05:28:45 actuator 0
2022-03-09 05:29:25 battery ok
2022-03-09 05:28:45 batteryLevel 3.1
2022-03-08 20:14:17 cfgState RegMiss
2022-03-09 05:29:25 commState CMDs_done
2022-03-09 05:29:25 desired-temp 20.5
2022-03-09 05:28:45 measured-temp 18.0
2022-03-09 05:28:45 motorErr ok
2022-03-09 05:29:25 state CMDs_done
2022-03-08 19:26:05 time-request -
helper:
HM_CMDNR 37
PONtest 1
cSnd 1100004164B1E1860429,1100004164B1E1860429
cfgStateUpdt 0
lastMsgTm 1646800165.22522
mId 0095
peerFriend -
peerOpt -:thermostat
regLst 0
rxType 140
supp_Pair_Rep 0
cfgChk:
idRc01 RegL_00.
cmds:
TmplKey :no:1646764776.449
TmplTs 1646764776.449
cmdKey 0:1:0::HeizungFenster:0095:00:
cmdLst:
assignHmKey noArg
burstXmit noArg
clear [({msgErrors}|msgEvents|rssi|attack|trigger|register|oldRegs|readings|all)]
deviceRename -newName-
fwUpdate -filename- [-bootTime-]
getConfig noArg
getDevInfo noArg
getRegRaw (List0|List1|List2|List3|List4|List5|List6|List7) [-peerChn-]
inhibit [(on|{off})]
raw -data- [...]
regBulk -list-.-peerChn- -addr1:data1- [-addr2:data2-]...
regSet [(prep|{exec})] -regName- -value- [-peerChn-]
reset noArg
sysTime noArg
tplDel -tplDel-
tplSet_0 -tplChan-
unpair noArg
lst:
condition slider,0,1,255
peer
peerOpt
tplChan
tplDel
tplPeer
rtrvLst:
cmdList [({short}|long)]
deviceInfo [({short}|long)]
list [({normal}|full)]
param -param-
reg -addr- -list- [-peerChn-]
regList noArg
regTable noArg
regVal -addr- -list- [-peerChn-]
saveConfig [-filename-]
tplInfo noArg
expert:
def 1
det 0
raw 1
tpl 0
io:
flgs 0
newChn +64B1E1,00,00,00
nextSend 1646800165.32465
rxt 2
vccu vccu
p:
64B1E1
00
00
00
prefIO:
hmusb
mRssi:
mNo 25
io:
hmusb:
-52
-52
peerIDsH:
prt:
awake 0
bErr 0
sProc 0
tryMsg:
q:
qReqConf
qReqStat
role:
dev 1
prs 1
rssi:
at_hmusb:
avg -57.1379310344828
cnt 290
lst -58
max -47
min -62
hmusb:
avg -54
cnt 4
lst -55
max -53
min -55
shRegW:
07 04
tmpl:
Attributes:
IOgrp vccu:hmusb
alexaName Heizung Fenster
alias Heizung Fenster
autoReadReg 4_reqStatus
burstAccess 1_auto
expert defReg,rawReg
firmware 1.4
group Heizung
model HM-CC-RT-DN
room Wohnzimmer
serialNr OEQ2093128
subType thermostat
webCmd getConfig:clear msgEvents:burstXmit
Danke für die Hilfe
Zitatich hab das Thermostat mittlerweile am laufen, hab es noch zweimal komplett auf Werkseinstellungen gesetzt und in Fhem wieder entfernt, und dann mit der VCCU gepeert und nun wird alles sauber abgearbeitet
völlig überflüssig.
mit burstaccess=1_auto wird immer versucht eine "neue" kommunikation über burst zu starten.
gelingt es (internal protCondBurst=on) und die kommunikation bricht nicht ab, gibt es keine probleme.
wenn aber burst nicht funktioniert hat, protCondBurst=off, soll mit wakeup fortgesetzt werden. dieser automatische modus wechsel führt ggf zu einer pending blockade.