Objekt Motion / Nomotion zu 1 oder 0
-
@ChrisXY
Was hast du für einen Bewegungsmelder in FHEM?
Hast du kein Objekt state_boolean im ioBroker angelegt bekommen?
Gruß
LausiD -
@LausiD Hab den HM-SEN-MDIR-O und kein state_boolean habe noch einen 2. der gibt halt true/false aus daher hat der 2. HM-SEC-MDIR den Status auch nicht .. aber komisch das der HM-SEN-MDIR-O sowas nicht macht
-
@LausiD okay hier
{ "Arg":"motion_stall", "Results": [ { "Name":"motion_stall", "PossibleSets":"assignHmKey:noArg clear:readings,trigger,register,oldRegs,rssi,msgEvents,msgErrors,attack,all deviceRename fwUpdate getConfig:noArg getDevInfo:noArg getRegRaw peerBulk peerChan raw regBulk regSet reset:noArg sign:on,off unpair:noArg peerSmart:Rauchmelder_Team,TeamVirtuell_Stall,VCCU_Btn4,VCCU_disarm,VCCU_lampe_stall_unterstand,VCCU_lampe_stall_unterstand_reitplatz,heizung_badoben_WindowRec,heizung_badoben_remote,heizung_badunten_WindowRec,heizung_badunten_remote,heizung_buro_WindowRec,heizung_buro_remote,heizung_esszimmer_WindowRec,heizung_esszimmer_remote,heizung_milena_WindowRec,heizung_milena_remote,heizung_schlafzimmer_WindowRec,heizung_schlafzimmer_remote,heizung_wohnzimmervitrine_WindowRec,heizung_wohnzimmervitrine_remote,pumpe_regenwasser_Sw,strom_aquarium_Sw,strom_server_Sw,strom_zaun ", "PossibleAttrs":"alias comment:textField-long eventMap:textField-long group room suppressReading userReadings:textField-long verbose:0,1,2,3,4,5 do_not_notify:1,0 showtime:1,0 rawToReadable unit expert:0_defReg,1_allReg,2_defReg+raw,3_allReg+raw,4_off,8_templ+default,12_templOnly,251_anything param readOnly:0,1 actAutoTry:0_off,1_on aesCommReq:1,0 model ignore:1,0 dummy:1,0 IODev IOList IOgrp rssiLog:1,0 actCycle hmKey hmKey2 hmKey3 readingOnDead:multiple,noChange,state,periodValues,periodString,channels subType:AlarmControl,KFM100,THSensor,blindActuator,blindActuatorSol,dimmer,display,keyMatic,motionAndBtn,motionDetector,no,outputUnit,powerMeter,powerSensor,pushButton,remote,repeater,rgb,senBright,sensRain,sensor,singleButton,siren,smokeDetector,swi,switch,thermostat,threeStateSensor,timer,tipTronic,virtual,winMatic .mId serialNr firmware .stc .devInfo actStatus autoReadReg:0_off,1_restart,2_pon-restart,3_onChange,4_reqStatus,5_readMissing,8_stateOnly burstAccess:0_off,1_auto msgRepeat hmProtocolEvents:0_off,1_dump,2_dumpFull,3_dumpTrigger aesKey:5,4,3,2,1,0 modelForce:ACTIONDETECTOR,ACTIONDETECTOR,ASH550,ASH550I,CCU-FHEM,CMM,DORMA_ATENT,DORMA_BRC-H,DORMA_RC-H,HM-CC-RT-DN,HM-CC-RT-DN-BOM,HM-CC-SCD,HM-CC-TC,HM-CC-VD,HM-DIS-EP-WM55,HM-DIS-TD-T,HM-DIS-WM55,HM-DW-WM,HM-ES-PMSW1-DR,HM-ES-PMSW1-PL,HM-ES-PMSW1-PL-DN-R1,HM-ES-PMSW1-PL-DN-R2,HM-ES-PMSW1-PL-DN-R3,HM-ES-PMSW1-PL-DN-R4,HM-ES-PMSW1-PL-DN-R5,HM-ES-PMSW1-SM,HM-ES-TX-WM,HM-HM-LC-DW-WM,HM-LC-AO-SM,HM-LC-BL1-FM,HM-LC-BL1-FM-2,HM-LC-BL1-PB-FM,HM-LC-BL1-SM,HM-LC-BL1-SM-2,HM-LC-BL1PBU-FM,HM-LC-DDC1-PCB,HM-LC-DIM1L-CV,HM-LC-DIM1L-CV-2,HM-LC-DIM1L-CV-644,HM-LC-DIM1L-PL,HM-LC-DIM1L-PL-2,HM-LC-DIM1L-PL-3,HM-LC-DIM1L-PL-644,HM-LC-DIM1PWM-CV,HM-LC-DIM1PWM-CV-2,HM-LC-DIM1T-CV,HM-LC-DIM1T-CV-2,HM-LC-DIM1T-CV-644,HM-LC-DIM1T-DR,HM-LC-DIM1T-FM,HM-LC-DIM1T-FM-2,HM-LC-DIM1T-FM-644,HM-LC-DIM1T-FM-LF,HM-LC-DIM1T-PL,HM-LC-DIM1T-PL-2,HM-LC-DIM1T-PL-3,HM-LC-DIM1T-PL-644,HM-LC-DIM1TPBU-FM,HM-LC-DIM1TPBU-FM-2,HM-LC-DIM2L-CV,HM-LC-DIM2L-SM,HM-LC-DIM2L-SM-2,HM-LC-DIM2L-SM-644,HM-LC-DIM2T-SM,HM-LC-DIM2T-SM,HM-LC-DIM2T-SM-2,HM-LC-JA1PBU-FM,HM-LC-RGBW-WM,HM-LC-SW1-BA-PCB,HM-LC-SW1-DR,HM-LC-SW1-FM,HM-LC-SW1-FM-2,HM-LC-SW1-PB-FM,HM-LC-SW1-PCB,HM-LC-SW1-PL,HM-LC-SW1-PL-3,HM-LC-SW1-PL-CT-R1,HM-LC-SW1-PL-CT-R2,HM-LC-SW1-PL-CT-R3,HM-LC-SW1-PL-CT-R4,HM-LC-SW1-PL-CT-R5,HM-LC-SW1-PL-DN-R1,HM-LC-SW1-PL-DN-R2,HM-LC-SW1-PL-DN-R3,HM-LC-SW1-PL-DN-R4,HM-LC-SW1-PL-DN-R5,HM-LC-SW1-PL-OM54,HM-LC-SW1-PL2,HM-LC-SW1-SM,HM-LC-SW1-SM-2,HM-LC-SW1-SM-ATMEGA168,HM-LC-SW1PBU-FM,HM-LC-SW2-DR,HM-LC-SW2-DR-2,HM-LC-SW2-FM,HM-LC-SW2-FM-2,HM-LC-SW2-PB-FM,HM-LC-SW2-SM,HM-LC-SW2PBU-FM,HM-LC-SW4-BA-PCB,HM-LC-SW4-DR,HM-LC-SW4-DR-2,HM-LC-SW4-PCB,HM-LC-SW4-PCB-2,HM-LC-SW4-SM,HM-LC-SW4-SM-2,HM-LC-SW4-SM-ATMEGA168,HM-LC-SW4-WM,HM-LC-SW4-WM-2,HM-MOD-EM-8,HM-MOD-EM-8BIT,HM-MOD-RE-8,HM-OU-CF-PL,HM-OU-CFM-PL,HM-OU-CFM-TW,HM-OU-CM-PCB,HM-OU-LED16,HM-PB-2-FM,HM-PB-2-WM,HM-PB-2-WM55,HM-PB-2-WM55-2,HM-PB-4-WM,HM-PB-4DIS-WM,HM-PB-4DIS-WM-2,HM-PB-6-WM55,HM-PBI-4-FM,HM-RC-12,HM-RC-12-B,HM-RC-12-SW,HM-RC-19,HM-RC-19-B,HM-RC-19-SW,HM-RC-2-PBU-FM,HM-RC-4,HM-RC-4-2,HM-RC-4-3,HM-RC-4-3-D,HM-RC-4-B,HM-RC-8,HM-RC-DIS-H-X-EU,HM-RC-KEY3,HM-RC-KEY3-B,HM-RC-KEY4-2,HM-RC-KEY4-3,HM-RC-P1,HM-RC-SEC3,HM-RC-SEC3-B,HM-RC-SEC4-2,HM-RC-SEC4-3,HM-SCI-3-FM,HM-SEC-CEN,HM-SEC-KEY,HM-SEC-KEY-O,HM-SEC-KEY-S,HM-SEC-MDIR,HM-SEC-MDIR-2,HM-SEC-MDIR-3,HM-SEC-RHS,HM-SEC-RHS-2,HM-SEC-SC,HM-SEC-SC-2,HM-SEC-SCO,HM-SEC-SD,HM-SEC-SD-2,HM-SEC-SFA-SM,HM-SEC-SIR-WM,HM-SEC-TIS,HM-SEC-WDS,HM-SEC-WDS-2,HM-SEC-WIN,HM-SEN-DB-PCB,HM-SEN-EP,HM-SEN-LI-O,HM-SEN-MDIR-O,HM-SEN-MDIR-O-2,HM-SEN-MDIR-O-3,HM-SEN-MDIR-SM,HM-SEN-MDIR-WM55,HM-SEN-RD-O,HM-SEN-WA-OD,HM-SWI-3-FM,HM-SYS-SRP-PL,HM-TC-IT-WM-W-EU,HM-WDC7000,HM-WDS10-TH-O,HM-WDS100-C6-O,HM-WDS100-C6-O-2,HM-WDS20-TH-O,HM-WDS30-OT2-SM,HM-WDS30-OT2-SM-2,HM-WDS30-T-O,HM-WDS40-TH-I,HM-WDS40-TH-I-2,HM-WS550,HM-WS550LCB,HM-WS550LCW,HM-WS550TECH,IS-WDS-TH-OD-S-R3,KFM-DISPLAY,KFM-SENSOR,KS550,KS550LC,KS550TECH,KS888,OLIGO-SMART-IQ-HM,PS-SWITCH,PS-TH-SENS,ROTO_ZEL-STG-RM-DWT-10,ROTO_ZEL-STG-RM-FDK,ROTO_ZEL-STG-RM-FEP-230V,ROTO_ZEL-STG-RM-FFK,ROTO_ZEL-STG-RM-FSA,ROTO_ZEL-STG-RM-FSS-UP3,ROTO_ZEL-STG-RM-FST-UP4,ROTO_ZEL-STG-RM-FWT,ROTO_ZEL-STG-RM-FZS,ROTO_ZEL-STG-RM-FZS-2,ROTO_ZEL-STG-RM-HS-4,ROTO_ZEL-STG-RM-WT-2,S550IA,SCHUECO_263-130,SCHUECO_263-131,SCHUECO_263-132,SCHUECO_263-133,SCHUECO_263-134,SCHUECO_263-135,SCHUECO_263-144,SCHUECO_263-145,SCHUECO_263-146,SCHUECO_263-147,SCHUECO_263-155,SCHUECO_263-157,SCHUECO_263-158,SCHUECO_263-160,SCHUECO_263-162,SCHUECO_263-167,SCHUECO_263-XXX,SENSOTIMER-ST-6,VIRTUAL,WDF-SOLAR,WS888 repPeers peerIDs tempListTmpl:none,defaultWeekplan, levelRange levelMap cyclicMsgOffset event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading DbLogExclude DbLogInclude alarmDevice:Actor,Sensor alarmSettings cmdIcon devStateIcon:textField-long devStateStyle icon msgContactAudio msgContactLight msgContactMail msgContactPush msgContactScreen msgParams msgPriority msgRecipient msgRecipientAudio msgRecipientLight msgRecipientMail msgRecipientPush msgRecipientScreen msgRecipientText msgTitle msgTitleShrt msgType:text,push,mail,screen,light,audio,queue sortby webCmd webCmdLabel:textField-long widgetOverride userattr", "Internals": { ".triggerUsed": "0", "DEF": "461309", "FUUID": "5cce995c-f33f-09a2-4026-a0e84556b11b8ebe", "HMLANGW_MSGCNT": "168", "HMLANGW_RAWMSG": "050000830084104613090000000601C400", "HMLANGW_RSSI": "-131", "HMLANGW_TIME": "2019-06-05 16:33:51", "HMLAN_MSGCNT": "43", "HMLAN_RAWMSG": "E461309,0000,03E48BA9,FF,FFAC,0084104613090000000601C400", "HMLAN_RSSI": "-84", "HMLAN_TIME": "2019-06-05 16:33:51", "LASTInputDev": "HMLAN", "MSGCNT": "211", "NAME": "motion_stall", "NOTIFYDEV": "global", "NR": "839", "NTFY_ORDER": "50-motion_stall", "STATE": "noMotion", "TYPE": "CUL_HM", "chanNo": "01", "lastMsg": "No:00 - t:10 s:461309 d:000000 0601C400", "protCmdPend": "4 CMDs_pending", "protLastRcv": "2019-06-05 16:33:51", "protRcv": "178 last_at:2019-06-05 16:33:51", "protRcvB": "2 last_at:2019-06-04 05:09:12", "protState": "CMDs_pending", "rssi_at_HMLAN": "cnt:43 min:-103 max:-83 avg:-89.62 lst:-84 ", "rssi_at_HMLANGW": "cnt:166 min:-134 max:-37 avg:-129.78 lst:-131 ", "rssi_at_rpt_HMLANGW": "cnt:2 min:-133 max:-63 avg:-98 lst:-63 ", "rssi_broadcast": "cnt:1 min:-189 max:-189 avg:-189 lst:-189 " }, "Readings": { ".D-devInfo": { "Value":"110100", "Time":"2019-05-06 09:13:34" }, ".D-stc": { "Value":"81", "Time":"2019-05-06 09:13:34" }, ".protLastRcv": { "Value":"2019-06-05 16:33:51", "Time":"2019-06-05 16:33:51" }, "Activity": { "Value":"alive", "Time":"2019-06-01 16:45:59" }, "D-firmware": { "Value":"1.6", "Time":"2019-05-06 09:13:34" }, "D-serialNr": { "Value":"NEQ0118339", "Time":"2019-05-06 09:13:34" }, "battery": { "Value":"ok", "Time":"2019-06-05 16:33:51" }, "brightness": { "Value":"196", "Time":"2019-06-05 16:33:51" }, "cover": { "Value":"closed", "Time":"2019-06-05 16:33:51" }, "motion": { "Value":"off", "Time":"2019-06-05 16:37:39" }, "motionCount": { "Value":"1_next:240s", "Time":"2019-06-05 16:33:37" }, "motionDuration": { "Value":"296", "Time":"2019-06-05 16:37:39" }, "powerOn": { "Value":"2019-06-05 16:33:04", "Time":"2019-06-05 16:33:04" }, "recentStateType": { "Value":"info", "Time":"2019-06-05 16:33:51" }, "state": { "Value":"noMotion", "Time":"2019-06-05 16:37:39" }, "trigDst_broadcast": { "Value":"noConfig", "Time":"2019-05-23 17:17:26" }, "trigger_cnt": { "Value":"1", "Time":"2019-06-05 16:33:37" } }, "Attributes": { ".mId": "005D", "DbLogExclude": ".*", "DbLogInclude": "trigger_cnt,brightness,motionDuration", "IODev": "HMLAN", "actCycle": "024:00", "actStatus": "alive", "alias": "motion_stall", "autoReadReg": "4_reqStatus", "expert": "2_raw", "firmware": "1.6", "model": "HM-SEN-MDIR-O", "room": "CUL_HM,ioBroker", "serialNr": "NEQ0118339", "subType": "motionDetector" } } ], "totalResultsReturned":1 } -
@ChrisXY
Danke..kannst FHEM Adapter über github aktualisieren
Nach Neustart sollte der Bewegungsmelder im ioBroker ein Objekt state_boolean mit true/false haben.
Gruß
LausiD -
@ChrisXY
Danke..kannst FHEM Adapter über github aktualisieren
Nach Neustart sollte der Bewegungsmelder im ioBroker ein Objekt state_boolean mit true/false haben.
Gruß
LausiDhost.iobroker 2019-06-06 16:04:16.687 error instance system.adapter.fhem.0 terminated with code 1 () Caught 2019-06-06 16:04:16.687 error by controller[0]: at bootstrap_node.js:625:3 Caught 2019-06-06 16:04:16.687 error by controller[0]: at startup (bootstrap_node.js:204:16) Caught 2019-06-06 16:04:16.687 error by controller[0]: at Function.Module.runMain (module.js:694:10) Caught 2019-06-06 16:04:16.687 error by controller[0]: at Function.Module._load (module.js:498:3) Caught 2019-06-06 16:04:16.686 error by controller[0]: at tryModuleLoad (module.js:506:12) Caught 2019-06-06 16:04:16.686 error by controller[0]: at Module.load (module.js:566:32) Caught 2019-06-06 16:04:16.686 error by controller[0]: at Object.Module._extensions..js (module.js:664:10) Caught 2019-06-06 16:04:16.686 error by controller[0]: at Module._compile (module.js:617:28) Caught 2019-06-06 16:04:16.686 error by controller[0]: at Object.runInThisContext (vm.js:139:10) Caught 2019-06-06 16:04:16.686 error by controller[0]: at createScript (vm.js:80:10) Caught 2019-06-06 16:04:16.686 error by controller[0]: SyntaxError: Invalid or unexpected token Caught 2019-06-06 16:04:16.686 error by controller[0]: ^^^^^^^^^^^ Caught 2019-06-06 16:04:16.686 error by controller[0]: if (valOrg === 'motion' || valOrg === 'nomotion' || valOrg === 'noMotion' || valOrg === "Motion') { Caught 2019-06-06 16:04:16.686 error by controller[0]: /opt/iobroker/node_modules/iobroker.fhem/main.js:1725EDIT: oder auch FHEM selbst neu tarten ? Hab nur den Adapter
-
host.iobroker 2019-06-06 16:04:16.687 error instance system.adapter.fhem.0 terminated with code 1 () Caught 2019-06-06 16:04:16.687 error by controller[0]: at bootstrap_node.js:625:3 Caught 2019-06-06 16:04:16.687 error by controller[0]: at startup (bootstrap_node.js:204:16) Caught 2019-06-06 16:04:16.687 error by controller[0]: at Function.Module.runMain (module.js:694:10) Caught 2019-06-06 16:04:16.687 error by controller[0]: at Function.Module._load (module.js:498:3) Caught 2019-06-06 16:04:16.686 error by controller[0]: at tryModuleLoad (module.js:506:12) Caught 2019-06-06 16:04:16.686 error by controller[0]: at Module.load (module.js:566:32) Caught 2019-06-06 16:04:16.686 error by controller[0]: at Object.Module._extensions..js (module.js:664:10) Caught 2019-06-06 16:04:16.686 error by controller[0]: at Module._compile (module.js:617:28) Caught 2019-06-06 16:04:16.686 error by controller[0]: at Object.runInThisContext (vm.js:139:10) Caught 2019-06-06 16:04:16.686 error by controller[0]: at createScript (vm.js:80:10) Caught 2019-06-06 16:04:16.686 error by controller[0]: SyntaxError: Invalid or unexpected token Caught 2019-06-06 16:04:16.686 error by controller[0]: ^^^^^^^^^^^ Caught 2019-06-06 16:04:16.686 error by controller[0]: if (valOrg === 'motion' || valOrg === 'nomotion' || valOrg === 'noMotion' || valOrg === "Motion') { Caught 2019-06-06 16:04:16.686 error by controller[0]: /opt/iobroker/node_modules/iobroker.fhem/main.js:1725EDIT: oder auch FHEM selbst neu tarten ? Hab nur den Adapter
-
hmm habs nochmal von github geladen nu is immer noch 1.2.1 drauf guthub gibt es aber nur 1.2.0
Edit : leider taucht auch ein state_boolean auf.. komisch
Will das fhem auch nicht löschen hab angst da was zu verlieren hab da Logging für vieles Aktiv. -
@ChrisXY
Sorry, Änderung nebenher ging schief.
Aller guten Dinge sind drei :-)
Kannst bitte nochmal von github aktualisieren....
Korrekt, die Version ist 1.2.1 und ändert sich auch nicht.
Beim Start FHEM Adapter werden folgende Zeilen ins Log geschrieben:
fhem.1 2019-06-06 20:16:08.526 info STEP 01 ===== buildDate 06.06.19b - check objects fhem.1
fhem.1 2019-06-06 20:16:08.460 info starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.fhem, node: v8.15.1Und jetzt sollte nach Neustart auch endgültig ein Objekt state_Boolean mit dem Wert true/false erscheinen :-)
Gruß
LausiD -
@ChrisXY
Sorry, Änderung nebenher ging schief.
Aller guten Dinge sind drei :-)
Kannst bitte nochmal von github aktualisieren....
Korrekt, die Version ist 1.2.1 und ändert sich auch nicht.
Beim Start FHEM Adapter werden folgende Zeilen ins Log geschrieben:
fhem.1 2019-06-06 20:16:08.526 info STEP 01 ===== buildDate 06.06.19b - check objects fhem.1
fhem.1 2019-06-06 20:16:08.460 info starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.fhem, node: v8.15.1Und jetzt sollte nach Neustart auch endgültig ein Objekt state_Boolean mit dem Wert true/false erscheinen :-)
Gruß
LausiD
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
320
Online32.8k
Benutzer82.7k
Themen1.3m
Beiträge