Hallo zusammen,
mir ist heute aufgefallen, dass sich die Bewegungserkennung meiner HmIP-SMI zwar via HMCCU abschalten, aber nicht mehr einschalten.
Wie lange das schon der Fall ist, weiß ich nicht.
Sprich:
set mySMI detection inactive -> funktioniert
set mySMI detection active -> tut nichts
Direkt auf der CCU kann ich die Detection problemlos ein/ausschalten.
Auch vom ioBroker aus geht beides problemlos, so dass ich die CCU und die Schnittstelle als Fehlerquelle ausschließen kann.
Wer kann helfen? Danke.
get config liefert:
Device 00091A49A94572
Channel 0 [MASTER]
ARR_TIMEOUT = 10
CYCLIC_BIDI_INFO_MSG_DISCARD_FACTOR = 0
CYCLIC_BIDI_INFO_MSG_DISCARD_VALUE = 0
CYCLIC_INFO_MSG = 1
CYCLIC_INFO_MSG_DIS = 1
CYCLIC_INFO_MSG_DIS_UNCHANGED = 20
CYCLIC_INFO_MSG_OVERDUE_THRESHOLD = 2
DISABLE_MSG_TO_AC = false
DUTYCYCLE_LIMIT = 180
ENABLE_ROUTING = true
LOCAL_RESET_DISABLED = false
LOW_BAT_LIMIT = 2.2
SUPPORTING_WIRED_OPERATION_MODE = true
Channel 1 [MASTER]
ALARM_MODE_TYPE = 0
ALARM_MODE_ZONE_1 = 0
ALARM_MODE_ZONE_2 = 0
ALARM_MODE_ZONE_3 = 0
ALARM_MODE_ZONE_4 = 0
ALARM_MODE_ZONE_5 = 0
ALARM_MODE_ZONE_6 = 0
ALARM_MODE_ZONE_7 = 0
BRIGHTNESS_FILTER = 7
CAPTURE_WITHIN_INTERVAL = true
COND_TX_THRESHOLD_LO = 1000
EVENT_FILTER_NUMBER = 1
EVENT_FILTER_PERIOD = 1.0
LED_DISABLE_CHANNELSTATE = true
MIN_INTERVAL = 0
MOTION_ACTIVE_TIME = 0
PIR_OPERATION_MODE = PIR_OPERATION_MODE_NORMAL
Channel 2 [MASTER]
BLOCKING_PERIOD_UNIT = 100MS
BLOCKING_PERIOD_VALUE = 30
deviceInfo:
DEV mySMI 00091A49A94572 interface=HmIP-RF type=HmIP-SMI
CHN 00091A49A94572:0 mySMI:0
0.CONFIG_PENDING = false {b} [RE]
0.DUTY_CYCLE = false {b} [RE]
0.ERROR_CODE = 0 {n} [RE]
0.INSTALL_TEST = true {b} [RW]
0.LOW_BAT = false {b} [RE]
0.OPERATING_VOLTAGE = 2.600000 {f} [RE]
0.OPERATING_VOLTAGE_STATUS = 0 {i} [RE]
0.RSSI_DEVICE = 197 {n} [RE]
0.RSSI_PEER = 223 {n} [RE]
0.SABOTAGE = false {b} [RE]
0.UNREACH = false {b} [RE]
0.UPDATE_PENDING = false {b} [RE]
CHN 00091A49A94572:1 mySMI:1
1.CURRENT_ILLUMINATION = 50.330000 {f} [RE]
1.CURRENT_ILLUMINATION_STATUS = 0 {i} [RE]
1.ILLUMINATION = 25.860000 {f} [RE]
1.ILLUMINATION_STATUS = 0 {i} [RE]
1.MOTION = false {b} [RE]
1.MOTION_DETECTION_ACTIVE = true {b} [RWE]
1.RESET_MOTION = {b} [W]
1.ON_TIME = {f} [W]
Device detection:
StateDatapoint = 1.MOTION [MOTIONDETECTOR_TRANSCEIVER]
ControlDatapoint = 1.MOTION_DETECTION_ACTIVE [MOTIONDETECTOR_TRANSCEIVER]
Recommended module for device definition: HMCCUCHN
Current state datapoint = 1.MOTION
Current control datapoint = 1.MOTION_DETECTION_ACTIVE
Device description
Device 00091A49A94572 mySMI [HmIP-SMI]
AES_ACTIVE: 1
AVAILABLE_FIRMWARE: 3.2.48
CHILDREN: 00091A49A94572:0,00091A49A94572:1,00091A49A94572:2,00091A49A94572:3
DIRECTION: NONE
FIRMWARE: 3.2.48
FIRMWARE_UPDATE_STATE: UP_TO_DATE
FLAGS: Visible
PARAMSETS: MASTER,SERVICE
RF_ADDRESS: 7350398
ROAMING: 0
RX_MODE: ALWAYS,LAZY_CONFIG,BURST
SUBTYPE: SMI
UPDATABLE: 1
Channel 00091A49A94572:0 mySMI:0 [MAINTENANCE]
AES_ACTIVE: 1
DIRECTION: NONE
FLAGS: Visible
PARAMSETS: MASTER,VALUES,SERVICE
PARENT: 00091A49A94572
PARENT_TYPE: HmIP-SMI
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00091A49A94572:1 mySMI:1 [MOTIONDETECTOR_TRANSCEIVER] known
AES_ACTIVE: 1
DIRECTION: SENDER
FLAGS: Visible
LINK_SOURCE_ROLES: CONDITIONAL_SWITCH
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00091A49A94572
PARENT_TYPE: HmIP-SMI
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00091A49A94572:2 mySMI:2 [STATE_RESET_RECEIVER]
AES_ACTIVE: 1
DIRECTION: RECEIVER
FLAGS: Visible
LINK_TARGET_ROLES: REMOTE_CONTROL,SWITCH,CONDITIONAL_SWITCH
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 00091A49A94572
PARENT_TYPE: HmIP-SMI
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 00091A49A94572:3 HmIP-SMI 00091A49A94572:3 [ALARM_COND_SWITCH_TRANSMITTER]
AES_ACTIVE: 1
DIRECTION: NONE
FLAGS:
PARAMSETS: MASTER,VALUES,SERVICE
PARENT: 00091A49A94572
PARENT_TYPE: HmIP-SMI
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Defaults
Support for role MOTIONDETECTOR_TRANSCEIVER of device type HmIP-SMI is built in.
Hallo zusammen,
das kann ich leider bestätigen. Ausschalten über FHEM geht. EInschalten leider nein. Ich nutze die aktuelleste Version von HMCCU5. Das Ein-/Ausschalten über piVCCU3 ist problemlos möglich.
Viele Grüße
Jürgen
ein list vom Device wäre hilfreich. Hatte auch so einen Bewegungsmelder, ist aber leider defekt (von der Decke gefallen :'( ).
Hallo zap,
anbei die gewünschte INfo:
Internals:
DEF 000918A9952DE7:1
FUUID 652e9995-f33f-a57c-48b7-14ece4359ea76ec8
IODev HMCCU3
NAME HmIP_SMI_000918A9952DE7
NR 160
STATE noMotion
TYPE HMCCUCHN
ccuaddr 000918A9952DE7:1
ccudevstate active
ccuif HmIP-RF
ccuname HmIP-SMI 000918A9952DE7:1
ccurolectrl MOTIONDETECTOR_TRANSCEIVER
ccurolestate MOTIONDETECTOR_TRANSCEIVER
ccusubtype SMI
ccutype HmIP-SMI
chntype ?
eventCount 405
firmware 3.2.48
readonly no
OLDREADINGS:
READINGS:
2024-02-25 13:05:48 CURRENT_ILLUMINATION 0.1
2024-02-25 13:05:48 CURRENT_ILLUMINATION_STATUS NORMAL
2024-02-25 14:30:57 ILLUMINATION 0.0
2024-02-25 14:30:57 ILLUMINATION_STATUS NORMAL
2024-02-25 10:44:44 LastMove 25.02.2024 - 10:44:29
2024-02-25 14:30:57 MOTION noMotion
2024-02-25 14:30:57 MOTION_DETECTION_ACTIVE active
2024-02-25 10:44:44 PRESS_SHORT 1
2024-02-25 14:30:57 activity alive
2024-02-25 14:30:57 battery ok
2024-02-25 14:30:57 brightness 0.0
2024-02-25 14:30:57 control active
2024-02-25 14:30:57 detection active
2024-02-25 14:30:57 devstate ok
2024-02-25 14:30:57 hmstate noMotion
2024-02-25 14:30:57 motion noMotion
2024-02-25 14:30:57 rssidevice -68
2024-02-25 13:05:48 rssipeer -69
2024-02-25 14:30:57 sabotage false
2024-02-25 14:30:57 state noMotion
2024-02-25 14:30:57 voltage 2.5
hmccu:
channels 1
detect 0
devspec 000918A9952DE7:1
nodefaults 1
role 1:MOTIONDETECTOR_TRANSCEIVER
setDefaults 0
cmdlist:
get
set reset:noArg detection:inactive,active
control:
chn 1
dpt MOTION_DETECTION_ACTIVE
dp:
0.ARR_TIMEOUT:
MASTER:
NVAL 10
SVAL 10
VAL 10
VALUES:
0.CONFIG_PENDING:
VALUES:
NVAL 0
ONVAL 1
OSVAL true
OVAL 1
SVAL false
VAL 0
0.CYCLIC_BIDI_INFO_MSG_DISCARD_FACTOR:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
0.CYCLIC_BIDI_INFO_MSG_DISCARD_VALUE:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
0.CYCLIC_INFO_MSG:
MASTER:
NVAL 1
SVAL 1
VAL 1
VALUES:
0.CYCLIC_INFO_MSG_DIS:
MASTER:
NVAL 1
SVAL 1
VAL 1
VALUES:
0.CYCLIC_INFO_MSG_DIS_UNCHANGED:
MASTER:
NVAL 20
SVAL 20
VAL 20
VALUES:
0.CYCLIC_INFO_MSG_OVERDUE_THRESHOLD:
MASTER:
NVAL 2
SVAL 2
VAL 2
VALUES:
0.DISABLE_MSG_TO_AC:
MASTER:
NVAL 0
SVAL false
VAL 0
VALUES:
0.DUTYCYCLE_LIMIT:
MASTER:
NVAL 180
SVAL 180
VAL 180
VALUES:
0.DUTY_CYCLE:
VALUES:
NVAL 0
SVAL false
VAL 0
0.ENABLE_ROUTING:
MASTER:
NVAL 1
SVAL true
VAL 1
VALUES:
0.ERROR_CODE:
VALUES:
NVAL 0
SVAL 0
VAL 0
0.INSTALL_TEST:
VALUES:
NVAL 1
SVAL true
VAL 1
0.LOCAL_RESET_DISABLED:
MASTER:
NVAL 0
SVAL false
VAL 0
VALUES:
0.LOW_BAT:
VALUES:
NVAL 0
SVAL ok
VAL 0
0.LOW_BAT_LIMIT:
MASTER:
NVAL 2.2
SVAL 2.2
VAL 2.2
VALUES:
0.OPERATING_VOLTAGE:
VALUES:
NVAL 2.5
ONVAL 2.500000
OVAL 2.500000
SVAL 2.5
VAL 2.5
0.OPERATING_VOLTAGE_STATUS:
VALUES:
NVAL 0
SVAL NORMAL
VAL 0
0.RSSI_DEVICE:
VALUES:
NVAL -68
ONVAL -67
OSVAL -67
OVAL -67
SVAL -68
VAL -68
0.RSSI_PEER:
VALUES:
NVAL -69
ONVAL -65
OSVAL -65
OVAL -65
SVAL -69
VAL -69
0.SABOTAGE:
VALUES:
NVAL 0
SVAL false
VAL 0
0.SUPPORTING_WIRED_OPERATION_MODE:
MASTER:
NVAL 1
SVAL true
VAL 1
VALUES:
0.UNREACH:
VALUES:
NVAL 0
SVAL alive
VAL 0
0.UPDATE_PENDING:
VALUES:
NVAL 0
SVAL false
VAL 0
1.ALARM_MODE_TYPE:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_1:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_2:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_3:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_4:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_5:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_6:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.ALARM_MODE_ZONE_7:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.BRIGHTNESS_FILTER:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.CAPTURE_WITHIN_INTERVAL:
MASTER:
NVAL 1
SVAL true
VAL 1
VALUES:
1.COND_TX_THRESHOLD_LO:
MASTER:
NVAL 1000
SVAL 1000
VAL 1000
VALUES:
1.CURRENT_ILLUMINATION:
VALUES:
NVAL 0.05
ONVAL 0.0
OSVAL 0.0
OVAL 0.0
SVAL 0.1
VAL 0.05
1.CURRENT_ILLUMINATION_STATUS:
VALUES:
NVAL 0
SVAL NORMAL
VAL 0
1.EVENT_FILTER_NUMBER:
MASTER:
NVAL 1
SVAL 1
VAL 1
VALUES:
1.EVENT_FILTER_PERIOD:
MASTER:
NVAL 1.0
SVAL 1.0
VAL 1.0
VALUES:
1.ILLUMINATION:
VALUES:
NVAL 0.02
ONVAL 0.01
OSVAL 0.1
OVAL 0.01
SVAL 0.0
VAL 0.02
1.ILLUMINATION_STATUS:
VALUES:
NVAL 0
SVAL NORMAL
VAL 0
1.LED_DISABLE_CHANNELSTATE:
MASTER:
NVAL 0
SVAL false
VAL 0
VALUES:
1.MIN_INTERVAL:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.MOTION:
VALUES:
NVAL 0
ONVAL 1
OSVAL motion
OVAL 1
SVAL noMotion
VAL 0
1.MOTION_ACTIVE_TIME:
MASTER:
NVAL 0
SVAL 0
VAL 0
VALUES:
1.MOTION_DETECTION_ACTIVE:
VALUES:
NVAL 1
ONVAL 0
OSVAL inactive
OVAL 0
SVAL active
VAL 1
1.PIR_OPERATION_MODE:
MASTER:
NVAL 0
SVAL PIR_OPERATION_MODE_NORMAL
VAL 0
VALUES:
1.PRESS_SHORT:
VALUES:
NVAL 1
SVAL 1
VAL 1
roleChannels:
MOTIONDETECTOR_TRANSCEIVER 1
roleCmds:
get:
set:
detection:
channel 1
role MOTIONDETECTOR_TRANSCEIVER
subcount 1
syntax V:MOTION_DETECTION_ACTIVE:#detection=inactive,active
usage detection {inactive,active}
subcmd:
000:
args inactive,active
dpt MOTION_DETECTION_ACTIVE
fnc
max 0
min 0
parname detection
partype 1
ps VALUES
scn 000
type BOOL
unit
look:
active 0
inactive 0
reset:
channel 1
role MOTIONDETECTOR_TRANSCEIVER
subcount 1
syntax V:RESET_MOTION:true
usage reset
subcmd:
000:
args true
dpt RESET_MOTION
fnc
max 1
min 0
parname RESET_MOTION
partype 3
ps VALUES
scn 000
type ACTION
unit
state:
chn 1
dpt MOTION
Attributes:
IODev HMCCU3
alias BWM Jürgen
devStateStyle style="text-align:right"
event-on-change-reading .*
room Homematic
sortby 02
userReadings LastMove:.*motion.* {ReadingsVal("HMCCU3","BWM_Juergen","")}
Viele Grüße
Jürgen
Danke! Ursache gefunden:
subcmd:
000:
args inactive,active
dpt MOTION_DETECTION_ACTIVE
fnc
max 0
min 0
parname detection
partype 1
ps VALUES
scn 000
type BOOL
unit
look:
active 0
inactive 0
Die letzten beiden Zeilen, sowohl bei active als auch inactive wird 0 geschickt. Schaue ich mir an
Morgen steht ein Update im SVN zur Verfügung, das das Problem mit dem Bewegungsmelder behebt
Es funktioniert wieder.
Viele Grüße
Jürgen