Ich habe eine Änderung bei den diversen Geräten vorgenommen, wo das Attribut IOgrp nur mehr den Eintrag VCCU hat.
Seit dieser Umstellung hat es den Anschein, dass die VCCU nur das erste HM-MOD-UART Module verwendet, wodurch es dann zu einem ERROR-Overload kommt.
Insgesamt sind in meinem großflächigen Objekt 6 Stk. HM-MOD-UART Module verbaut.
list VCCU
Internals:
CFGFN /media/hdd/fhem/mycfg/HM/hm_rasp01.cfg
DEF F12347
FUUID 5c45b04c-f33f-f4d2-4334-8937b207a433d26e
HmUART_AB_GTO_MSGCNT 5602
HmUART_AB_GTO_RAWMSG 05000140698002F123475D019400
HmUART_AB_GTO_RSSI -64
HmUART_AB_GTO_TIME 2022-07-08 15:43:25
HmUART_EG_MSGCNT 7141
HmUART_EG_RAWMSG 0500005D188002F123474C23A300
HmUART_EG_RSSI -93
HmUART_EG_TIME 2022-07-08 15:44:39
HmUART_OG1_MSGCNT 6742
HmUART_OG1_RAWMSG 0500004D188002F123474C23A300
HmUART_OG1_RSSI -77
HmUART_OG1_TIME 2022-07-08 15:44:39
HmUART_OG2_MSGCNT 5286
HmUART_OG2_RAWMSG 05000136188002F123474C23A300
HmUART_OG2_RSSI -54
HmUART_OG2_TIME 2022-07-08 15:44:39
HmUART_Test_MSGCNT 6475
HmUART_Test_RAWMSG 0500013E188002F123474C23A300
HmUART_Test_RSSI -62
HmUART_Test_TIME 2022-07-08 15:44:39
IODev HmUART_AB_FR
LASTInputDev HmUART_Test
MSGCNT 31246
NAME VCCU
NOTIFYDEV global
NR 1544
NTFY_ORDER 48-VCCU
STATE HmUART_AB_FR:Warning-HighLoad,HmUART_AB_GTO:ok,HmUART_EG:ok,HmUART_OG1:ok,HmUART_OG2:ok,HmUART_Test:ok
TYPE CUL_HM
assignedIOs HmUART_AB_FR,HmUART_AB_GTO,HmUART_EG,HmUART_OG1,HmUART_OG2,HmUART_Test
channel_01 VCCU_Btn1
eventCount 964
lastMsg No:18 - t:02 s:F12347 d:4C23A3 00
protLastRcv 2022-07-08 15:44:39
protRcv 8694 last_at:2022-07-08 15:44:39
protRcvB 962 last_at:2022-07-08 15:40:58
rssi_at_HmUART_AB_GTO cnt:5602 min:-82 max:-55 avg:-64.81 lst:-64
rssi_at_HmUART_EG cnt:7141 min:-97 max:-71 avg:-85.85 lst:-93
rssi_at_HmUART_OG1 cnt:6742 min:-97 max:-54 avg:-65.43 lst:-77
rssi_at_HmUART_OG2 cnt:5286 min:-65 max:-52 avg:-56.77 lst:-54
rssi_at_HmUART_Test cnt:6475 min:-91 max:-52 avg:-62.9 lst:-62
READINGS:
2022-07-08 15:44:39 CommandAccepted yes
2022-07-05 08:13:50 IODev HmUART_AB_FR
2022-07-08 15:45:24 IOopen 6
2022-07-07 20:00:25 aesReqTo EG_STH_ZS_T1VGF
2022-07-04 12:22:05 cfgState ok
2022-05-22 10:21:31 hmPair name:AB_MB_PS SN:OEQ0611889 model:HM-SEN-WA-OD
2022-07-08 15:45:24 state HmUART_AB_FR:Warning-HighLoad,HmUART_AB_GTO:ok,HmUART_EG:ok,HmUART_OG1:ok,HmUART_OG2:ok,HmUART_Test:ok
2022-06-23 19:59:36 unknown_5A3043 received
2022-06-26 02:19:15 unknown_69DEE5 received
2022-04-11 19:51:33 unknown_6B23B9 received
2022-06-19 21:37:22 unknown_6B23DF received
2022-04-22 02:56:40 unknown_6B5B87 received
2022-04-12 18:06:20 unknown_E13347 received
2022-04-26 16:12:44 unknown_F12357 received
helper:
HM_CMDNR 24
PONtest 1
lastMsgTm 1657287879.0748
mId FFF0
peerFriend -
peerOpt -:virtual
regLst
rxType 1
supp_Pair_Rep 0
ack:
cmds:
TmplKey :no:1657001635.54129
TmplTs 1657001635.54129
cmdKey 0:1:1::VCCU:FFF0:01:
cmdLst:
assignIO -IO- [({set}|unset)]
clear [(readings|rssi|msgEvents|attack|{msgErrors}|unknownDev)]
defIgnUnknown noArg
hmPairForSec [-sec-]
hmPairSerial -serial-
tplSet_0 -tplChan-
update noArg
virtual [(1..50;1|{1})]
lst:
condition slider,0,1,255
peer
peerOpt
tplChan
tplDel
tplPeer
rtrvLst:
cmdList [({short}|long)]
deviceInfo [({short}|long)]
list [({normal}|full)]
listDevice noArg
param -param-
expert:
def 1
det 0
raw 0
tpl 0
io:
nextSend 1657287879.15302
vccu VCCU
ioList:
HmUART_AB_FR
HmUART_AB_GTO
HmUART_EG
HmUART_OG1
HmUART_OG2
HmUART_Test
prefIO:
mRssi:
mNo 18
io:
HmUART_AB_GTO:
-64
HmUART_EG:
-93
-93
HmUART_OG1:
-77
-77
HmUART_OG2:
-54
-54
HmUART_Test:
-62
-62
peerIDsH:
prt:
bErr 0
sProc 0
rspWait:
q:
qReqConf
qReqStat
role:
dev 1
vrt 1
rssi:
at_HmUART_AB_GTO:
avg -64.8102463405926
cnt 5602
lst -64
max -55
min -82
at_HmUART_EG:
avg -85.851421369556
cnt 7141
lst -93
max -71
min -97
at_HmUART_OG1:
avg -65.438148917235
cnt 6742
lst -77
max -54
min -97
at_HmUART_OG2:
avg -56.7765796443436
cnt 5286
lst -54
max -52
min -65
at_HmUART_Test:
avg -62.9020849420849
cnt 6475
lst -62
max -52
min -91
shadowReg:
tmpl:
Attributes:
IOList HmUART_AB_FR,HmUART_AB_GTO,HmUART_EG,HmUART_OG1,HmUART_OG2,HmUART_Test
IOgrp VCCU
aesCommReq 0
alias HomeMatic Virtuelle CCU
commStInCh off
event-on-change-reading .*
group .HomeMatic VCCU
hmKey 01:e1fa95c5613ea3c257a6862a2fdc6bf9
hmKey2 02:eb6e444f34df0e509c3a82a0a079772c
hmKey3 03:ee955645ccc18dc0ebb5a137bf7c9e70
icon hm_ccu
model CCU-FHEM
room _HM,_Kontaktsensoren,_RxTx
subType virtual
verbose 0
webCmd virtual:update
Eigentlich sollten je nach RSSI Stärke die Auswahl des HM-MOD-UART Modules erfolgen. Das dürfte aber nicht funktionieren.
Damit das HM-MOD-UART Module wieder funktioniert, muss manuell ein restart oder ein reopen erfolgen.
Ist das Absicht, dass die RSSI Modulauswahl nicht mehr funktioniert?
Welche Version(en) (CUL_HM, HMinfo und IO-Module) sind im Einsatz?
Ggf. mal einen Blick auf https://forum.fhem.de/index.php/topic,120857.msg1208516.html#msg1208516 werfen.
Zeig mal ein
list DEF=...... IODev IOgrp
Die IO-Module sind alle am gleichen Stand.
list HmUART_OG2
Internals:
AssignedPeerCnt 36
CFGFN /media/hdd/fhem/mycfg/schnittstellen_rasp01.cfg
CNT 23
Clients :CUL_HM:
DEF /dev/ttyAMA0
DEVCNT 23
DevState 99
DevType UART
DeviceName /dev/ttyAMA0@115200
FD 278
FUUID 5c45b01a-f33f-f4d2-8d3f-2afd62f7e9d7ecdc
LastOpen 1657001580.34803
NAME HmUART_OG2
NOTIFYDEV global
NR 490
NTFY_ORDER 47-HmUART_OG2
PARTIAL
RAWMSG 040201
RSSI -53
STATE opened
TYPE HMUARTLGW
XmitOpen 1
eventCount 7
model HM-MOD-UART
msgLoadCurrent 1
msgLoadHistory 0/0/0/0/0/0/0/0/0/0/0/0
msgLoadHistoryAbs 1/1/1/1/1/1/1/1/1/1/1/1/1
owner F12347
owner_CCU VCCU
Helper:
CreditTimer 17361
FW 66561
Initialized 1
SendCnt 510
AckPending:
LastSendLen:
3
3
Log:
IDs:
PendingCMD:
RoundTrip:
Delay 0.0108969211578369
loadLvl:
lastHistory 1657302041.23364
MatchList:
1:CUL_HM ^A......................
Peers:
4C0DD5 +4C0DD5,00,03,00
4C1DAB +4C1DAB,00,03,00
4C1E47 +4C1E47,00,03,00
4C1E60 +4C1E60,00,03,00
4C1E72 +4C1E72,00,03,00
4C218B +4C218B,00,03,00
4C21C5 +4C21C5,00,03,00
4C21D1 +4C21D1,00,03,00
4C242E +4C242E,02,03,00
4C2456 +4C2456,00,03,00
4DEBC0 +4DEBC0,00,03,00
4EA895 +4EA895,00,03,00
544F7C +544F7C,00,03,00
544FEE +544FEE,00,03,00
545002 +545002,00,03,00
5555EE +5555EE,00,03,00
56799E +56799E,00,03,00
5A30CA +5A30CA,00,03,00
5A7966 +5A7966,00,03,00
5C1ED3 +5C1ED3,00,03,00
5C20E5 +5C20E5,00,03,00
5E59A8 +5E59A8,00,03,00
5FFAA0 +5FFAA0,00,03,00
5FFC66 +5FFC66,00,03,00
6387ED +6387ED,00,03,00
6437FC +6437FC,00,03,00
6437FD +6437FD,00,03,00
64381E +64381E,00,03,00
6631A1 +6631A1,00,03,00
673948 +673948,00,03,00
6752BF +6752BF,00,03,00
67534F +67534F,00,03,00
67B292 +67B292,00,03,00
6A53C7 +6A53C7,00,03,00
6B3FD3 +6B3FD3,02,03,00
772D79 +772D79,00,03,00
READINGS:
2022-07-05 08:55:29 D-HMIdAssigned F12347
2022-07-05 09:00:38 D-HMIdOriginal 4C3DB2
2022-07-05 09:00:40 D-firmware 1.4.1
2022-07-05 09:00:40 D-serialNr NEQ0605280
2022-07-05 08:11:26 D-type HM-MOD-UART
2022-07-05 09:00:41 cond ok
2022-07-08 14:52:40 load 1
2022-07-05 09:00:41 loadLvl low
2022-07-05 08:13:00 state opened
helper:
Attributes:
alias HomeMatic Gateway - OG2 EDV Raum
devStateIcon init:hm_lan@orange opened:hm_lan@0CFB0C closed:it_network@red
dutyCycle 1
group Schnittstellen HomeMatic
hmId F12347
icon hm_lan
qLen 60
room Brandmeldeanlage,_HM,_RxTx
verbose 0
Version HMinfo
File Rev Last Change
98_HMinfo.pm 25978 2022-04-18 14:50:17Z martinp876
doif.js 24438 2021-05-14 18:08:18Z Ellert
fhemweb.js 25983 2022-04-19 17:26:44Z rudolfkoenig
fhemweb_readingsGroup.js 15189 2017-10-03 17:53:27Z justme1968
Version CUL_HM
File Rev Last Change
10_CUL_HM.pm 25977 2022-04-18 14:48:41Z martinp876
doif.js 24438 2021-05-14 18:08:18Z Ellert
fhemweb.js 25983 2022-04-19 17:26:44Z rudolfkoenig
fhemweb_readingsGroup.js 15189 2017-10-03 17:53:27Z justme1968
list DEF=...... IODev IOgrp
AB_BKTR_BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
AB_FR_AAM IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_FR
AB_FR_AD IODev HmUART_AB_FR
IOgrp VCCU
AB_FR_BL_RGB IODev HmUART_AB_GTO
IOgrp VCCU
AB_FR_RM IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR
AB_GAO_SSPPWT_FSI IODev HmUART_AB_FR
IOgrp VCCU
AB_GO_RM IODev HmUART_AB_FR
IOgrp VCCU
AB_GO_RM_TEAMDEV IODev HmUART_AB_FR
IOgrp VCCU
AB_MB_PS IODev HmUART_OG2
IOgrp VCCU
AB_SA_NT IODev HmUART_AB_FR
IOgrp VCCU
AB_SG_12BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
AB_SG_34BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
AB_SG_56BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
AB_SG_BLGOBWS IODev HmUART_Test
IOgrp VCCU
AB_SG_BLWSBWS IODev HmUART_AB_FR
IOgrp VCCU
AB_VG_BW IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
AB_WST_RS IODev HmUART_OG2
IOgrp VCCU
EG_BA_HZG_RT IODev HmUART_Test
IOgrp VCCU
EG_BA_HZG_TC IODev HmUART_Test
IOgrp VCCU
EG_KUE_AAM IODev HmUART_EG
IOgrp VCCU:HmUART_EG
EG_KUE_RM IODev HmUART_OG1
IOgrp VCCU
EG_KU_HZG_RT IODev HmUART_OG1
IOgrp VCCU
EG_KU_HZG_TC IODev HmUART_Test
IOgrp VCCU
EG_RM_TEAMDEV IODev HmUART_EG
IOgrp VCCU
EG_SL_HZG_RT IODev HmUART_Test
IOgrp VCCU
EG_SL_HZG_TC IODev HmUART_EG
IOgrp VCCU
EG_SL_RM IODev HmUART_EG
IOgrp VCCU
EG_STH_AAM IODev HmUART_EG
IOgrp VCCU:HmUART_EG
EG_STH_HZG_RT IODev HmUART_OG1
IOgrp VCCU
EG_STH_T1_FB IODev HmUART_OG1
IOgrp VCCU
EG_STH_T1_VGT IODev HmUART_EG
IOgrp VCCU
EG_STH_ZS_T1VGF IODev HmUART_OG1
IOgrp VCCU
EG_VR_RM IODev HmUART_EG
IOgrp VCCU
EG_WC_HZG_RT IODev HmUART_OG1
IOgrp VCCU
EG_WC_HZG_TC IODev HmUART_AB_FR
IOgrp VCCU
EG_WI_HZG_RT IODev HmUART_EG
IOgrp VCCU
EG_WI_HZG_TC IODev HmUART_EG
IOgrp VCCU
EG_WR_RM IODev HmUART_OG1
IOgrp VCCU
EG_WZ_HZG_RT IODev HmUART_OG2
IOgrp VCCU
EG_WZ_HZG_TC IODev HmUART_Test
IOgrp VCCU
EG_WZ_RM IODev HmUART_Test
IOgrp VCCU
HM_6A8CB3 IODev HmUART_AB_FR
IOgrp VCCU
HM_6A9533 IODev HmUART_AB_GTO
IOgrp VCCU
OG1_BA_HZG_TC IODev HmUART_Test
IOgrp VCCU
OG1_KI_HZG_RT IODev HmUART_OG1
IOgrp VCCU
OG1_KI_HZG_TC IODev HmUART_OG1
IOgrp VCCU
OG1_KI_RM IODev HmUART_OG2
IOgrp VCCU
OG1_KUE_RM IODev HmUART_OG2
IOgrp VCCU
OG1_KU_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
OG1_KU_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG1_KU_OA_FS1I IODev HmUART_OG2
IOgrp VCCU
OG1_KU_OA_FS2I IODev HmUART_OG2
IOgrp VCCU
OG1_KU_WA_OAFGO IODev HmUART_OG2
IOgrp VCCU
OG1_RM_TEAMDEV IODev HmUART_OG1
IOgrp VCCU
OG1_SL_BLO IODev HmUART_OG1
IOgrp VCCU
OG1_SL_BLO_RLL IODev HmUART_Test
OG1_SL_FB1 IODev HmUART_OG1
IOgrp VCCU
OG1_SL_FB2 IODev HmUART_OG1
IOgrp VCCU
OG1_SL_FB3 IODev HmUART_OG2
IOgrp VCCU
OG1_SL_HZG_RT IODev HmUART_Test
IOgrp VCCU
OG1_SL_HZG_TC IODev HmUART_OG1
IOgrp VCCU
OG1_SL_RM IODev HmUART_OG1
IOgrp VCCU
OG1_STH_HZG_RT IODev HmUART_OG1
IOgrp VCCU
OG1_STH_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
OG1_STH_RM IODev HmUART_OG2
IOgrp VCCU
OG1_VR_AAM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
OG1_VR_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
OG1_WC_HZG_RT IODev HmUART_OG1
IOgrp VCCU
OG1_WC_HZG_TC IODev HmUART_OG1
IOgrp VCCU
OG1_WZ_BL_RGB IODev HmUART_Test
IOgrp VCCU
OG1_WZ_BL_VIO IODev HmUART_Test
IOgrp VCCU
OG1_WZ_HZG_RT IODev HmUART_Test
IOgrp VCCU
OG1_WZ_HZG_TC IODev HmUART_Test
IOgrp VCCU
OG1_WZ_RM IODev HmUART_Test
IOgrp VCCU
OG2_B1_KG IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG2_BU1_AAM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG2_BU1_HZG_RT IODev HmUART_Test
IOgrp VCCU
OG2_BU1_HZG_TC IODev HmUART_AB_GTO
IOgrp VCCU
OG2_BU1_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG2_BU2_HZG_RT1 IODev HmUART_AB_GTO
IOgrp VCCU
OG2_BU2_HZG_RT2 IODev HmUART_AB_GTO
IOgrp VCCU
OG2_BU2_HZG_TC IODev HmUART_AB_GTO
IOgrp VCCU
OG2_BU2_RM IODev HmUART_OG2
IOgrp VCCU
OG2_DB_RM IODev HmUART_OG2
IOgrp VCCU
OG2_EDV_RM IODev HmUART_OG2
IOgrp VCCU
OG2_RM_TEAMDEV IODev HmUART_OG2
IOgrp VCCU
OG2_VR_RM IODev HmUART_OG2
IOgrp VCCU
OG2_VR_STI IODev HmUART_AB_GTO
IOgrp VCCU
OG2_WC_HZG_RT IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG2_WC_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
STH_RM_TEAMDEV IODev HmUART_OG1
IOgrp VCCU
UESF1_AB_FR IODev HmUART_AB_FR
IOgrp VCCU
UESF1_AB_GAO IODev HmUART_Test
IOgrp VCCU
UESF1_EG_BA IODev HmUART_Test
IOgrp VCCU
UESF1_EG_KUE IODev HmUART_Test
IOgrp VCCU
UESF1_EG_SL IODev HmUART_EG
IOgrp VCCU
UESF1_EG_STH IODev HmUART_OG1
IOgrp VCCU
UESF1_EG_WC IODev HmUART_OG1
IOgrp VCCU
UESF1_EG_WI IODev HmUART_OG1
IOgrp VCCU
UESF1_EG_WZ IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
UESF1_OG1_BA IODev HmUART_AB_GTO
IOgrp VCCU
UESF1_OG1_KI IODev HmUART_OG1
IOgrp VCCU
UESF1_OG1_KUE IODev HmUART_OG2
IOgrp VCCU
UESF1_OG1_SL IODev HmUART_OG1
IOgrp VCCU
UESF1_OG1_WC IODev HmUART_OG2
IOgrp VCCU
UESF1_OG1_WZ IODev HmUART_Test
IOgrp VCCU
UESF1_OG2_BUE1_N IODev HmUART_AB_GTO
IOgrp VCCU
UESF1_OG2_BUE2_N IODev HmUART_AB_GTO
IOgrp VCCU
UESF1_OG2_BUE2_W IODev HmUART_AB_GTO
IOgrp VCCU
UESF1_OG2_DB IODev HmUART_OG2
IOgrp VCCU
UESF1_OG2_DBN IODev HmUART_OG2
IOgrp VCCU
UESF2_AB_GAO IODev HmUART_Test
IOgrp VCCU
UESF2_EG_SL IODev HmUART_EG
IOgrp VCCU
UESF2_EG_STH IODev HmUART_OG2
IOgrp VCCU
UESF2_EG_WZ IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
UESF2_OG1_SL IODev HmUART_OG1
IOgrp VCCU
UESF2_OG1_WZ IODev HmUART_Test
IOgrp VCCU
UESF2_OG2_BUE1_N IODev HmUART_AB_GTO
IOgrp VCCU
UESF2_OG2_BUE2_N IODev HmUART_OG2
IOgrp VCCU
UESF2_OG2_BUE2_W IODev HmUART_OG2
IOgrp VCCU
UESF2_OG2_DBN IODev HmUART_OG2
IOgrp VCCU
UESF3_OG1_STH IODev HmUART_OG1
IOgrp VCCU
UESF3_OG2_BUE1_N IODev HmUART_AB_GTO
IOgrp VCCU
UESF3_OG2_BUE2_W IODev HmUART_Test
IOgrp VCCU
UESF3_OG2_DBN IODev HmUART_OG2
IOgrp VCCU
UESF4_OG1_STH IODev HmUART_OG1
IOgrp VCCU
UESF5_OG2_STH IODev HmUART_AB_GTO
IOgrp VCCU
UEST1_AB_FR IODev HmUART_AB_FR
IOgrp VCCU
UEST1_AB_GAO IODev HmUART_Test
IOgrp VCCU
UEST1_AB_GTW IODev HmUART_Test
IOgrp VCCU
UEST1_AB_SA IODev HmUART_AB_FR
IOgrp VCCU
UEST1_EG_BA IODev HmUART_EG
IOgrp VCCU
UEST1_EG_KUE IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
UEST1_EG_STH IODev HmUART_OG1
IOgrp VCCU
UEST1_OG1_KUE IODev HmUART_OG2
IOgrp VCCU
UEST1_OG2_EDV IODev HmUART_OG2
IOgrp VCCU
UEST2_AB_GAO IODev HmUART_Test
IOgrp VCCU
UEST2_AB_GAW IODev HmUART_Test
IOgrp VCCU
VCCU IODev HmUART_AB_FR
IOgrp VCCU
besser wäre die ausgabe von:
list DEF=...... i:IODev a:IOgrpdamit nicht zufällig das attribut IODev angezeigt wird.
ich zähle jedenfalls nur (noch) 13 devices, die von HmUART_AB_FR angefunkt wurden. das umswitchen geht doch.
allerdings könnte es nach einem fhem restart zunächst eine "ungewünschte" io-zuweisung geben.
zeig mal "get hminfo protoEvents".
ZitatIch habe eine Änderung bei den diversen Geräten vorgenommen, wo das Attribut IOgrp nur mehr den Eintrag VCCU hat
im list sind aber noch etliche mit IOgrp=VCCU zu sehen.
list DEF=...... i:IODev a:IOgrpAB_BKTR_BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
AB_FR_AAM IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_FR
AB_FR_AD IODev HmUART_AB_FR
IOgrp VCCU
AB_FR_BL_RGB IODev HmUART_AB_GTO
IOgrp VCCU
AB_FR_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_AB_FR
AB_GAO_SSPPWT_FSI IODev HmUART_AB_FR
IOgrp VCCU
AB_GO_RM IODev HmUART_AB_FR
IOgrp VCCU
AB_GO_RM_TEAMDEV IODev HmUART_AB_FR
IOgrp VCCU
AB_MB_PS IODev HmUART_OG2
IOgrp VCCU
AB_SA_NT IODev HmUART_AB_FR
IOgrp VCCU
AB_SG_12BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
AB_SG_34BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
AB_SG_56BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
AB_SG_BLGOBWS IODev HmUART_Test
IOgrp VCCU
AB_SG_BLWSBWS IODev HmUART_OG1
IOgrp VCCU
AB_VG_BW IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
AB_WST_RS IODev HmUART_OG2
IOgrp VCCU
EG_BA_HZG_RT IODev HmUART_Test
IOgrp VCCU
EG_BA_HZG_TC IODev HmUART_Test
IOgrp VCCU
EG_KUE_AAM IODev HmUART_EG
IOgrp VCCU:HmUART_EG
EG_KUE_RM IODev HmUART_OG1
IOgrp VCCU
EG_KU_HZG_RT IODev HmUART_OG1
IOgrp VCCU
EG_KU_HZG_TC IODev HmUART_Test
IOgrp VCCU
EG_RM_TEAMDEV IODev HmUART_EG
IOgrp VCCU
EG_SL_HZG_RT IODev HmUART_Test
IOgrp VCCU
EG_SL_HZG_TC IODev HmUART_EG
IOgrp VCCU
EG_SL_RM IODev HmUART_EG
IOgrp VCCU
EG_STH_AAM IODev HmUART_EG
IOgrp VCCU:HmUART_EG
EG_STH_HZG_RT IODev HmUART_OG1
IOgrp VCCU
EG_STH_T1_FB IODev HmUART_OG1
IOgrp VCCU
EG_STH_T1_VGT IODev HmUART_EG
IOgrp VCCU
EG_STH_ZS_T1VGF IODev HmUART_OG1
IOgrp VCCU
EG_VR_RM IODev HmUART_EG
IOgrp VCCU
EG_WC_HZG_RT IODev HmUART_EG
IOgrp VCCU
EG_WC_HZG_TC IODev HmUART_AB_FR
IOgrp VCCU
EG_WI_HZG_RT IODev HmUART_EG
IOgrp VCCU
EG_WI_HZG_TC IODev HmUART_EG
IOgrp VCCU
EG_WR_RM IODev HmUART_OG1
IOgrp VCCU
EG_WZ_HZG_RT IODev HmUART_Test
IOgrp VCCU
EG_WZ_HZG_TC IODev HmUART_Test
IOgrp VCCU
EG_WZ_RM IODev HmUART_Test
IOgrp VCCU
HM_6A8CB3 IODev HmUART_AB_FR
IOgrp VCCU
HM_6A9533 IODev HmUART_AB_FR
IOgrp VCCU
OG1_BA_HZG_TC IODev HmUART_Test
IOgrp VCCU
OG1_KI_HZG_RT IODev HmUART_OG1
IOgrp VCCU
OG1_KI_HZG_TC IODev HmUART_OG1
IOgrp VCCU
OG1_KI_RM IODev HmUART_OG2
IOgrp VCCU
OG1_KUE_RM IODev HmUART_OG2
IOgrp VCCU
OG1_KU_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
OG1_KU_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG1_KU_OA_FS1I IODev HmUART_OG2
IOgrp VCCU
OG1_KU_OA_FS2I IODev HmUART_OG2
IOgrp VCCU
OG1_KU_WA_OAFGO IODev HmUART_OG2
IOgrp VCCU
OG1_RM_TEAMDEV IODev HmUART_OG1
IOgrp VCCU
OG1_SL_BLO IODev HmUART_OG1
IOgrp VCCU
OG1_SL_BLO_RLL IODev HmUART_Test
OG1_SL_FB1 IODev HmUART_OG1
IOgrp VCCU
OG1_SL_FB2 IODev HmUART_OG1
IOgrp VCCU
OG1_SL_FB3 IODev HmUART_OG2
IOgrp VCCU
OG1_SL_HZG_RT IODev HmUART_Test
IOgrp VCCU
OG1_SL_HZG_TC IODev HmUART_OG1
IOgrp VCCU
OG1_SL_RM IODev HmUART_OG1
IOgrp VCCU
OG1_STH_HZG_RT IODev HmUART_OG1
IOgrp VCCU
OG1_STH_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
OG1_STH_RM IODev HmUART_OG2
IOgrp VCCU
OG1_VR_AAM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
OG1_VR_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
OG1_WC_HZG_RT IODev HmUART_OG1
IOgrp VCCU
OG1_WC_HZG_TC IODev HmUART_OG1
IOgrp VCCU
OG1_WZ_BL_RGB IODev HmUART_Test
IOgrp VCCU
OG1_WZ_BL_VIO IODev HmUART_Test
IOgrp VCCU
OG1_WZ_HZG_RT IODev HmUART_Test
IOgrp VCCU
OG1_WZ_HZG_TC IODev HmUART_Test
IOgrp VCCU
OG1_WZ_RM IODev HmUART_Test
IOgrp VCCU
OG2_B1_KG IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG2_BU1_AAM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG2_BU1_HZG_RT IODev HmUART_Test
IOgrp VCCU
OG2_BU1_HZG_TC IODev HmUART_AB_GTO
IOgrp VCCU
OG2_BU1_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG2_BU2_HZG_RT1 IODev HmUART_AB_GTO
IOgrp VCCU
OG2_BU2_HZG_RT2 IODev HmUART_AB_GTO
IOgrp VCCU
OG2_BU2_HZG_TC IODev HmUART_AB_GTO
IOgrp VCCU
OG2_BU2_RM IODev HmUART_OG2
IOgrp VCCU
OG2_DB_RM IODev HmUART_OG2
IOgrp VCCU
OG2_EDV_RM IODev HmUART_OG2
IOgrp VCCU
OG2_RM_TEAMDEV IODev HmUART_OG2
IOgrp VCCU
OG2_VR_RM IODev HmUART_OG2
IOgrp VCCU
OG2_VR_STI IODev HmUART_AB_GTO
IOgrp VCCU
OG2_WC_HZG_RT IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
OG2_WC_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
STH_RM_TEAMDEV IODev HmUART_OG1
IOgrp VCCU
UESF1_AB_FR IODev HmUART_AB_FR
IOgrp VCCU
UESF1_AB_GAO IODev HmUART_Test
IOgrp VCCU
UESF1_EG_BA IODev HmUART_Test
IOgrp VCCU
UESF1_EG_KUE IODev HmUART_Test
IOgrp VCCU
UESF1_EG_SL IODev HmUART_EG
IOgrp VCCU
UESF1_EG_STH IODev HmUART_OG2
IOgrp VCCU
UESF1_EG_WC IODev HmUART_OG1
IOgrp VCCU
UESF1_EG_WI IODev HmUART_OG1
IOgrp VCCU
UESF1_EG_WZ IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
UESF1_OG1_BA IODev HmUART_AB_GTO
IOgrp VCCU
UESF1_OG1_KI IODev HmUART_OG1
IOgrp VCCU
UESF1_OG1_KUE IODev HmUART_OG2
IOgrp VCCU
UESF1_OG1_SL IODev HmUART_OG1
IOgrp VCCU
UESF1_OG1_WC IODev HmUART_OG2
IOgrp VCCU
UESF1_OG1_WZ IODev HmUART_Test
IOgrp VCCU
UESF1_OG2_BUE1_N IODev HmUART_AB_GTO
IOgrp VCCU
UESF1_OG2_BUE2_N IODev HmUART_AB_GTO
IOgrp VCCU
UESF1_OG2_BUE2_W IODev HmUART_AB_GTO
IOgrp VCCU
UESF1_OG2_DB IODev HmUART_OG2
IOgrp VCCU
UESF1_OG2_DBN IODev HmUART_OG2
IOgrp VCCU
UESF2_AB_GAO IODev HmUART_Test
IOgrp VCCU
UESF2_EG_SL IODev HmUART_EG
IOgrp VCCU
UESF2_EG_STH IODev HmUART_OG2
IOgrp VCCU
UESF2_EG_WZ IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1
UESF2_OG1_SL IODev HmUART_OG1
IOgrp VCCU
UESF2_OG1_WZ IODev HmUART_Test
IOgrp VCCU
UESF2_OG2_BUE1_N IODev HmUART_AB_GTO
IOgrp VCCU
UESF2_OG2_BUE2_N IODev HmUART_OG2
IOgrp VCCU
UESF2_OG2_BUE2_W IODev HmUART_AB_GTO
IOgrp VCCU
UESF2_OG2_DBN IODev HmUART_OG2
IOgrp VCCU
UESF3_OG1_STH IODev HmUART_OG1
IOgrp VCCU
UESF3_OG2_BUE1_N IODev HmUART_AB_GTO
IOgrp VCCU
UESF3_OG2_BUE2_W IODev HmUART_Test
IOgrp VCCU
UESF3_OG2_DBN IODev HmUART_OG2
IOgrp VCCU
UESF4_OG1_STH IODev HmUART_OG1
IOgrp VCCU
UESF5_OG2_STH IODev HmUART_AB_GTO
IOgrp VCCU
UEST1_AB_FR IODev HmUART_AB_FR
IOgrp VCCU
UEST1_AB_GAO IODev HmUART_Test
IOgrp VCCU
UEST1_AB_GTW IODev HmUART_Test
IOgrp VCCU
UEST1_AB_SA IODev HmUART_Test
IOgrp VCCU
UEST1_EG_BA IODev HmUART_EG
IOgrp VCCU
UEST1_EG_KUE IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2
UEST1_EG_STH IODev HmUART_OG1
IOgrp VCCU
UEST1_OG1_KUE IODev HmUART_Test
IOgrp VCCU
UEST1_OG2_EDV IODev HmUART_OG2
IOgrp VCCU
UEST2_AB_GAO IODev HmUART_Test
IOgrp VCCU
UEST2_AB_GAW IODev HmUART_Test
IOgrp VCCU
VCCU IODev HmUART_AB_FR
IOgrp VCCUZitatallerdings könnte es nach einem fhem restart zunächst eine "ungewünschte" io-zuweisung geben.
Auch ohne FHEM Restart wird mindestens einmal pro Tag der Zustand für HmUART_AB_FR erreicht. Warum nur bei diesem der Status erreicht wird ist mir unklar. Meinen Beobachtungen nach dürfte es an der Reihenfolge liegen, wo der erste mit der RSSI Zuweisung in diesen Status kommt.
Zitatim list sind aber noch etliche mit IOgrp=VCCU zu sehen.
Ich glaube da haben wir ein Missverständnis. Es sollten bei den Geräten nur das Attribut
IOgrp VCCU stehen, damit die RSSI Zuweisung greift.
Jedenfalls sehe ich mit Euren Tips noch einiges zu optimieren.
get HMinfo protoEventsSiehe Anhang.
ZitatIch glaube da haben wir ein Missverständnis. Es sollten bei den Geräten nur das Attribut IOgrp VCCU stehen, damit die RSSI Zuweisung greift.
warum keine prefered io mehr?
gerade in deiner konstellation (132 devices mit 6 io auf mehrere gebäude verteilt) wird es mit IOgrp=VCCU bei jedem fhem restart zum chaos führen.
beim start gibt es keine rssi. also wird vermutlich zunächst immer das erste der liste in attr IOList der vccu gewählt.
ausserdem muss man den load möglichst gerecht verteilen.
########################
aktuell steht noch bei 11 devices das io HmUART_AB_FR im internal IODev.
davon verursachen sicherlich diese beiden den grössten anteil am aktuellen load von 51%.
es wurde noch nichts empfangen, also gibt es auch noch keine rssi. vermutlich ist das io hier völlig sinnlos.
zudem werden haufenweise burst gesendet, was zusätzlich auf load und batterie aller burst devices geht.
protoEvents send to devices done:
name :State |CmdPend |Snd |SndB |Rcv |RcvB |Resnd #CmdDel |ResndFail |Nack |IOerr
HM_6A8CB3 : done_Errors:1 | - | 1476 | 2475 | - | - | 999 # 1568 | 869 | - | 67
HM_6A9533 : done_Errors:1 | - | 1014 | 1735 | - | - | 721 # 1532 | 629 | - | 38
########################
ich empfehle dringend bei allen "stationären" devices mindestens 1 prefered io zu setzen, besser 2 oder mehr.
HMinfoTools.js macht anhand der gesammelten rssi vorschläge für attr IOgrp und erzeugt ein ranking für die io (1. kriterium: anzahl empfangener messages; 2. kriterium bei gleicher anzahl: bester average).
für jedes device werden, wenn möglich, 2 prefered io gewählt. mit 2-3 klicks ist erstmal überall was gesetzt.
anschliessend müsstest du je nach load ggf noch umverteilen.
es wäre für mich auch interessant, ob HMinfoTools mit deiner vielzahl an devices klar kommt. 8)
solltest du HMinfoTools.js installieren: es sollte ohne fhem restart möglich sein, so dass die gesammelten rssi erhalten bleiben.
Zitatich empfehle dringend bei allen "stationären" devices mindestens 1 prefered io zu setzen, besser 2 oder mehr.
Da war dann meine Überlegung falsch, die Priorisierungen über RSSI durchzuführen.
Das werde ich wieder zurückstellen, wie ich es noch vor zwei Monaten hatte.
ZitatHMinfoTools.js macht anhand der gesammelten rssi vorschläge
Damit werde ich mich beschäftigen.
Zitatwarum keine prefered io mehr?
Ich habe die Änderungen betreffend der prefered IOs durchgeführt.
Was mir dabei aufgefallen ist, dass Oregon IODev von den Sensoren PCR800 und WGR800 sich in dieser Liste befinden.
Eigenartig ist daran, das nicht alle Oregon Geräte aufscheinen. Eigentlich sollten alle oder keine Oregon Geräte gelistet werden.
list DEF=...... i:IODev a:IOgrpAB_BKTR_BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
AB_FR_AAM IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_FR_AD IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_FR_BL_RGB IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_FR_RM IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG1,HmUART_OG2
AB_GAO_SSPPWT_FSI IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_GO_RM IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_GO_RM_TEAMDEV IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_MB_PS IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_SA_NT IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_SG_12BW IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG1,HmUART_EG
AB_SG_34BW IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_OG2
AB_SG_56BW IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_OG2
AB_SG_BLGOBWS IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_SG_BLWSBWS IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_VG_BW IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
AB_WST_RS IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
EG_BA_HZG_RT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
EG_BA_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
EG_KUE_AAM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_KUE_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_FR,HmUART_OG2
EG_KU_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_EG,HmUART_OG2
EG_KU_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_EG
EG_RM_TEAMDEV IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1
EG_SL_HZG_RT IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
EG_SL_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
EG_SL_RM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_GTO
EG_STH_AAM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_STH_HZG_RT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_STH_T1_FB IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_STH_T1_VGT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_STH_ZS_T1VGF IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_VR_RM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1
EG_WC_HZG_RT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_WC_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_WI_HZG_RT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_WI_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_WR_RM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1
EG_WZ_HZG_RT IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_EG
EG_WZ_HZG_TC IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
EG_WZ_RM IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1,HmUART_OG2
HM_6A8CB3 IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG,HmUART_OG1,HmUART_OG2,HmUART_Test
HM_6A9533 IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG,HmUART_OG1,HmUART_OG2,HmUART_Test
OG1_BA_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_EG
OG1_KI_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2
OG1_KI_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2
OG1_KI_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2,HmUART_AB_FR
OG1_KUE_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR,HmUART_EG
OG1_KU_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_KU_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
OG1_KU_OA_FS1I IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_KU_OA_FS2I IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_KU_WA_OAFGO IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
OG1_RM_TEAMDEV IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_OG2
OG1_SL_BLO IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_SL_BLO_RLL IODev HmUART_OG1
OG1_SL_FB1 IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_SL_FB2 IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_SL_FB3 IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_SL_HZG_RT IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1,HmUART_OG2
OG1_SL_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_GTO
OG1_SL_RM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_GTO
OG1_STH_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_EG
OG1_STH_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_EG,HmUART_AB_FR
OG1_STH_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_EG
OG1_VR_AAM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2,HmUART_AB_FR
OG1_VR_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2
OG1_WC_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_WC_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_WZ_BL_RGB IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_WZ_BL_VIO IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_GTO
OG1_WZ_HZG_RT IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_OG2
OG1_WZ_HZG_TC IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_OG2
OG1_WZ_RM IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG2,HmUART_OG1,HmUART_EG
OG2_B1_KG IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_BU1_AAM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
OG2_BU1_HZG_RT IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_BU1_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_BU1_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_BU2_HZG_RT1 IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_GTO
OG2_BU2_HZG_RT2 IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG2,HmUART_OG1
OG2_BU2_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_GTO
OG2_BU2_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_DB_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_EDV_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_FR,HmUART_OG1
OG2_RM_TEAMDEV IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO,HmUART_AB_FR
OG2_VR_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
OG2_VR_STI IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_WC_HZG_RT IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
OG2_WC_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
PCR800 IODev sduino_ab
STH_RM_TEAMDEV IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_OG2
UESF1_AB_FR IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
UESF1_AB_GAO IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
UESF1_EG_BA IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
UESF1_EG_KUE IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
UESF1_EG_SL IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
UESF1_EG_STH IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
UESF1_EG_WC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_FR,HmUART_OG1
UESF1_EG_WI IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1
UESF1_EG_WZ IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
UESF1_OG1_BA IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_EG
UESF1_OG1_KI IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2
UESF1_OG1_KUE IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
UESF1_OG1_SL IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_EG
UESF1_OG1_WC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
UESF1_OG1_WZ IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_OG2
UESF1_OG2_BUE1_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF1_OG2_BUE2_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF1_OG2_BUE2_W IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG2,HmUART_OG1
UESF1_OG2_DB IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
UESF1_OG2_DBN IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF2_AB_GAO IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
UESF2_EG_SL IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
UESF2_EG_STH IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
UESF2_EG_WZ IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
UESF2_OG1_SL IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_EG
UESF2_OG1_WZ IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_OG2
UESF2_OG2_BUE1_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF2_OG2_BUE2_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF2_OG2_BUE2_W IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF2_OG2_DBN IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF3_OG1_STH IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_OG2
UESF3_OG2_BUE1_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF3_OG2_BUE2_W IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
UESF3_OG2_DBN IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF4_OG1_STH IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
UESF5_OG2_STH IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
UEST1_AB_FR IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
UEST1_AB_GAO IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
UEST1_AB_GTW IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
UEST1_AB_SA IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
UEST1_EG_BA IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_GTO
UEST1_EG_KUE IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_EG
UEST1_EG_STH IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_FR,HmUART_OG1
UEST1_OG1_KUE IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
UEST1_OG2_EDV IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
UEST2_AB_GAO IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
UEST2_AB_GAW IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
VCCU IODev HmUART_AB_FR
IOgrp VCCU
WGR800 IODev sduino_abDas mit dem HMinfoTools.js habe ich jetzt zwar installiert, aber so richtig sehe ich daraus nicht wirklich etwas Brauchbares.
Version HMinfoTools.jsno loaded modules found that match: HMinfoTools.js
doif.js 24438 2021-05-14 18:08:18Z Ellert
fhemweb.js 25983 2022-04-19 17:26:44Z rudolfkoenig
fhemweb_readingsGroup.js 15189 2017-10-03 17:53:27Z justme1968Wo finde ich die ID des td-elementes
id="hminfotools_weblink".
Derzeit habe ich die Nr. von HMinfo eingetragen.
Beim durchstöbern ist mir Fehler aufgefallen.
https://forum.fhem.de/index.php/topic,112825.msg1184583.html#msg1184583
############
## Perlcode um für SystemCheck die Fehler zu senden #######
sub HM_Error($$)
{
my ($hminfo, $event) = @_;
my $text = "";
if ($event =~ /^ERR_[^_].*/) {
# Event caused by sumERROR
$text = "$event:".InternalVal($hminfo, "ERR_names", "");
}
elsif ($event =~ /^ERR__protocol:.*/) {
# Protocol error
$text = "$event:".InternalVal($hminfo, "ERR__protoNames", "");
}
elsif ($event =~ /^ERR__unreachable:.*/) {
# Unreachable
$text = "$event:".InternalVal($hminfo, "W__unreachNames", "")];
}
else {
$text = "Unknown event: $event";
}
# fhem "set teleBot message @#FHEM $text" ;
fhem "msg push $text" ;
}Hier ist bei
"W__unreachNames", "")]; ein Klammerfehler.
Zitatzudem werden haufenweise burst gesendet, was zusätzlich auf load und batterie aller burst devices geht.
Bei den Fenstersensoren und den RTs & CTs wird BURST benötigt. Hat sich da etwas geändert?
Sind dir andere Geräte auch aufgefallen die BURST verwenden? Diese würde ich dann ändern.
Update: 2022.07.10 18:15
Der Debugger HMinfoTools.js dürfte anscheinen nicht laufen. Da muss ich noch einen Konfigurationsfehler haben.Der Fehler lag in der Datei controls.txt. Der Eintrag wurde ohne Zeilenumruch eingetragen, wodurch beide controls.txt Einträge nicht mehr funktionieren.
Ständige Log-Einträge seit der Änderungen von HM-Info
2022.07.10 18:39:54.590 3: CUL_HM set UEST2_AB_GAW clear attack
2022.07.10 18:39:54.592 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:54.968 3: HMinfo HMinfo get:update :
2022.07.10 18:39:54.969 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:55.319 3: HMinfo HMinfo get:update :
2022.07.10 18:39:55.320 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:55.671 3: HMinfo HMinfo get:update :
2022.07.10 18:39:55.672 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:56.024 1: [Freezemon] myFreezemon: possible freeze starting at 18:39:39, delay is 17.022 possibly caused by: tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-I2C_SUSV_Poll_GPIO(SUSV) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMUARTLGW_CheckCredits(HmUART_AB_GTO) tmr-HMUARTLGW_CheckCredits(HmUART_OG2) tmr-HMUARTLGW_CheckCredits(HmUART_Test) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMUARTLGW_CheckCredits(HmUART_EG) tmr-HMUARTLGW_CheckCredits(HmUART_OG1) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_init(N/A) tmr-HMinfo_autoUpdate(HMinfo) tmr-GPIO4_DeviceUpdateLoop(OG2_EDV_R_EDVVT) tmr-FHEM::Astro::Update(myAstro) tmr-CODE(0x4274968)(GetStatus) tmr-CODE(0x283d690)(SIGNALduino_KeepAlive) tmr-CODE(0x283d690)(SIGNALduino_KeepAlive) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo)
2022.07.10 18:39:56.077 3: HMinfo HMinfo get:update :
2022.07.10 18:39:56.078 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:56.429 3: HMinfo HMinfo get:update :
2022.07.10 18:39:56.429 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:56.820 3: HMinfo HMinfo get:update :
2022.07.10 18:39:56.821 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:57.171 3: HMinfo HMinfo get:update :
2022.07.10 18:39:57.172 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:57.551 3: HMinfo HMinfo get:update :
2022.07.10 18:39:57.552 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:57.919 3: HMinfo HMinfo get:update :
2022.07.10 18:39:57.920 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:58.255 3: HMinfo HMinfo get:update :
2022.07.10 18:39:58.256 3: CUL_HM set ActionDetector update noArg
2022.07.10 18:39:58.606 3: HMinfo HMinfo get:update :
2022.07.10 18:39:58.607 3: CUL_HM set ActionDetector update noArgDie Übersicht vom HM-Tool ist sehr unübersichtlich. Es wird durch die Readings von HM-Info auseinander gestreckt.
moin.
ZitatWas mir dabei aufgefallen ist, dass Oregon IODev von den Sensoren PCR800 und WGR800 sich in dieser Liste befinden.
"list DEF=......" zeigt alle devices mit 6 zeichen in der DEF, also alles ok.
ZitatSind dir andere Geräte auch aufgefallen die BURST verwenden? Diese würde ich dann ändern.
in der spalte "SndB" von protoEvents stehen alle burst messages die fhem an die devices gesendet hat.
ZitatBeim durchstöbern ist mir Fehler aufgefallen.
woher kommt der code? von mir nicht, denke ich. edit: habe den code gefunden. ist von @RalfRog ein paar beiträge über dem gesendeten link. da kann ich nichts editieren.
ZitatStändige Log-Einträge seit der Änderungen von HM-Info
vermutlich hast du "attr hminfo autoupdate" falsch gesetzt.
bei dir kommen die einträge ja im sekundentakt, 10min sollten dicke ausreichen. ggf kann man auch zusätzlich manuell "updaten", wenn man in der kopfzeile von hminfotools auf das wort "updated" klickt.
ich habe bei hminfo und im actiondetector verbose=2 gesetzt, um diese einträge zu canceln. mach das aber erst, wenn du den sekundentakt "repariert" hast.
### hminfotoolsZitatDer Fehler lag in der Datei controls.txt. Der Eintrag wurde ohne Zeilenumruch eingetragen, wodurch beide controls.txt Einträge nicht mehr funktionieren.
seltsam, bei anderen hat es funktioniert.
wie hast du die dateien nach fhem gebracht?
ZitatWo finde ich die ID des td-elementes id="hminfotools_weblink".
Derzeit habe ich die Nr. von HMinfo eingetragen.
falsch.
id="hminfotools_weblink" musst du so übernehmen, siehe beschreibung:
Zitat- zusätzlich ist es möglich HMinfoTools auf raumseiten anzuzeigen, zb mit einem weblink device:
defmod my_weblink weblink htmlCode <table><tbody><tr><td id="hminfotools_weblink" dev="hminfo"></td></tr></tbody></table>
der name des weblink devices (my_weblink) ist beliebig, die id des td-elementes ist zwingend einzuhalten, das attribut dev="hminfo" des td-elementes muss den namen des hminfo devices bekommen.
ZitatDie Übersicht vom HM-Tool ist sehr unübersichtlich. Es wird durch die Readings von HM-Info auseinander gestreckt.
ja leider. und mit vielen fehlern wird es immer "schlimmer". ;)
am kompaktesten ist die weblink-version in einem eigenen raum.
tipp: ein fehlerfreies system zeigt nur die kopfzeile, wenn als ansicht nur die fehlerbehafteten devices gewählt sind (checkbox am ende der kopfzeile ist nicht gesetzt).
ich würde zunächst alle gemeldeten fehler von hminfo configCheck beseitigen (rote 3-fach-zahnräder) und alle protokollfehler löschen (weisse LED/runder kreis ganz links in der kopfzeile).
protokollfehler sammelt cul_hm ebenfalls wie rssi werte, fhem restart löscht sie.
ein gutes stabiles system zeigt keine protokollfehler (eine optimale io zuordnung ist voraussetzung).
wenn dann vermehrt devices protokollfehler zeigen, sollte man bei diesen devices mal nachforschen und verbessern.
für die rssi_overview ansicht musst du das zahnrad ganz rechts in der kopfzeile klicken.
je nachdem ob vorher
alle devices gewählt sind (checkbox gesetzt) kann man dann auch bei
allen devices in der rssi overview das attr IOgrp ändern.
schön, dass es grundsätzlich erst einmal läuft.
Ständige Log-Einträge seit der Änderungen von HM-Info
Das ist meine HMinfodefine HMinfo HMinfo
attr HMinfo alias HM Info
attr HMinfo autoArchive 1
attr HMinfo autoLoadArchive 1_load
attr HMinfo autoUpdate 00:10
attr HMinfo configDir /media/hdd/fhem/homematic/config/
attr HMinfo configFilename regConfig.cfg
attr HMinfo configTempFile tempList.cfg
attr HMinfo event-on-change-reading .*
attr HMinfo group .HomeMatic
attr HMinfo icon edit_paste
attr HMinfo room _HM
attr HMinfo sumERROR battery:ok,sabotageError:off,powerError:ok,overload:off,overheat:off,reduced:off,motorError:no,error:none,uncertain:yes,smoke_detect:none,cover:closed,cfgState:ok,sabotageAttack_ErrIoAttack_cnt:ok,R_tempList_State:verified,R_P1_tempList_State:verified,R_P2_tempList_State:verified,R_P3_tempList_State:verified,valveCtrl:restart:unknown:ok:miss_1:miss_2:miss_3:miss_4:miss_5,smokeChamber:ok,alarmTest:ok
attr HMinfo sumStatus battery,sabotageError,powerError,motor
attr HMinfo webCmd update:protoEvents short:rssi:peerXref:configCheck:modelsZitatseltsam, bei anderen hat es funktioniert.
wie hast du die dateien nach fhem gebracht?
Ich musste in der controls.txt Datei eine Leerzeile einfügen. Warum diese fehlte, ist mir nicht klar.
Mit der Leerzeile funktioniert es wieder wie gewohnt.
update add https://raw.githubusercontent.com/frank962/fhem/main/autoupdate/controls_HMtools.txt
Sorry, aber ich finde den Hinweis nicht, damit ich die
id des td-elementes finde.
ZitatSorry, aber ich finde den Hinweis nicht, damit ich die id des td-elementes finde.
du musst keine id suchen.
beim weblink beispiel muss du nur den devicenamen von deinem hminfo device ändern:
dein hminfo device hat den namen "HMinfo", also sollte folgendes funktionieren:
Zitatdefine my_weblink weblink htmlCode <table><tbody><tr><td id="hminfotools_weblink" dev="HMinfo"></td></tr></tbody></table>
ZitatStändige Log-Einträge seit der Änderungen von HM-Info
das attribut autoupdate sieht gut aus.
es sollten schon "ständige" einträge auftauchen allerdings im abstand von 10 min.
die svn version macht glaube ich dann alle 10min doppelte einträge.
Zitatdu musst keine id suchen.
Da ist die Info für mich verwirrend gewesen.
die id des td-elementes ist zwingend einzuhaltenZitatdein hminfo device hat den namen "HMinfo", also sollte folgendes funktionieren:
Das hatte ich auch so nach meinem HMinfo benannt.
Zitatdas attribut autoupdate sieht gut aus.
es sollten schon "ständige" einträge auftauchen allerdings im abstand von 10 min.
Da dürfte ich noch einen Fehler haben.
Nach wie vor kommen sehr viele LOG-Einträge, verursacht durch HM, vor, und FHEM-WEB ist sehr gebremmst.
2022.07.11 18:00:57.999 3: HMinfo HMinfo get:update :
2022.07.11 18:00:58.000 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:00:58.356 3: [Freezemon] myFreezemon: possible freeze starting at 18:00:55, delay is 3.355 possibly caused by: tmr-JSONMETER_GetUpdate(EnergieGas) tmr-JSONMETER_GetUpdate(EnergieAB) tmr-JSONMETER_GetUpdate(EnergieEG) tmr-JSONMETER_GetUpdate(EnergieOG1) tmr-JSONMETER_GetUpdate(EnergieOG2) tmr-GPIO4_DeviceUpdateLoop(KG_RT) tmr-I2C_SUSV_Poll_GPIO(SUSV) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-freezemon_ProcessTimer(myFreezemon)
2022.07.11 18:00:59.629 3: HMinfo HMinfo get:loadConfig :
2022.07.11 18:00:59.728 3: HMinfo HMinfo get:update :
2022.07.11 18:00:59.729 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:00.083 3: HMinfo HMinfo get:update :
2022.07.11 18:01:00.084 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:05.306 3: HMinfo HMinfo get:update :
2022.07.11 18:01:05.307 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:05.705 3: HMinfo HMinfo get:update :
2022.07.11 18:01:05.706 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:06.085 2: [Freezemon] myFreezemon: possible freeze starting at 18:00:59, delay is 7.084 possibly caused by: tmr-GPIO4_DeviceUpdateLoop(OG2_EDV_R_RT) tmr-HMinfo_init(N/A) tmr-I2C_SUSV_Poll_GPIO(SUSV) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo)
2022.07.11 18:01:06.160 3: HMinfo HMinfo get:configCheck :-f,^(OG1_VR_AAM|OG1_VR_AAM_Led|OG1_VR_AAM_Mp3|OG1_VR_AAM)$
2022.07.11 18:01:07.175 3: HMinfo HMinfo get:update :
2022.07.11 18:01:07.176 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:07.531 3: HMinfo HMinfo get:update :
2022.07.11 18:01:07.532 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:07.889 3: HMinfo HMinfo get:update :
2022.07.11 18:01:07.890 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:08.245 3: HMinfo HMinfo get:update :
2022.07.11 18:01:08.246 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:08.600 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 2239
2022.07.11 18:01:08.618 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 2240
2022.07.11 18:01:08.641 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 2241
2022.07.11 18:01:08.664 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 2242
2022.07.11 18:01:08.688 1: Timeout for JSONMETER_GetJsonFile reached, terminated process 2243
2022.07.11 18:01:08.954 3: HMinfo HMinfo get:loadConfig :
2022.07.11 18:01:17.358 1: [Freezemon] myFreezemon: possible freeze starting at 18:01:07, delay is 10.356 possibly caused by: tmr-I2C_SUSV_Poll_GPIO(SUSV) tmr-CUL_HM_cfgStateUpdate(OG1_VR_AAM) tmr-GPIO4_DeviceUpdateLoop(OG2_EDV_R_EDVVT) tmr-FHEM::Astro::Update(myAstro) tmr-CODE(0x40639a0)(GetStatus) tmr-CODE(0x2630820)(SIGNALduino_KeepAlive) tmr-CODE(0x2630820)(SIGNALduino_KeepAlive) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_FHEM_Server) tmr-NUT_PollTimer(APCUSVL) tmr-NUT_PollTimer(APCUSVLB) tmr-HMUARTLGW_CheckCredits(HmUART_OG1) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-FHEM2FHEM_keepalive(F2F_Rasp03) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-BlockingKill(N/A) tmr-BlockingKill(N/A) tmr-BlockingKill(N/A) tmr-BlockingKill(N/A) tmr-BlockingKill(N/A) tmr-HMinfo_init(N/A) tmr-FHEM2FHEM_keepalive(F2F_Rasp03) tmr-HMUARTLGW_CheckCredits(HmUART_EG)
2022.07.11 18:01:17.425 3: HMinfo HMinfo get:update :
2022.07.11 18:01:17.426 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:17.777 3: HMinfo HMinfo get:update :
2022.07.11 18:01:17.778 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:18.127 3: HMinfo HMinfo get:update :
2022.07.11 18:01:18.128 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:18.478 3: HMinfo HMinfo get:update :
2022.07.11 18:01:18.479 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:18.909 3: HMinfo HMinfo get:update :
2022.07.11 18:01:18.910 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:19.535 3: HMinfo HMinfo get:loadConfig :
2022.07.11 18:01:19.631 3: HMinfo HMinfo get:update :
2022.07.11 18:01:19.632 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:19.980 3: HMinfo HMinfo get:update :
2022.07.11 18:01:19.981 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:20.330 3: HMinfo HMinfo get:update :
2022.07.11 18:01:20.331 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:23.703 3: HMinfo HMinfo get:update :
2022.07.11 18:01:23.703 3: CUL_HM set ActionDetector update noArg
2022.07.11 18:01:24.063 2: [Freezemon] myFreezemon: possible freeze starting at 18:01:18, delay is 6.061 possibly caused by: tmr-I2C_SUSV_Poll_GPIO(SUSV) tmr-CODE(0x25d5c30)(SIGNALduino_HandleWriteQueue) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-BlockingStart(N/A) tmr-BlockingStart(N/A) tmr-BlockingStart(N/A) tmr-BlockingStart(N/A) tmr-BlockingStart(N/A) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMUARTLGW_CheckCredits(HmUART_Test) tmr-HMUARTLGW_CheckCredits(HmUART_AB_GTO) tmr-HMUARTLGW_CheckCredits(HmUART_OG2) tmr-HMUARTLGW_CheckCredits(HmUART_AB_FR) tmr-HMinfo_init(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HMinfo_autoUpdate(HMinfo) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_FHEM_Server) tmr-NUT_PollTimer(APCUSVL) tmr-NUT_PollTimer(APCUSVLB) tmr-HMinfo_autoUpdate(HMinfo)
2022.07.11 18:01:24.112 3: HMinfo HMinfo get:update :
2022.07.11 18:01:24.113 3: CUL_HM set ActionDetector update noArgDas sind alles sehr nützliche Infos und Tools.
Nächste Aktion die Burst Reduzierung, sofern möglich.
logeinträge:
schau mal ob du ein at/notify/doif in fhem.cfg hast, welches entweder "set hminfo update" ausführt oder ob "attr hminfo autoupdate" gesetzt wird.
wenn du nichts findest probiere zuerst "fhem restart", danach ein reboot des servers.
wenn alles nichts hilft, lösche "attr hminfo autoupdate" bis zur klärung des problems, da sonst zu viel resourcen verbraten werden.
so lange musst du dann manuelle updates bei hminfo machen, damit die tabelle aktuell ist.
zuerst prefered io setzen, würde ich sagen.
Folgendes habe ich durchgeführt:Zitatat/notify/doif in fhem.cfg hast
attr HMinfo autoupdate war gesetzt.
Ist gesetzt => entferntZitatzuerst "fhem restart", danach ein reboot des servers.
Hat keine Änderung ergeben.
lösche "attr hminfo autoupdate" bis zur klärung des problemsGelöscht, und hat auch keine Änderung gebracht.
Zur Sicherheit nach alldem wieder einen Reboot durchgeführt.
LOG nach den Änderungen2022.07.12 10:13:13.937 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:13:17.052 3: MQTT2_FHEM_Server: MQTT2_FHEM_Server_192.168.17.161_60445 left us (keepalive check)
2022.07.12 10:13:19.212 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:13:24.492 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:13:29.767 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:13:34.190 2: SUSV: unknown battery state 148 - 212 148
2022.07.12 10:13:35.094 3: [Freezemon] myFreezemon: possible freeze starting at 10:13:34, delay is 1.092 possibly caused by: tmr-I2C_SUSV_Poll(SUSV) tmr-FW_closeInactiveClients(N/A) tmr-SYSMON_Update(sysmon) tmr-JSONMETER_GetUpdate(EnergieGas) tmr-JSONMETER_GetUpdate(EnergieAB) tmr-JSONMETER_GetUpdate(EnergieEG) tmr-JSONMETER_GetUpdate(EnergieOG1) tmr-JSONMETER_GetUpdate(EnergieOG2) tmr-GPIO4_DeviceUpdateLoop(KG_RT) tmr-FHEM::Astro::Update(myAstro) tmr-I2C_SUSV_Poll_GPIO(SUSV)
2022.07.12 10:13:35.549 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:13:38.138 3: [Freezemon] myFreezemon: possible freeze starting at 10:13:37, delay is 1.137 possibly caused by: tmr-I2C_SUSV_Poll_GPIO(SUSV) tmr-GPIO4_DeviceUpdateLoop(OG2_EDV_R_EDVVT) tmr-CODE(0x3c9ad18)(GetStatus) tmr-CODE(0x22605f0)(SIGNALduino_KeepAlive) tmr-FHEM2FHEM_keepalive(F2F_Rasp03) tmr-CODE(0x22605f0)(SIGNALduino_KeepAlive)
2022.07.12 10:13:40.823 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:13:46.105 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:13:51.378 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:13:56.655 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:01.893 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:07.240 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:12.477 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:17.760 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:22.997 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:28.279 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:33.770 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:35.864 3: [Freezemon] myFreezemon: possible freeze starting at 10:14:34, delay is 1.864 possibly caused by: tmr-HMinfo_init(N/A) tmr-I2C_SUSV_Poll_GPIO(SUSV)
2022.07.12 10:14:37.666 3: [Freezemon] myFreezemon: possible freeze starting at 10:14:36, delay is 1.664 possibly caused by: tmr-I2C_SUSV_Poll(SUSV) tmr-FW_closeInactiveClients(N/A) tmr-SYSMON_Update(sysmon) tmr-JSONMETER_GetUpdate(EnergieGas) tmr-JSONMETER_GetUpdate(EnergieAB) tmr-JSONMETER_GetUpdate(EnergieEG) tmr-JSONMETER_GetUpdate(EnergieOG1) tmr-JSONMETER_GetUpdate(EnergieOG2) tmr-GPIO4_DeviceUpdateLoop(KG_RT) tmr-FHEM::Astro::Update(myAstro)
2022.07.12 10:14:39.807 3: [Freezemon] myFreezemon: possible freeze starting at 10:14:38, delay is 1.806 possibly caused by: tmr-GPIO4_DeviceUpdateLoop(OG2_EDV_R_RT) tmr-I2C_SUSV_Poll_GPIO(SUSV) tmr-GPIO4_DeviceUpdateLoop(OG2_EDV_R_EDVVT) tmr-CODE(0x3c9ad18)(GetStatus) tmr-CODE(0x22605f0)(SIGNALduino_KeepAlive) tmr-CODE(0x22605f0)(SIGNALduino_KeepAlive)
2022.07.12 10:14:40.137 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:45.373 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:50.727 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:14:55.973 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:01.247 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:06.517 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:11.792 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:13.889 3: CUL_HM set OG2_BU2_HZG_TC sysTime noArg
2022.07.12 10:15:13.936 3: CUL_HM set EG_KU_HZG_TC sysTime noArg
2022.07.12 10:15:17.050 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:22.286 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:27.522 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:32.760 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:38.587 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:43.421 3: [Freezemon] myFreezemon: possible freeze starting at 10:15:40, delay is 3.42 possibly caused by: tmr-GPIO4_DeviceUpdateLoop(OG2_EDV_R_EDVVT) tmr-CODE(0x3c9ad18)(GetStatus) tmr-CODE(0x22605f0)(SIGNALduino_KeepAlive) tmr-CODE(0x22605f0)(SIGNALduino_KeepAlive) tmr-HMUARTLGW_CheckCredits(HmUART_OG1) tmr-HMUARTLGW_CheckCredits(HmUART_Test) tmr-HMUARTLGW_CheckCredits(HmUART_AB_GTO)
2022.07.12 10:15:43.988 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:49.246 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:54.503 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:15:59.771 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:16:05.991 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:16:06.087 3: [Freezemon] myFreezemon: possible freeze starting at 10:16:05, delay is 1.086 possibly caused by: tmr-HMinfo_init(N/A)
2022.07.12 10:16:09.646 3: [Freezemon] myFreezemon: possible freeze starting at 10:16:08, delay is 1.645 possibly caused by: tmr-I2C_SUSV_Poll_GPIO(SUSV)
2022.07.12 10:16:11.269 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:16:16.751 3: HMinfo HMinfo get:loadConfig :
2022.07.12 10:16:21.987 3: HMinfo HMinfo get:loadConfig :Zitatzuerst prefered io setzen, würde ich sagen.
Ich habe die Änderungen betreffend der prefered IOs schon eine Weile durchgeführt.
list DEF=...... i:IODev a:IOgrpAB_BKTR_BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_EG,HmUART_AB_FR
AB_FR_AAM IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_FR_AD IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_FR_BL_RGB IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_FR_RM IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG1,HmUART_OG2
AB_GAO_SSPPWT_FSI IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_GO_RM IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_GO_RM_TEAMDEV IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_MB_PS IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_FR,HmUART_OG1
AB_SA_NT IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
AB_SG_12BW IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
AB_SG_34BW IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_OG2
AB_SG_56BW IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_OG2
AB_SG_BLGOBWS IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
AB_SG_BLWSBWS IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG1,HmUART_OG2
AB_VG_BW IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG2,HmUART_EG,HmUART_OG1
AB_WST_RS IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
EG_BA_HZG_RT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
EG_BA_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
EG_KUE_AAM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_KUE_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_FR,HmUART_OG2
EG_KU_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_EG,HmUART_OG2
EG_KU_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_EG
EG_RM_TEAMDEV IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1
EG_SL_HZG_RT IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
EG_SL_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
EG_SL_RM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_GTO
EG_STH_AAM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_STH_HZG_RT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_STH_T1_FB IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_STH_T1_VGT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_STH_ZS_T1VGF IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_VR_RM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1
EG_WC_HZG_RT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_WC_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_WI_HZG_RT IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_WI_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
EG_WR_RM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1
EG_WZ_HZG_RT IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_EG
EG_WZ_HZG_TC IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
EG_WZ_RM IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1,HmUART_OG2
HM_6A8CB3 IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG,HmUART_OG1,HmUART_OG2,HmUART_Test
HM_6A9533 IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG,HmUART_OG1,HmUART_OG2,HmUART_Test
OG1_BA_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_EG
OG1_KI_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2
OG1_KI_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2
OG1_KI_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2,HmUART_AB_FR
OG1_KUE_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR,HmUART_EG
OG1_KU_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_KU_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
OG1_KU_OA_FS1I IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_KU_OA_FS2I IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_KU_WA_OAFGO IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
OG1_RM_TEAMDEV IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_OG2
OG1_SL_BLO IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_SL_BLO_RLL IODev HmUART_OG1
OG1_SL_FB1 IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_SL_FB2 IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_SL_FB3 IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_SL_HZG_RT IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1,HmUART_OG2
OG1_SL_HZG_TC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_GTO
OG1_SL_RM IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_GTO
OG1_STH_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_EG
OG1_STH_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_EG,HmUART_AB_FR
OG1_STH_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_EG
OG1_VR_AAM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2,HmUART_AB_FR
OG1_VR_RM IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2
OG1_WC_HZG_RT IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_WC_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
OG1_WZ_BL_RGB IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_AB_GTO
OG1_WZ_BL_VIO IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_GTO
OG1_WZ_HZG_RT IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_OG2
OG1_WZ_HZG_TC IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_OG2
OG1_WZ_RM IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG2,HmUART_OG1,HmUART_EG
OG2_B1_KG IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_BU1_AAM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
OG2_BU1_HZG_RT IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_BU1_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_BU1_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_BU2_HZG_RT1 IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_GTO
OG2_BU2_HZG_RT2 IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG2,HmUART_OG1
OG2_BU2_HZG_TC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_GTO
OG2_BU2_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_DB_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_EDV_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_FR,HmUART_OG1
OG2_RM_TEAMDEV IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO,HmUART_AB_FR
OG2_VR_RM IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
OG2_VR_STI IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
OG2_WC_HZG_RT IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
OG2_WC_HZG_TC IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
PCR800 IODev sduino_ab
STH_RM_TEAMDEV IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_OG2
UESF1_AB_FR IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
UESF1_AB_GAO IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
UESF1_EG_BA IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
UESF1_EG_KUE IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
UESF1_EG_SL IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
UESF1_EG_STH IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
UESF1_EG_WC IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_FR,HmUART_OG1
UESF1_EG_WI IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1
UESF1_EG_WZ IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
UESF1_OG1_BA IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_EG
UESF1_OG1_KI IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_EG,HmUART_OG2
UESF1_OG1_KUE IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
UESF1_OG1_SL IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_EG
UESF1_OG1_WC IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
UESF1_OG1_WZ IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_OG2
UESF1_OG2_BUE1_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF1_OG2_BUE2_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF1_OG2_BUE2_W IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG2,HmUART_OG1
UESF1_OG2_DB IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
UESF1_OG2_DBN IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF2_AB_GAO IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
UESF2_EG_SL IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_GTO,HmUART_OG1
UESF2_EG_STH IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_FR
UESF2_EG_WZ IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
UESF2_OG1_SL IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_EG
UESF2_OG1_WZ IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_OG1,HmUART_OG2
UESF2_OG2_BUE1_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF2_OG2_BUE2_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF2_OG2_BUE2_W IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF2_OG2_DBN IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF3_OG1_STH IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_OG2
UESF3_OG2_BUE1_N IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF3_OG2_BUE2_W IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
UESF3_OG2_DBN IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_AB_GTO,HmUART_OG1
UESF4_OG1_STH IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
UESF5_OG2_STH IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_FR
UEST1_AB_FR IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
UEST1_AB_GAO IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
UEST1_AB_GTW IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_EG,HmUART_OG1
UEST1_AB_SA IODev HmUART_AB_FR
IOgrp VCCU:HmUART_AB_FR,HmUART_OG2,HmUART_OG1
UEST1_EG_BA IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_OG1,HmUART_AB_GTO
UEST1_EG_KUE IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_AB_FR,HmUART_EG
UEST1_EG_STH IODev HmUART_EG
IOgrp VCCU:HmUART_EG,HmUART_AB_FR,HmUART_OG1
UEST1_OG1_KUE IODev HmUART_OG1
IOgrp VCCU:HmUART_OG1,HmUART_OG2,HmUART_AB_FR
UEST1_OG2_EDV IODev HmUART_OG2
IOgrp VCCU:HmUART_OG2,HmUART_OG1,HmUART_AB_GTO
UEST2_AB_GAO IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
UEST2_AB_GAW IODev HmUART_AB_GTO
IOgrp VCCU:HmUART_AB_GTO,HmUART_AB_FR,HmUART_EG
VCCU IODev HmUART_AB_FR
IOgrp VCCU
WGR800 IODev sduino_ab
ok, jetzt ist der cmd "loadconfig" zu sehen.
dein problem ist wohl eine fehlende "config datei", in der die register- und peeringinfos der devices gespeichert werden können.
entweder du erstellst eine datei (eventuell "set saveConfig"; bin gerade unterwegs und nicht sicher), oder du cancelst die nutzung, indem du die 2 attribute autoArchive, autoLoadArchive löscht.
Ich kann es erwarten, bist du zu Hause bist.
Mich interessiert auch, wo diese Datei fehlt.
Bis dann.
Update: 2022.07.14
Eines was mir bei dem HMinfoTool aufgefallen ist, ist, das viele der 104 HomeMatic Geräte nicht aufgelistet sind. In der RSSI Aufstellung sind sie enthalten.
Ein Update Aufruf im HMinfo ändert nichts daran.
In der RSSI Auflistung sind Darstellungsfehler ersichtlich. Siehe Anhang.
In der HMinfoToolsübersicht wird nicht nur das Gerät aufgelistet, sondern bei manchen auch die einzelnen Kanäle.
Das ist aber nicht immer der Fall.
Eine Frage zur fehlenden Datei für autoArchive und autoLoadArchive.
Wo soll sich diese Datei befinden und wie heißt diese Datei?
Kann sich diese Datei auch an einem beliebigen Standort befinden?
Gelegentlich tauchen Fehlermeldungen auf.
LOG bei Neustart
2022.07.12 09:51:20.125 3: HMinfo HMinfo get:loadConfig :
2022.07.12 09:51:29.892 1: PERL WARNING: Use of uninitialized value $VALUE in sprintf at (eval 970) line 1.
2022.07.12 09:51:30.066 1: PERL WARNING: Use of uninitialized value $VALUE in sprintf at (eval 973) line 1.
FEHLERMELDUNG FHEMWEB
HMinfoTools.js line 919:
TypeError: devObj is undefined
hi chris.
configfile:diese datei existiert per default nicht.
wie bereits geschrieben, kann man sie mit "saveConfig" erstellen.
infos sind sehr verteilt zu finden und wie immer ist die commandref ein guter erster startpunkt.
aber auch im wiki gibt es hinweise:
https://wiki.fhem.de/wiki/HMinfo#Speichern_von_Konfigurationen (https://wiki.fhem.de/wiki/HMinfo#Speichern_von_Konfigurationen)
ZitatEine Frage zur fehlenden Datei für autoArchive und autoLoadArchive.
Wo soll sich diese Datei befinden und wie heißt diese Datei?
Kann sich diese Datei auch an einem beliebigen Standort befinden?
den default namen und pfad kann man zusätzlich mit attributen ändern.
also einfach mal im set menü von hminfo "saveConfig" auswählen und draufklicken.
hminfotools:ZitatIn der RSSI Auflistung sind Darstellungsfehler ersichtlich. Siehe Anhang.
kann ich nicht erkennen.
du meinst eventuell die unterschiedliche darstellung der 2 unterschiedlichen kommunikationsrichtungen?
in der spalte receive steht das device, das die rssi der jeweiligen zeile gemessen hat.
du hattest jedenfalls nicht die checkbox zum anzeigen aller devices gesetzt => deshalb zeigen zb nur devices mit fehlern die eingabemöglichkeit für das attr IOgrp.
ZitatIn der HMinfoToolsübersicht wird nicht nur das Gerät aufgelistet, sondern bei manchen auch die einzelnen Kanäle.
Das ist aber nicht immer der Fall.
wie geschrieben: per default (checkbox oben rechts nicht ausgewählt) =>
nur entities bei denen hminfo fehler meldet, werden angezeigt. mit ausgewählter checkbox werden
zusätzlich darunter auch alle hauptdevices ohne fehler angezeigt.
channel-entities ohne fehler sind nie zu sehen.
Zitat2022.07.12 09:51:20.125 3: HMinfo HMinfo get:loadConfig :
der cmd loadConfig wurde ausgeführt und hiermit protokolliert. du hast es mit attr autoLoadConfig ja so eingestellt.
ZitatHMinfoTools.js line 919:
TypeError: devObj is undefined
taucht das schon immer auf?
was steht dann in der javascript konsole?
poste anschliessend mal ein list von hminfo.
sonstiges:Zitat2022.07.12 09:51:29.892 1: PERL WARNING: Use of uninitialized value $VALUE in sprintf at (eval 970) line 1.
ich würde mal fhem.cfg nach "$VALUE sprintf" durchsuchen. vielleicht eine readingsgroup?