Hi,
Vorab - FHem ist aktuell
Ich habe gestern einen Vibrationsmelder über zigbee2mqtt in Betrieb genommen.
Nun wurde kein Gerät angelegt sondern die Werte an die Bridge angehangen.
Wie sollte ich vorgehen um dies zu separiereren?
muss an der Bridge autocreate auf 1 stehen? Wenn ja würde es mich wundern warum es auf einmal weg ist
bridge:
Internals:
CID z2mdocker
DEF z2mdocker
DEVICETOPIC zigbee2mqtt
FUUID 61e846db-f33f-53cd-eb5e-cb9c0e377144cb2c
IODev m2c
LASTInputDev m2s
MSGCNT 382
NAME MQTT2_z2mdocker
NR 358
STATE online
TYPE MQTT2_DEVICE
m2c_MSGCNT 5
m2c_TIME 2022-01-21 12:24:17
m2s_CONN m2s_192.168.0.146_50900
m2s_MSGCNT 377
m2s_TIME 2022-01-22 10:41:03
READINGS:
2022-01-21 12:24:17 IODev m2c
2022-01-22 10:41:02 action tilt
2022-01-22 10:41:03 angle 29
2022-01-22 10:41:03 angle_x 1
2022-01-22 10:41:03 angle_x_absolute 89
2022-01-22 10:41:03 angle_y 1
2022-01-22 10:41:03 angle_y_absolute 89
2022-01-22 10:41:03 angle_z 88
2022-01-19 18:17:13 attrTemplateVersion 20220114
2022-01-22 10:36:47 availability online
2022-01-22 10:41:03 battery 100
2022-01-21 17:05:29 data_definition_description Aqara vibration sensor
2022-01-21 17:05:29 data_definition_exposes_10_access 1
2022-01-21 17:05:29 data_definition_exposes_10_description Link quality (signal strength)
2022-01-21 17:05:29 data_definition_exposes_10_name linkquality
2022-01-21 17:05:29 data_definition_exposes_10_property linkquality
2022-01-21 17:05:29 data_definition_exposes_10_type numeric
2022-01-21 17:05:29 data_definition_exposes_10_unit lqi
2022-01-21 17:05:29 data_definition_exposes_10_value_max 255
2022-01-21 17:05:29 data_definition_exposes_10_value_min 0
2022-01-21 17:05:29 data_definition_exposes_1_access 1
2022-01-21 17:05:29 data_definition_exposes_1_description Remaining battery in %
2022-01-21 17:05:29 data_definition_exposes_1_name battery
2022-01-21 17:05:29 data_definition_exposes_1_property battery
2022-01-21 17:05:29 data_definition_exposes_1_type numeric
2022-01-21 17:05:29 data_definition_exposes_1_unit %
2022-01-21 17:05:29 data_definition_exposes_1_value_max 100
2022-01-21 17:05:29 data_definition_exposes_1_value_min 0
2022-01-21 17:05:29 data_definition_exposes_2_access 1
2022-01-21 17:05:29 data_definition_exposes_2_description Indicates whether the device detected vibration
2022-01-21 17:05:29 data_definition_exposes_2_name vibration
2022-01-21 17:05:29 data_definition_exposes_2_property vibration
2022-01-21 17:05:29 data_definition_exposes_2_type binary
2022-01-21 17:05:29 data_definition_exposes_2_value_off false
2022-01-21 17:05:29 data_definition_exposes_2_value_on true
2022-01-21 17:05:29 data_definition_exposes_3_access 1
2022-01-21 17:05:29 data_definition_exposes_3_description Triggered action (e.g. a button click)
2022-01-21 17:05:29 data_definition_exposes_3_name action
2022-01-21 17:05:29 data_definition_exposes_3_property action
2022-01-21 17:05:29 data_definition_exposes_3_type enum
2022-01-21 17:05:29 data_definition_exposes_3_values_1 vibration
2022-01-21 17:05:29 data_definition_exposes_3_values_2 tilt
2022-01-21 17:05:29 data_definition_exposes_3_values_3 drop
2022-01-21 17:05:29 data_definition_exposes_4_access 1
2022-01-21 17:05:29 data_definition_exposes_4_name strength
2022-01-21 17:05:29 data_definition_exposes_4_property strength
2022-01-21 17:05:29 data_definition_exposes_4_type numeric
2022-01-21 17:05:29 data_definition_exposes_5_access 3
2022-01-21 17:05:29 data_definition_exposes_5_name sensitivity
2022-01-21 17:05:29 data_definition_exposes_5_property sensitivity
2022-01-21 17:05:29 data_definition_exposes_5_type enum
2022-01-21 17:05:29 data_definition_exposes_5_values_1 low
2022-01-21 17:05:29 data_definition_exposes_5_values_2 medium
2022-01-21 17:05:29 data_definition_exposes_5_values_3 high
2022-01-21 17:05:29 data_definition_exposes_6_access 1
2022-01-21 17:05:29 data_definition_exposes_6_name angle_x
2022-01-21 17:05:29 data_definition_exposes_6_property angle_x
2022-01-21 17:05:29 data_definition_exposes_6_type numeric
2022-01-21 17:05:29 data_definition_exposes_6_value_max 90
2022-01-21 17:05:29 data_definition_exposes_6_value_min -90
2022-01-21 17:05:29 data_definition_exposes_7_access 1
2022-01-21 17:05:29 data_definition_exposes_7_name angle_y
2022-01-21 17:05:29 data_definition_exposes_7_property angle_y
2022-01-21 17:05:29 data_definition_exposes_7_type numeric
2022-01-21 17:05:29 data_definition_exposes_7_value_max 90
2022-01-21 17:05:29 data_definition_exposes_7_value_min -90
2022-01-21 17:05:29 data_definition_exposes_8_access 1
2022-01-21 17:05:29 data_definition_exposes_8_name angle_z
2022-01-21 17:05:29 data_definition_exposes_8_property angle_z
2022-01-21 17:05:29 data_definition_exposes_8_type numeric
2022-01-21 17:05:29 data_definition_exposes_8_value_max 90
2022-01-21 17:05:29 data_definition_exposes_8_value_min -90
2022-01-21 17:05:29 data_definition_exposes_9_access 1
2022-01-21 17:05:29 data_definition_exposes_9_description Voltage of the battery in millivolts
2022-01-21 17:05:29 data_definition_exposes_9_name voltage
2022-01-21 17:05:29 data_definition_exposes_9_property voltage
2022-01-21 17:05:29 data_definition_exposes_9_type numeric
2022-01-21 17:05:29 data_definition_exposes_9_unit mV
2022-01-21 17:05:29 data_definition_model DJT11LM
2022-01-21 17:05:29 data_definition_options_1_access 2
2022-01-21 17:05:29 data_definition_options_1_description Time in seconds after which vibration is cleared after detecting it (default 90 seconds).
2022-01-21 17:05:29 data_definition_options_1_name vibration_timeout
2022-01-21 17:05:29 data_definition_options_1_property vibration_timeout
2022-01-21 17:05:29 data_definition_options_1_type numeric
2022-01-21 17:05:29 data_definition_options_1_value_min 0
2022-01-21 17:05:29 data_definition_supports_ota false
2022-01-21 17:05:29 data_definition_vendor Xiaomi
2022-01-22 09:52:57 data_friendly_name IKEA_TRADFI_WZ_KUECHE
2022-01-22 10:36:47 data_from 0x00158d000729ba21
2022-01-22 10:36:47 data_homeassistant_rename false
2022-01-22 09:52:57 data_ieee_address 0x842e14fffe411e14
2022-01-21 17:05:29 data_status successful
2022-01-21 17:05:29 data_supported true
2022-01-22 10:36:47 data_to Aqara_Briefkasten
2022-01-22 10:36:47 devices habe ich gecutted
2022-01-21 12:24:17 extensions []
2022-01-21 12:24:17 groups [{"friendly_name":"default_bind_group","id":901,"members":[],"scenes":[]}]
2022-01-22 10:36:47 info habe ich gecutted
2022-01-22 10:41:03 linkquality 72
2022-01-22 10:41:03 log_level info
2022-01-22 10:41:03 log_message MQTT publish: topic 'zigbee2mqtt/Aqara_Briefkasten', payload '{"angle":29,"angle_x":1,"angle_x_absolute":89,"angle_y":1,"angle_y_absolute":89,"angle_z":88,"battery":100,"linkquality":72,"strength":113,"vibration":true,"voltage":3195}'
2022-01-21 12:24:17 state online
2022-01-22 10:36:47 status ok
2022-01-22 10:41:03 strength 113
2022-01-21 12:25:17 subscriptions zigbee2mqtt/#
2022-01-22 10:36:47 transaction y725l-1
2022-01-22 09:52:57 type device_announce
2022-01-22 10:41:03 vibration true
2022-01-22 10:41:03 voltage 3195
Attributes:
bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]+)[/]?.*:.* "zigbee_$1"
comment To check for new updates of the deamon software, you might want to use a separate HTTPMOD device. See HTTPMOD template zigbee2mqtt_daemon_updates for further details.
devicetopic zigbee2mqtt
getList devicelist:noArg log $DEVICETOPIC/bridge/config/devices/get
networkmap_raw:noArg raw $DEVICETOPIC/bridge/networkmap raw
networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/networkmap graphviz
icon mqtt
model zigbee2mqtt_bridge
readingList $DEVICETOPIC/bridge/state:.* state
$DEVICETOPIC/bridge/config/devices:.* {}
$DEVICETOPIC/bridge/config/log_level:.* log_level
$DEVICETOPIC/bridge/config/permit_join:.* permit_join
$DEVICETOPIC/bridge/config/rename:.* { json2nameValue($EVENT, 'rename_') }
$DEVICETOPIC/bridge/config:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/log:.*\"type\".\"devices\".\"message\".* devices
$DEVICETOPIC/bridge/log:.* log
$DEVICETOPIC/bridge/logging:.* { json2nameValue($EVENT,'log_') }
$DEVICETOPIC/bridge/networkmap:.* {}
$DEVICETOPIC/bridge/networkmap/graphviz:.* graphviz
$DEVICETOPIC/bridge/networkmap/raw:.* raw
$DEVICETOPIC/bridge/devices:.* devices
$DEVICETOPIC/bridge/info:.* info
$DEVICETOPIC/bridge/groups:.* groups
$DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/extensions:.* extensions
z2mdocker:zigbee2mqtt/0x00158d000729ba21:.* { json2nameValue($EVENT) }
z2mdocker:zigbee2mqtt/Aqara_Briefkasten/availability:.* availability
z2mdocker:zigbee2mqtt/Aqara_Briefkasten:.* { json2nameValue($EVENT) }
z2mdocker:zigbee2mqtt/bridge/response/device/rename:.* { json2nameValue($EVENT) }
room MQTT2_DEVICE
setList log_level:debug,info,warn,error $DEVICETOPIC/bridge/config/log_level $EVTPART1
permit_join:true,false $DEVICETOPIC/bridge/config/permit_join $EVTPART1
remove:textField $DEVICETOPIC/bridge/config/remove $EVTPART1
ota_update:textField $DEVICETOPIC/bridge/ota_update/update $EVTPART1
ota_update_check:textField $DEVICETOPIC/bridge/ota_update/check $EVTPART1
y_device_setting:textField $DEVICETOPIC/$EVTPART1/set {"$EVTPART2": "$EVTPART3"}
x_bind:textField $DEVICETOPIC/bridge/bind/$EVTPART1 $EVTPART2
x_bind_unbind:textField $DEVICETOPIC/bridge/unbind/$EVTPART1 $EVTPART2
x_device_options:textField $DEVICETOPIC/bridge/config/device_options {"friendly_name":"$EVTPART1","options": {"$EVTPART2": "$EVTPART3"}}
x_group_add_to:textField $DEVICETOPIC/bridge/group/$EVTPART1/add $EVTPART2
x_group_rm_from:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove $EVTPART2
x_group_rm_from_all:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove_all $EVTPART2
x_group_add_group:textField $DEVICETOPIC/bridge/config/add_group $EVTPART1
x_group_rm_group:textField $DEVICETOPIC/bridge/config/remove_group $EVTPART1
z_elapsed:textField $DEVICETOPIC/bridge/config/elapsed $EVTPART1
z_last_seen:disable,ISO_8601,epoch,ISO_8601_local $DEVICETOPIC/bridge/config/last_seen $EVTPART1
z_ban:textField $DEVICETOPIC/bridge/config/ban $EVTPART1
z_rename:textField $DEVICETOPIC/bridge/config/rename {"old":"$EVTPART1","new":"$EVTPART2"}
z_reset_CC:noArg $DEVICETOPIC/bridge/config/reset
setStateList on off
server:
Internals:
CONNECTS 18
Clients :MQTT2_DEVICE:MQTT_GENERIC_BRIDGE:
ClientsKeepOrder 1
DEF 11883 global
FD 26
FUUID 61dca4ae-f33f-53cd-d84e-c153f9f8956e0964
NAME m2s
NR 305
PORT 11883
STATE Initialized
TYPE MQTT2_SERVER
MatchList:
1:MQTT2_DEVICE ^.
2:MQTT_GENERIC_BRIDGE ^.
READINGS:cutted
2022-01-17 21:15:24 lastPublish cmnd/Vindriktning/Backlog:StateText1 off; StateText2 on; StateText3 toggle; StateText4 hold; SetOption26 1; SaveData 1
2022-01-22 01:53:43 nrclients 9
2022-01-21 12:24:17 state Initialized
clients:
m2s_192.168.0.122_59117 1
m2s_192.168.0.124_52497 1
m2s_192.168.0.146_50900 1
m2s_192.168.0.37_57904 1
m2s_192.168.0.41_53727 1
m2s_192.168.0.84_60080 1
m2s_192.168.0.85_52231 1
m2s_192.168.0.86_62795 1
m2s_192.168.0.8_58876 1
retain:
dafang1:
ts 1642764257.15495
val {"uptime":" 21:15:46 up 0 min, 0 users, load average: 1.03, 0.26, 0.08", "ssid":"bigbossbgn", "bitrate":"72.2 Mb/s", "signal_level":"75%", "link_quality":"72%", "noise_level":"0%" }
dafang1/ir_cut:
ts 1642764257.15495
val ON
dafang1/leds/blue:
ts 1642764257.15495
val ON
dafang1/leds/ir:
ts 1642764257.15495
val OFF
dafang1/leds/yellow:
ts 1642764257.15495
val OFF
dafang1/motion/detection:
ts 1642764257.15495
val ON
dafang1/motion/send_mail:
ts 1642764257.15495
val OFF
dafang1/motion/send_telegram:
ts 1642764257.15495
val OFF
dafang1/motion/tracking:
ts 1642764257.15495
val OFF
dafang1/motors/horizontal:
ts 1642764257.15495
val 0
dafang1/motors/vertical:
ts 1642764257.15495
val 0
dafang1/night_mode:
ts 1642764257.15495
val OFF
dafang1/night_mode/auto:
ts 1642764257.15495
val ON
dafang1/rtsp_h264_server:
ts 1642764257.15495
val OFF
dafang1/rtsp_mjpeg_server:
ts 1642764257.15495
val ON
dafang2:
ts 1642764257.15495
val {"uptime":" 21:11:47 up 0 min, 0 users, load average: 0.14, 0.03, 0.01", "ssid":"bigbossbgn", "bitrate":"72.2 Mb/s", "signal_level":"90%", "link_quality":"66%", "noise_level":"0%" }
dafang2/ir_cut:
ts 1642764257.15495
val ON
dafang2/leds/blue:
ts 1642764257.15495
val ON
dafang2/leds/ir:
ts 1642764257.15495
val OFF
dafang2/leds/yellow:
ts 1642764257.15495
val OFF
dafang2/motion/detection:
ts 1642764257.15495
val ON
dafang2/motion/send_mail:
ts 1642764257.15495
val OFF
dafang2/motion/send_telegram:
ts 1642764257.15495
val OFF
dafang2/motion/tracking:
ts 1642764257.15495
val OFF
dafang2/motors/horizontal:
ts 1642764257.15495
val 0
dafang2/motors/vertical:
ts 1642764257.15495
val 0
dafang2/night_mode:
ts 1642764257.15495
val OFF
dafang2/night_mode/auto:
ts 1642764257.15495
val ON
dafang2/rtsp_h264_server:
ts 1642764257.15495
val OFF
dafang2/rtsp_mjpeg_server:
ts 1642764257.15495
val ON
dafang3:
ts 1642764257.15495
val {"uptime":" 21:08:25 up 4 min, 0 users, load average: 2.22, 1.17, 0.48", "ssid":"bigbossbgn", "bitrate":"72.2 Mb/s", "signal_level":"86%", "link_quality":"68%", "noise_level":"0%" }
dafang3/ir_cut:
ts 1642764257.15495
val ON
dafang3/leds/blue:
ts 1642764257.15495
val ON
dafang3/leds/ir:
ts 1642764257.15495
val OFF
dafang3/leds/yellow:
ts 1642764257.15495
val OFF
dafang3/motion/detection:
ts 1642764257.15495
val ON
dafang3/motion/send_mail:
ts 1642764257.15495
val OFF
dafang3/motion/send_telegram:
ts 1642764257.15495
val OFF
dafang3/motion/tracking:
ts 1642764257.15495
val OFF
dafang3/motors/horizontal:
ts 1642764257.15495
val 0
dafang3/motors/vertical:
ts 1642764257.15495
val 100
dafang3/night_mode:
ts 1642764257.15495
val OFF
dafang3/night_mode/auto:
ts 1642764257.15495
val ON
dafang3/rtsp_h264_server:
ts 1642764257.15495
val OFF
dafang3/rtsp_mjpeg_server:
ts 1642764257.15495
val ON
tasmota/discovery/2C3AE83BC7C0/config:
ts 1642764264.6274
val {"ip":"192.168.0.8","dn":"Sonoff","fn":["Sonoff",null,null,null,null,null,null,null],"hn":"Sonoff-Spielzimmerlicht","mac":"2C3AE83BC7C0","md":"Sonoff Basic","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["off","on","toggle","hold"],"sw":"10.1.0","t":"Sonoff_Spielzimmerlicht","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"sho":[0,0,0,0],"ver":1}
tasmota/discovery/2C3AE83BC7C0/sensors:
ts 1642764264.63067
val {"sn":{"Time":"2022-01-21T12:24:24"},"ver":1}
tasmota/discovery/84F3EBEC9DF6/config:
ts 1642764264.03065
val {"ip":"192.168.0.84","dn":"SP111_01","fn":["SP111_01",null,null,null,null,null,null,null],"hn":"SP111-01","mac":"84F3EBEC9DF6","md":"BW_JVM","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["off","on","toggle","hold"],"sw":"10.1.0","t":"SP111_01","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"sho":[0,0,0,0],"ver":1}
tasmota/discovery/84F3EBEC9DF6/sensors:
ts 1642764264.03949
val {"sn":{"Time":"2022-01-21T12:24:24","ENERGY":{"TotalStartTime":"2019-12-07T19:24:58","Total":5.112,"Yesterday":0.008,"Today":0.002,"Power": 0,"ApparentPower": 0,"ReactivePower": 0,"Factor":0.00,"Voltage": 0,"Current":0.000}},"ver":1}
tasmota/discovery/84F3EBEC9FB1/config:
ts 1642764264.74953
val {"ip":"192.168.0.85","dn":"SP111_02","fn":["SP111_02",null,null,null,null,null,null,null],"hn":"SP111-02","mac":"84F3EBEC9FB1","md":"BW_JVM","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["off","on","toggle","hold"],"sw":"2022.01.2","t":"SP111_02","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"sho":[0,0,0,0],"ver":1}
tasmota/discovery/84F3EBEC9FB1/sensors:
ts 1642764264.75269
val {"sn":{"Time":"2022-01-21T12:24:24","ENERGY":{"TotalStartTime":"2019-12-07T19:51:00","Total":20.236,"Yesterday":0.008,"Today":0.004,"Power": 0,"ApparentPower": 0,"ReactivePower": 0,"Factor":0.00,"Voltage": 0,"Current":0.000}},"ver":1}
tasmota/discovery/84F3EBECA01E/config:
ts 1642775339.47302
val {"ip":"192.168.0.86","dn":"SP111_03","fn":["SP111_03",null,null,null,null,null,null,null],"hn":"SP111-03","mac":"84F3EBECA01E","md":"BW_JVM","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["off","on","toggle","hold"],"sw":"10.1.0","t":"tasmota_ECA01E","ft":"%prefix%/SP111_03/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"sho":[0,0,0,0],"ver":1}
tasmota/discovery/84F3EBECA01E/sensors:
ts 1642775339.4765
val {"sn":{"Time":"2022-01-21T15:28:57","ENERGY":{"TotalStartTime":"2019-12-07T20:04:33","Total":59.369,"Yesterday":0.529,"Today":0.252,"Power": 0,"ApparentPower": 0,"ReactivePower": 0,"Factor":0.00,"Voltage": 0,"Current":0.000}},"ver":1}
tasmota/discovery/B4E62D1526D0/config:
ts 1642786034.21602
val {"ip":"192.168.0.37","dn":"SONOFFS205","fn":["SONOFFS205",null,null,null,null,null,null,null],"hn":"sonoffs205","mac":"B4E62D1526D0","md":"Sonoff S2X","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["off","on","toggle","hold"],"sw":"2022.01.2","t":"Sonoffs205","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"sho":[0,0,0,0],"ver":1}
tasmota/discovery/B4E62D1526D0/sensors:
ts 1642786034.21947
val {"sn":{"Time":"2022-01-21T18:27:14"},"ver":1}
tasmota/discovery/C4DD570B4915/config:
ts 1642776560.1657
val {"ip":"192.168.0.122","dn":"SP1_01","fn":["SP1_01",null,null,null,null,null,null,null],"hn":"SP1-01","mac":"C4DD570B4915","md":"Gosund SP1 v23","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["off","on","toggle","hold"],"sw":"10.1.0","t":"SP1_01","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"sho":[0,0,0,0],"ver":1}
tasmota/discovery/C4DD570B4915/sensors:
ts 1642776560.17303
val {"sn":{"Time":"2022-01-21T15:49:19","ENERGY":{"TotalStartTime":"2021-01-16T22:04:25","Total":9.687,"Yesterday":0.000,"Today":2.668,"Power": 4,"ApparentPower":16,"ReactivePower":16,"Factor":0.23,"Voltage":234,"Current":0.068}},"ver":1}
tasmota/discovery/C4DD570E93F9/config:
ts 1642812823.89547
val {"ip":"192.168.0.124","dn":"SP1_02","fn":["SP1_02",null,null,null,null,null,null,null],"hn":"SP1-02","mac":"C4DD570E93F9","md":"Gosund SP1 v23","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["off","on","toggle","hold"],"sw":"2022.01.2","t":"SP1_02","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[1,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"sho":[0,0,0,0],"ver":1}
tasmota/discovery/C4DD570E93F9/sensors:
ts 1642812823.8991
val {"sn":{"Time":"2022-01-22T01:53:43","ENERGY":{"TotalStartTime":"2021-01-16T22:14:25","Total":4.213,"Yesterday":2.600,"Today":0.004,"Power": 2,"ApparentPower": 7,"ReactivePower": 7,"Factor":0.30,"Voltage":234,"Current":0.031}},"ver":1}
tasmota/discovery/E098069214F5/config:
ts 1642764264.47956
val {"ip":"192.168.0.41","dn":"VINDRIKTNING","fn":["VINDRIKTNING",null,null,null,null,null,null,null],"hn":"VINDRIKTNING","mac":"E098069214F5","md":"Generic","ty":0,"if":0,"ofln":"Offline","onln":"Online","state":["off","on","toggle","hold"],"sw":"10.0.0.4","t":"Vindriktning","ft":"%prefix%/%topic%/","tp":["cmnd","stat","tele"],"rl":[0,0,0,0,0,0,0,0],"swc":[-1,-1,-1,-1,-1,-1,-1,-1],"swn":[null,null,null,null,null,null,null,null],"btn":[0,0,0,0,0,0,0,0],"so":{"4":0,"11":0,"13":0,"17":0,"20":0,"30":0,"68":0,"73":0,"82":0,"114":0,"117":0},"lk":0,"lt_st":0,"sho":[0,0,0,0],"ver":1}
tasmota/discovery/E098069214F5/sensors:
ts 1642764264.4829
val {"sn":{"Time":"2022-01-21T12:24:24","VINDRIKTNING":{"PM2.5":8}},"ver":1}
tele/SP111_01/LWT:
ts 1642764264.01058
val Online
tele/SP111_02/LWT:
ts 1642764264.25361
val Online
tele/SP111_03/LWT:
ts 1642775338.53406
val Online
tele/SP1_01/LWT:
ts 1642776560.14837
val Online
tele/SP1_02/LWT:
ts 1642812823.3567
val Online
tele/Sonoff_Spielzimmerlicht/LWT:
ts 1642764264.19404
val Online
tele/Sonoffs205/LWT:
ts 1642786033.82461
val Online
tele/Vindriktning/LWT:
ts 1642764264.22774
val Online
tele/sonoffs205/LWT:
ts 1642764257.15495
val Offline
tele/tasmota_9214F5/LWT:
ts 1642764257.15495
val Offline
tele/tasmota_ECA01E/LWT:
ts 1642764257.15495
val Offline
zigbee2mqtt/Aqara_Briefkasten/availability:
ts 1642844207.57242
val online
zigbee2mqtt/bridge/devices:
ts 1642844207.54791
val cutted
zigbee2mqtt/bridge/extensions:
ts 1642764257.15495
val []
zigbee2mqtt/bridge/groups:
ts 1642764257.15495
val [{"friendly_name":"default_bind_group","id":901,"members":[],"scenes":[]}]
zigbee2mqtt/bridge/info:
ts 1642844207.6896
val cutted
zigbee2mqtt/bridge/state:
ts 1642764257.71589
val online
Attributes:
keepaliveFactor 5
room Messenger
Ich musste einiges kürze da das Forum sonst Datenbankfehler meldete :-[
In der bridge (im MQTT2_DEVICE) ist autocreate per default 1. Das wirkt aber nur lokal im Gerät.
ist autocreate im System an?
list autocreate
Hi,
ja ist gesetzt, wenn ich das richtig deute:
Internals:
FUUID 61d76136-f33f-53cd-6db1-1be1923f63662e86
NAME autocreate
NOTIFYDEV global
NR 10
NTFY_ORDER 50-autocreate
STATE active
TYPE autocreate
Attributes:
filelog ./log/%NAME-%Y.log
Im normalen LogFile hast Du auch keine autocreate Einträge?
Keine neuen von diesem "Fall".
die EInträge in der Readinglist hat "er" erzeugt:
z2mdocker:zigbee2mqtt/0x00158d000729ba21:.* { json2nameValue($EVENT) }\
z2mdocker:zigbee2mqtt/Aqara_Briefkasten/availability:.* availability\
z2mdocker:zigbee2mqtt/Aqara_Briefkasten:.* { json2nameValue($EVENT) }\
EDIT: Hab die mal rausgelöscht. Das Device bewegt und es erzeugt Meldungen
und zack:
Internals:
CFGFN
CID zigbee_Aqara_Briefkasten
DEF zigbee_Aqara_Briefkasten
DEVICETOPIC MQTT2_zigbee_Aqara_Briefkasten
FUUID 61ebeaca-f33f-53cd-6f8f-94fc6a3a72c5ea54
IODev m2s
LASTInputDev m2s
MSGCNT 1
NAME MQTT2_zigbee_Aqara_Briefkasten
NR 1661
STATE ???
TYPE MQTT2_DEVICE
m2s_CONN m2s_192.168.0.146_50914
m2s_MSGCNT 1
m2s_TIME 2022-01-22 12:30:53
READINGS:
2022-01-22 12:30:18 IODev m2s
2022-01-22 12:30:18 action vibration
2022-01-22 12:30:53 angle 29
2022-01-22 12:30:53 angle_x 1
2022-01-22 12:30:53 angle_x_absolute 89
2022-01-22 12:30:53 angle_y 1
2022-01-22 12:30:53 angle_y_absolute 89
2022-01-22 12:30:53 angle_z 88
2022-01-22 12:30:18 associatedWith MQTT2_z2mdocker
2022-01-22 12:30:53 battery 100
2022-01-22 12:30:53 linkquality 81
2022-01-22 12:30:53 strength 86
2022-01-22 12:30:53 vibration true
2022-01-22 12:30:53 voltage 3185
Attributes:
readingList zigbee2mqtt/Aqara_Briefkasten:.* { json2nameValue($EVENT) }
room MQTT2_DEVICE
angelegt.
Ich VERMUTE, dass bei der Erstinbetriebnahme in Zigbee2mwtt noch dieser 0x48234384723894 name war. Das "mochte" fhem wohl nicht so richtig und wollte kein device anlegen
Und auch gleich zigbee2mqtt_Motion_Sensor zugewiesen - läuft.
Ich habe heute nochmal geschaut.
Leider habe ich an meiner Bridge nun viele Werte, die da nicht hingehören vermute ich.
Was ist davon richtig
und was kann davon wie weg?
defmod MQTT2_z2mdocker MQTT2_DEVICE z2mdocker
attr MQTT2_z2mdocker bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]+)[/]?.*:.* "zigbee_$1"
attr MQTT2_z2mdocker comment To check for new updates of the deamon software, you might want to use a separate HTTPMOD device. See HTTPMOD template zigbee2mqtt_daemon_updates for further details.
attr MQTT2_z2mdocker devicetopic zigbee2mqtt
attr MQTT2_z2mdocker getList devicelist:noArg log $DEVICETOPIC/bridge/config/devices/get\
networkmap_raw:noArg raw $DEVICETOPIC/bridge/networkmap raw\
networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/networkmap graphviz
attr MQTT2_z2mdocker icon mqtt
attr MQTT2_z2mdocker model zigbee2mqtt_bridge
attr MQTT2_z2mdocker readingList $DEVICETOPIC/bridge/state:.* state\
$DEVICETOPIC/bridge/config/devices:.* {}\
$DEVICETOPIC/bridge/config/log_level:.* log_level\
$DEVICETOPIC/bridge/config/permit_join:.* permit_join\
$DEVICETOPIC/bridge/config/rename:.* { json2nameValue($EVENT, 'rename_') }\
$DEVICETOPIC/bridge/config:.* { json2nameValue($EVENT) }\
$DEVICETOPIC/bridge/log:.*\"type\".\"devices\".\"message\".* devices\
$DEVICETOPIC/bridge/log:.* log\
$DEVICETOPIC/bridge/logging:.* { json2nameValue($EVENT,'log_') }\
$DEVICETOPIC/bridge/networkmap:.* {}\
$DEVICETOPIC/bridge/networkmap/graphviz:.* graphviz\
$DEVICETOPIC/bridge/networkmap/raw:.* raw\
$DEVICETOPIC/bridge/devices:.* devices\
$DEVICETOPIC/bridge/info:.* info\
$DEVICETOPIC/bridge/groups:.* groups\
$DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }\
$DEVICETOPIC/bridge/extensions:.* extensions
attr MQTT2_z2mdocker room MQTT2_DEVICE
attr MQTT2_z2mdocker setList log_level:debug,info,warn,error $DEVICETOPIC/bridge/config/log_level $EVTPART1\
permit_join:true,false $DEVICETOPIC/bridge/config/permit_join $EVTPART1\
remove:textField $DEVICETOPIC/bridge/config/remove $EVTPART1\
ota_update:textField $DEVICETOPIC/bridge/ota_update/update $EVTPART1\
ota_update_check:textField $DEVICETOPIC/bridge/ota_update/check $EVTPART1\
y_device_setting:textField $DEVICETOPIC/$EVTPART1/set {"$EVTPART2": "$EVTPART3"}\
x_bind:textField $DEVICETOPIC/bridge/bind/$EVTPART1 $EVTPART2\
x_bind_unbind:textField $DEVICETOPIC/bridge/unbind/$EVTPART1 $EVTPART2\
x_device_options:textField $DEVICETOPIC/bridge/config/device_options {"friendly_name":"$EVTPART1","options": {"$EVTPART2": "$EVTPART3"}}\
x_group_add_to:textField $DEVICETOPIC/bridge/group/$EVTPART1/add $EVTPART2\
x_group_rm_from:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove $EVTPART2\
x_group_rm_from_all:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove_all $EVTPART2\
x_group_add_group:textField $DEVICETOPIC/bridge/config/add_group $EVTPART1\
x_group_rm_group:textField $DEVICETOPIC/bridge/config/remove_group $EVTPART1\
z_elapsed:textField $DEVICETOPIC/bridge/config/elapsed $EVTPART1\
z_last_seen:disable,ISO_8601,epoch,ISO_8601_local $DEVICETOPIC/bridge/config/last_seen $EVTPART1\
z_ban:textField $DEVICETOPIC/bridge/config/ban $EVTPART1\
z_rename:textField $DEVICETOPIC/bridge/config/rename {"old":"$EVTPART1","new":"$EVTPART2"}\
z_reset_CC:noArg $DEVICETOPIC/bridge/config/reset
attr MQTT2_z2mdocker setStateList on off
setstate MQTT2_z2mdocker online
setstate MQTT2_z2mdocker 2022-01-23 00:02:15 IODev m2c
setstate MQTT2_z2mdocker 2022-01-22 12:26:55 action vibration
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 angle 29
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 angle_x 1
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 angle_x_absolute 89
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 angle_y 1
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 angle_y_absolute 89
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 angle_z 88
setstate MQTT2_z2mdocker 2022-01-19 18:17:13 attrTemplateVersion 20220114
setstate MQTT2_z2mdocker 2022-01-22 10:36:47 availability online
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 battery 100
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_description Aqara vibration sensor
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_10_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_10_description Link quality (signal strength)
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_10_name linkquality
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_10_property linkquality
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_10_type numeric
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_10_unit lqi
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_10_value_max 255
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_10_value_min 0
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_1_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_1_description Remaining battery in %
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_1_name battery
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_1_property battery
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_1_type numeric
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_1_unit %
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_1_value_max 100
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_1_value_min 0
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_2_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_2_description Indicates whether the device detected vibration
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_2_name vibration
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_2_property vibration
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_2_type binary
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_2_value_off false
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_2_value_on true
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_3_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_3_description Triggered action (e.g. a button click)
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_3_name action
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_3_property action
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_3_type enum
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_3_values_1 vibration
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_3_values_2 tilt
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_3_values_3 drop
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_4_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_4_name strength
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_4_property strength
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_4_type numeric
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_5_access 3
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_5_name sensitivity
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_5_property sensitivity
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_5_type enum
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_5_values_1 low
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_5_values_2 medium
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_5_values_3 high
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_6_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_6_name angle_x
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_6_property angle_x
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_6_type numeric
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_6_value_max 90
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_6_value_min -90
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_7_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_7_name angle_y
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_7_property angle_y
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_7_type numeric
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_7_value_max 90
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_7_value_min -90
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_8_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_8_name angle_z
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_8_property angle_z
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_8_type numeric
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_8_value_max 90
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_8_value_min -90
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_9_access 1
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_9_description Voltage of the battery in millivolts
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_9_name voltage
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_9_property voltage
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_9_type numeric
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_exposes_9_unit mV
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_model DJT11LM
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_options_1_access 2
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_options_1_description Time in seconds after which vibration is cleared after detecting it (default 90 seconds).
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_options_1_name vibration_timeout
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_options_1_property vibration_timeout
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_options_1_type numeric
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_options_1_value_min 0
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_supports_ota false
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_definition_vendor Xiaomi
setstate MQTT2_z2mdocker 2022-01-24 08:21:24 data_friendly_name STYRBAR01
setstate MQTT2_z2mdocker 2022-01-22 10:36:47 data_from 0x00158d000729ba21
setstate MQTT2_z2mdocker 2022-01-22 10:36:47 data_homeassistant_rename false
setstate MQTT2_z2mdocker 2022-01-24 08:21:24 data_ieee_address 0x842e14fffe68d419
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_status successful
setstate MQTT2_z2mdocker 2022-01-21 17:05:29 data_supported true
setstate MQTT2_z2mdocker 2022-01-22 10:36:47 data_to Aqara_Briefkasten
setstate MQTT2_z2mdocker 2022-01-24 08:21:24 devices lange liste gekillt
setstate MQTT2_z2mdocker 2022-01-23 00:02:15 extensions []
setstate MQTT2_z2mdocker 2022-01-23 00:02:15 groups [{"friendly_name":"default_bind_group","id":901,"members":[],"scenes":[]}]
setstate MQTT2_z2mdocker 2022-01-23 00:02:15 info lange liste gekillt
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 linkquality 60
setstate MQTT2_z2mdocker 2022-01-24 13:40:51 log_level info
setstate MQTT2_z2mdocker 2022-01-24 13:40:51 log_message MQTT publish: topic 'zigbee2mqtt/Aqara_Briefkasten', payload '{"angle":87,"angle_x":-69,"angle_x_absolute":159,"angle_y":-3,"angle_y_absolute":93,"angle_z":21,"battery":100,"linkquality":60,"strength":19,"vibration":false,"voltage":3135}'
setstate MQTT2_z2mdocker 2022-01-23 00:02:16 state online
setstate MQTT2_z2mdocker 2022-01-22 10:36:47 status ok
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 strength 6
setstate MQTT2_z2mdocker 2022-01-24 13:03:32 subscriptions zigbee2mqtt/#
setstate MQTT2_z2mdocker 2022-01-22 10:36:47 transaction y725l-1
setstate MQTT2_z2mdocker 2022-01-24 08:21:24 type device_announce
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 vibration false
setstate MQTT2_z2mdocker 2022-01-22 12:28:25 voltage 3185
Desweiteren laufen die get Befehle immer in einen Timeout und sehe sie mit dem mqttexplorer auch nicht.
Zitat von: masterpete23 am 24 Januar 2022, 13:43:27
Leider habe ich an meiner Bridge nun viele Werte, die da nicht hingehören vermute ich.
Was ist davon richtig
und was kann davon wie weg?
Prinzipiell werden fast alle Readings, die von der MQTT-Seite her erzeugt werden auch wieder ergänzt, sobald die entsprechende Info (beim passenden Device) ankommt. Gibt recht wenige Ausnahmen, von daher macht attrTemplate standardmäßig auch sowas:
deletereading -q DEVICE (?!associatedWith|IODev).*(lösche alles bis auf...) Hier würde ich vielleicht noch die attrTemplate-Version belassen...
Zitat
Desweiteren laufen die get Befehle immer in einen Timeout und sehe sie mit dem mqttexplorer auch nicht.
Das mit den timeouts ist "normal" - da kommt entweder gar keine Rückmeldung oder eben eine verspätete oder eine, die auf das "falsche" Reading gemappt wird...(Falls jemand Ideen hat, wie man das verbessern kann, baue ich es ein, das sorgt anscheinend immer wieder für Irritationen)
Danke. Jetzt ist die Bridge wieder sauber.
WEnn ich über Zigbee2mqtt so eine Netzwerkkarte erstellen lasse, legt mir FHEM mit der Antwort ein neues device an.
Liegt das daran, weil die Benamung bei mir anders ist?
Oder kann ich die Antwort irgendwie abfangen
Er legt : MQTT2_zigbee_bridge an
Internals:
CFGFN
CID zigbee_bridge
DEF zigbee_bridge
DEVICETOPIC MQTT2_zigbee_bridge
FUUID 61eeae3c-f33f-53cd-d44e-3d8f5d2e874df810
IODev m2s
NAME MQTT2_zigbee_bridge
NR 686
STATE ???
TYPE MQTT2_DEVICE
READINGS:
2022-01-24 14:48:44 IODev m2s
2022-01-24 14:48:44 associatedWith MQTT2_z2mdocker
2022-01-24 14:48:44 networkmap ganz viel text
Attributes:
readingList zigbee2mqtt/bridge/response/networkmap:.* networkmap
room MQTT2_DEVICE
meine Bridge ist aber
Save config
Amazon
Badezimmer
CUL
Flur
Garten
Information
Kalender
Keller
Kueche
Logik
MAX
MQTT2_DEVICE
Mats
Messenger
Plots
Residents
Saugroboter
Tim
Unsorted
Wetter
Wohnzimmer
icoEverything Everything
Logfile
Commandref
Remote doc
Edit files
Select style
Event monitor
Internals:
CID z2mdocker
DEF z2mdocker
DEVICETOPIC zigbee2mqtt
FUUID 61e846db-f33f-53cd-eb5e-cb9c0e377144cb2c
IODev m2s
LASTInputDev m2s
MSGCNT 7
NAME MQTT2_z2mdocker
NR 357
STATE online
TYPE MQTT2_DEVICE
m2s_CONN m2s_192.168.0.146_50964
m2s_MSGCNT 7
m2s_TIME 2022-01-24 14:48:44
READINGS:
2022-01-24 14:45:06 IODev m2s
2022-01-19 18:17:13 attrTemplateVersion 20220114
2022-01-24 14:48:44 log_level info
2022-01-24 14:48:44 log_message ganz viel text
2022-01-24 14:45:07 state online
2022-01-24 14:48:44 subscriptions zigbee2mqtt/#
Attributes:
bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]+)[/]?.*:.* "zigbee_$1"
comment To check for new updates of the deamon software, you might want to use a separate HTTPMOD device. See HTTPMOD template zigbee2mqtt_daemon_updates for further details.
devicetopic zigbee2mqtt
getList devicelist:noArg log $DEVICETOPIC/bridge/config/devices/get
networkmap_raw:noArg raw $DEVICETOPIC/bridge/networkmap raw
networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/networkmap graphviz
icon mqtt
model zigbee2mqtt_bridge
readingList $DEVICETOPIC/bridge/state:.* state
$DEVICETOPIC/bridge/config/devices:.* {}
$DEVICETOPIC/bridge/config/log_level:.* log_level
$DEVICETOPIC/bridge/config/permit_join:.* permit_join
$DEVICETOPIC/bridge/config/rename:.* { json2nameValue($EVENT, 'rename_') }
$DEVICETOPIC/bridge/config:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/log:.*\"type\".\"devices\".\"message\".* devices
$DEVICETOPIC/bridge/log:.* log
$DEVICETOPIC/bridge/logging:.* { json2nameValue($EVENT,'log_') }
$DEVICETOPIC/bridge/networkmap:.* {}
$DEVICETOPIC/bridge/networkmap/graphviz:.* graphviz
$DEVICETOPIC/bridge/networkmap/raw:.* raw
$DEVICETOPIC/bridge/devices:.* devices
$DEVICETOPIC/bridge/info:.* info
$DEVICETOPIC/bridge/groups:.* groups
$DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/extensions:.* extensions
room MQTT2_DEVICE
setList log_level:debug,info,warn,error $DEVICETOPIC/bridge/config/log_level $EVTPART1
permit_join:true,false $DEVICETOPIC/bridge/config/permit_join $EVTPART1
remove:textField $DEVICETOPIC/bridge/config/remove $EVTPART1
ota_update:textField $DEVICETOPIC/bridge/ota_update/update $EVTPART1
ota_update_check:textField $DEVICETOPIC/bridge/ota_update/check $EVTPART1
y_device_setting:textField $DEVICETOPIC/$EVTPART1/set {"$EVTPART2": "$EVTPART3"}
x_bind:textField $DEVICETOPIC/bridge/bind/$EVTPART1 $EVTPART2
x_bind_unbind:textField $DEVICETOPIC/bridge/unbind/$EVTPART1 $EVTPART2
x_device_options:textField $DEVICETOPIC/bridge/config/device_options {"friendly_name":"$EVTPART1","options": {"$EVTPART2": "$EVTPART3"}}
x_group_add_to:textField $DEVICETOPIC/bridge/group/$EVTPART1/add $EVTPART2
x_group_rm_from:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove $EVTPART2
x_group_rm_from_all:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove_all $EVTPART2
x_group_add_group:textField $DEVICETOPIC/bridge/config/add_group $EVTPART1
x_group_rm_group:textField $DEVICETOPIC/bridge/config/remove_group $EVTPART1
z_elapsed:textField $DEVICETOPIC/bridge/config/elapsed $EVTPART1
z_last_seen:disable,ISO_8601,epoch,ISO_8601_local $DEVICETOPIC/bridge/config/last_seen $EVTPART1
z_ban:textField $DEVICETOPIC/bridge/config/ban $EVTPART1
z_rename:textField $DEVICETOPIC/bridge/config/rename {"old":"$EVTPART1","new":"$EVTPART2"}
z_reset_CC:noArg $DEVICETOPIC/bridge/config/reset
setStateList on off
Na ja, da scheint sich ein Antwortpfad geändert zu haben... Mal wieder: komisch, dass das bisher keinem aufgefallen ist.
Wenn man (=ich) jetzt noch die Info hätte, welche map-Variante du angefragt hattest, könnte "man" es auch gleich reparieren... (dto. für die 2. Variante).
Zitat von: Beta-User am 24 Januar 2022, 14:58:05
Na ja, da scheint sich ein Antwortpfad geändert zu haben... Mal wieder: komisch, dass das bisher keinem aufgefallen ist.
Wenn man (=ich) jetzt noch die Info hätte, welche map-Variante du angefragt hattest, könnte "man" es auch gleich reparieren... (dto. für die 2. Variante).
Sorry, kam jetzt erst dazu zu antworten.
Das Problem tritt bei allen GETs auf.
Timeout reading answer for zigbee2mqtt/bridge/config/devices/getTimeout reading answer for zigbee2mqtt/bridge/networkmap graphvizTimeout reading answer for zigbee2mqtt/bridge/networkmap raw
Hmm, anscheinend hatte ich die Frage nicht spezifisch genug gestellt:
Auf welchen Pfad wird _jeweils_ die Antwort gesendet?
Der timeout titt auf weil die Antwort jeweils
- vielleicht zu spät kommt (aber uU. auf den richtigen Topic), oder
- auf einen anderen Topic kommt (das scheint bei den networkmap-Anfragen der Fall zu sein, aus dem einen gezeigten Topic läßt sich aber nicht ableiten, welche von beiden das war).
Da in der Doku auf die Schnelle nichts zu finden war, wäre es hilfreich, wenn jemand dazu eine etwas spezifischere Auskunft - getrennt für alle drei Abfragen - geben könnte...
Also was ich dir liefern kann ist, dass es anscheinend nichts auslöst, wenn ich die Befehle absetze.
Im MQTT Explorer sehe ich nichts neues.
Liegt es an meinem Naming?
Meine Bridge heißt ja
defmod MQTT2_z2mdocker MQTT2_DEVICE z2mdocker
attr MQTT2_z2mdocker bridgeRegexp zigbee2mqtt/([A-Za-z0-9._]+)[/]?.*:.* "zigbee_$1"
attr MQTT2_z2mdocker comment To check for new updates of the deamon software, you might want to use a separate HTTPMOD device. See HTTPMOD template zigbee2mqtt_daemon_updates for further details.
attr MQTT2_z2mdocker devicetopic zigbee2mqtt
attr MQTT2_z2mdocker getList devicelist:noArg log $DEVICETOPIC/bridge/config/devices/get\
networkmap_raw:noArg raw $DEVICETOPIC/bridge/networkmap raw\
networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/networkmap graphviz
attr MQTT2_z2mdocker icon mqtt
attr MQTT2_z2mdocker model zigbee2mqtt_bridge
attr MQTT2_z2mdocker readingList $DEVICETOPIC/bridge/state:.* state\
$DEVICETOPIC/bridge/config/devices:.* {}\
$DEVICETOPIC/bridge/config/log_level:.* log_level\
$DEVICETOPIC/bridge/config/permit_join:.* permit_join\
$DEVICETOPIC/bridge/config/rename:.* { json2nameValue($EVENT, 'rename_') }\
$DEVICETOPIC/bridge/config:.* { json2nameValue($EVENT) }\
$DEVICETOPIC/bridge/log:.*\"type\".\"devices\".\"message\".* devices\
$DEVICETOPIC/bridge/log:.* log\
$DEVICETOPIC/bridge/logging:.* { json2nameValue($EVENT,'log_') }\
$DEVICETOPIC/bridge/networkmap:.* {}\
$DEVICETOPIC/bridge/networkmap/graphviz:.* graphviz\
$DEVICETOPIC/bridge/networkmap/raw:.* raw\
$DEVICETOPIC/bridge/devices:.* devices\
$DEVICETOPIC/bridge/info:.* info\
$DEVICETOPIC/bridge/groups:.* groups\
$DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }\
$DEVICETOPIC/bridge/extensions:.* extensions
attr MQTT2_z2mdocker room MQTT2_DEVICE
attr MQTT2_z2mdocker setList log_level:debug,info,warn,error $DEVICETOPIC/bridge/config/log_level $EVTPART1\
permit_join:true,false $DEVICETOPIC/bridge/config/permit_join $EVTPART1\
remove:textField $DEVICETOPIC/bridge/config/remove $EVTPART1\
ota_update:textField $DEVICETOPIC/bridge/ota_update/update $EVTPART1\
ota_update_check:textField $DEVICETOPIC/bridge/ota_update/check $EVTPART1\
y_device_setting:textField $DEVICETOPIC/$EVTPART1/set {"$EVTPART2": "$EVTPART3"}\
x_bind:textField $DEVICETOPIC/bridge/bind/$EVTPART1 $EVTPART2\
x_bind_unbind:textField $DEVICETOPIC/bridge/unbind/$EVTPART1 $EVTPART2\
x_device_options:textField $DEVICETOPIC/bridge/config/device_options {"friendly_name":"$EVTPART1","options": {"$EVTPART2": "$EVTPART3"}}\
x_group_add_to:textField $DEVICETOPIC/bridge/group/$EVTPART1/add $EVTPART2\
x_group_rm_from:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove $EVTPART2\
x_group_rm_from_all:textField $DEVICETOPIC/bridge/group/$EVTPART1/remove_all $EVTPART2\
x_group_add_group:textField $DEVICETOPIC/bridge/config/add_group $EVTPART1\
x_group_rm_group:textField $DEVICETOPIC/bridge/config/remove_group $EVTPART1\
z_elapsed:textField $DEVICETOPIC/bridge/config/elapsed $EVTPART1\
z_last_seen:disable,ISO_8601,epoch,ISO_8601_local $DEVICETOPIC/bridge/config/last_seen $EVTPART1\
z_ban:textField $DEVICETOPIC/bridge/config/ban $EVTPART1\
z_rename:textField $DEVICETOPIC/bridge/config/rename {"old":"$EVTPART1","new":"$EVTPART2"}\
z_reset_CC:noArg $DEVICETOPIC/bridge/config/reset
attr MQTT2_z2mdocker setStateList on offZitat von: Beta-User am 17 Februar 2022, 06:44:40
Hmm, anscheinend hatte ich die Frage nicht spezifisch genug gestellt:
Auf welchen Pfad wird _jeweils_ die Antwort gesendet?
Der timeout titt auf weil die Antwort jeweils
- vielleicht zu spät kommt (aber uU. auf den richtigen Topic), oder
- auf einen anderen Topic kommt (das scheint bei den networkmap-Anfragen der Fall zu sein, aus dem einen gezeigten Topic läßt sich aber nicht ableiten, welche von beiden das war).
Da in der Doku auf die Schnelle nichts zu finden war, wäre es hilfreich, wenn jemand dazu eine etwas spezifischere Auskunft - getrennt für alle drei Abfragen - geben könnte...
Hmm, irgendwie paßt diese Aussage nach meinem Weltbild nicht zu der Info von neulich, dass du auf eine der networkmap-Anfragen ein neues Gerät angelegt bekommen hast mit dieser readingList:
readingList zigbee2mqtt/bridge/response/networkmap:.* networkmapDanach war ich davon ausgegangen, dass eine Anfrage rausgeht, die Antwort aber auf einem anderen Pfad kommt als bisher bekannt.
Aber da es anscheinend keine weiteren Betroffenen gibt oder das Thema auch nicht so wichtig zu sein scheint, sollten wir es erst mal dabei belassen.
Früher würde angefragt über das Topic
$DEVICETOPIC/bridge/networkmap
Beim aktuellem Stand wäre es
$DEVICETOPIC/bridge/request/networkmap
Für devicelist soll beim aktuellen Stand gelten
$DEVICETOPIC/bridge/devices
Also demnach in attrTemplate-Form so?
attr DEVICE getList\
devicelist:noArg log $\DEVICETOPIC/bridge/config/devices/get\
networkmap_raw:noArg raw $\DEVICETOPIC/bridge/request/networkmap raw\
networkmap_graphviz:noArg graphviz $\DEVICETOPIC/bridge/request/networkmap graphviz
attr DEVICE readingList\
$\DEVICETOPIC/bridge/state:.* state\
$\DEVICETOPIC/bridge/config/devices:.* {}\
$\DEVICETOPIC/bridge/config/log_level:.* log_level\
$\DEVICETOPIC/bridge/config/permit_join:.* permit_join\
$\DEVICETOPIC/bridge/config/rename:.* { json2nameValue($EVENT, 'rename_') }\
$\DEVICETOPIC/bridge/config:.* { json2nameValue($EVENT) }\
$\DEVICETOPIC/bridge/log:.*\"type\".\"devices\".\"message\".* devices\
$\DEVICETOPIC/bridge/log:.* log\
$\DEVICETOPIC/bridge/logging:.* { json2nameValue($EVENT,'log_') }\
$\DEVICETOPIC/bridge/networkmap:.* {}\
$\DEVICETOPIC/bridge/response/networkmap/graphviz:.* graphviz\
$\DEVICETOPIC/bridge/response/networkmap/raw:.* raw\
$\DEVICETOPIC/bridge/devices:.* devices\
$\DEVICETOPIC/bridge/info:.* info\
$\DEVICETOPIC/bridge/groups:.* groups\
$\DEVICETOPIC/bridge/event:.* { json2nameValue($EVENT) }\
$\DEVICETOPIC/bridge/extensions:.* extensions
Zitat von: Beta-User am 17 Februar 2022, 10:06:41
Hmm, irgendwie paßt diese Aussage nach meinem Weltbild nicht zu der Info von neulich, dass du auf eine der networkmap-Anfragen ein neues Gerät angelegt bekommen hast mit dieser readingList:
readingList zigbee2mqtt/bridge/response/networkmap:.* networkmapDanach war ich davon ausgegangen, dass eine Anfrage rausgeht, die Antwort aber auf einem anderen Pfad kommt als bisher bekannt.
Aber da es anscheinend keine weiteren Betroffenen gibt oder das Thema auch nicht so wichtig zu sein scheint, sollten wir es erst mal dabei belassen.
Ah njein. Ich hatte es händisch über das zigbee2mqtt frontend ausgelöst. Dabei wurde die Antwort dann als neues Device angelegt
...diese Bruchstücke helfen nur bedingt weiter, daher hatte ich versucht, das unter Berücksichtigung der Infos von @OdfFhem in meinem letzten Post zu konsolidieren.
Ist es denn so schwierig, das auf das eigene Umfeld anzupassen und dann eine Rückmeldung zu geben, ob das so klappt bzw. wie es klappt und anzupassen ist?
...
ich hatte die Antwort von OdfFhem überlesen - sorry.
Also wenn ich nun über mein Bridge die getlist auf devicelist:noArg log $DEVICETOPIC/bridge/devices
networkmap_raw:noArg raw $DEVICETOPIC/bridge/request/networkmap raw
networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/request/networkmap graphviz
angepasst habe, wird bei networkmap der Scan korrekt ausgelöst
die Antwort kommt über zigbee2mqtt/bridge/response/networkmap leider wieder bei dem falschen Device an.
Dann habe ich die Readinglist Einträge von dem "falschen" Device auf meins übersetzt:
$DEVICETOPIC/bridge/response/networkmap:.* networkmap
$DEVICETOPIC/bridge/response/options:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/response/device/rename:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/response/device/ota_update/check:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/response/device/ota_update/update:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/response/group/remove:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/response/group/add:.* { json2nameValue($EVENT) }
$DEVICETOPIC/bridge/response/group/members/add:.* { json2nameValue($EVENT) }
Der Timeoutfehler kommt trotzdem nach kurzer Zeit
request: 11:15:51
response: 11:16:53
Das Reading ist nun korrekt am richtigen Device.
bei Graphwiz das gleiche.
Devicelist will leider nicht funktionieren.
Hmmm, wie nach der etwas zögerlichen Info von OdfFhem eigentlich nicht anders zu erwarten war, scheint es keine getrennten Topics mehr zu geben für Antworten auf Anfragen für "raw"- und "graphviz"-maps. Soweit so unklar...
Bedeutet...? Neues Reading? Oder eines der beiden bestehenden hernehmen? Braucht es Änderungen wegen der Map-Erstellung in FHEMWEB?
Werde jetzt erst mal bei Gelegenheit eine Zwischenlösung ins svn schubsen.
Was "devicelist" angeht: von der zigbee2mqtt-UI aus die Anfrage anschubsen, um den neuen Topic zu ermitteln, und schauen, wohin die Antwort kommt. getList und readingList entsprechend ändern und hier das Ergebnis zeigen.
Ich selbst verwende produktiv kein allerneuestes zigbee2mqtt ... daher nur Doku "gelesen" ...
Ich kann aber heute Abend mal das Testsystem "analysieren" - sofern noch Infos fehlen ...
:) Danke für die Erhellung des Hintergrunds des etwas kryptischen Hinweises ::) .
Das Ganze eilt ja nicht, allerdings versuche ich bekanntermaßen, die attrTemplate jeweils auf den gerade aktuellen Stand der firmware/Software-Version der Gegenseite anzupassen, so dass derjenige, der irgendwas updated dann eben auch auf derm FHEM-Seite einen funktionsfähigen Stand hat. Von daher wäre es natürlich schön, wenn ich den Punkt hier irgendwann wieder für mich (bzw. für die davon profitierenden User) schließen könnte, ohne tiefer Nachgrübeln zu müssen ;D .
devicelist kann wohl erstmal raus: https://github.com/Koenkk/zigbee2mqtt/discussions/11294
ist die Zwischenlösung zum Test schon im SVN? Dann könnte ich deine Idee mal bei mir testen:
Ob der Timeout noch kommt und ob eine Visualiserung zu sehen ist.
Zitat von: masterpete23 am 17 Februar 2022, 14:08:52
devicelist kann wohl erstmal raus: https://github.com/Koenkk/zigbee2mqtt/discussions/11294 (https://github.com/Koenkk/zigbee2mqtt/discussions/11294)
OK, dann werfe ich das mal aus der getList.
Zitat
ist die Zwischenlösung zum Test schon im SVN? Dann könnte ich deine Idee mal bei mir testen:
Ob der Timeout noch kommt und ob eine Visualiserung zu sehen ist.
Nein, damit wollte ich warten, bis weitere Rückmeldung kam. Die "Vertemplatung" ist ja kein Hexenwerk.
Jetzt geht es eigentlich nur darum, ob mit der neuen getList dann die Daten an denselben Topic gesendet werden oder ob das nach wie vor zwei Topics sind (und welcher Typ nach bisherigen Maßsstäben jetzt ggf. unter der Bezeichnung networkmap geliefert wird, falls es verschiedene sind).
Bei der Visualisierung ist mir grade nicht gegenwärtig, wie Rudi das gebastelt hatte, also ob eine bestimmte Datenstruktur unter einem bestimmten Readingnamen erwartet wird (ich meine, es müßte die graphviz-Variante gewesen sein).
Auszug aus getList:
networkmap_raw:noArg raw $DEVICETOPIC/bridge/request/networkmap raw
networkmap_graphviz:noArg graphviz $DEVICETOPIC/bridge/request/networkmap graphviz
Auszug aus readingList:
$DEVICETOPIC/bridge/response/networkmap:.* { my $type = $EVENT =~ m/.*,"type":"(raw|graphviz)",.*/ ? $1 : 'networkmap'; $EVENT =~ m/{"data":\{.*"value":"?(.*[^"])"?\},"status":"ok"\}/ ? { $type=>$1 } : {} }
$DEVICETOPIC/bridge/request/networkmap:.* {}
- ermittelt den type der Antwort und speichert diesen in $type
- extrahiert den Wert von value
- ist ein passender value vorhanden, dann Speicherung unter $type
* networkmap_raw funktioniert
* networkmap_graphviz funktioniert im Grunde auch, jedoch ist der hinterlegte Wert im Reading nicht nutzbar.
- bekommt man keinen Timeout, dann sieht man im aufgeblendeten Dialog:
digraph G { node[shape=record]; "0x00124b00258 ...
Kopiert man den gesamten Inhalt ohne das führende graphviz, dann kann man die Geräte visualisieren.
- Im Reading steht Folgendes:
digraph G {\nnode[shape=record];\n \"0x00124b00258 ...
Zeilenumbrüche und Anführungszeichen sind maskiert - man kann nicht (einfach) die Geräte visualisieren.
- wie wird man auf einfach(st)e Art die Maskierung los ?
...unschön....
Wenn ich Rudi noch richtig in Erinnerung habe, war damals die Reaktion auf das irgendwann aufgetauchte "raw": "wenn ich das früher gewußt hätte..." Ergo ist es vermutlich einfacher, den Grafikerstellungscode mal anzusehen und zu versuchen, den auf raw umzubiegen. Dann wären wir vermutlich weniger abhängig von dem, was irgendjemand meint "verbessern" zu müssen...
Werde halt bei Gelegenheit mal den "ist"-Stand einpflegen, mal schauen, ob sich jemand findet, der sich das antut...
Zitat von: OdfFhem am 17 Februar 2022, 20:41:29
- wie wird man auf einfach(st)e Art die Maskierung los ?
Hmm, der Code für die Visualisierung ist in MQTT2_DEVICE zu finden: MQTT2_DEVICE_nlData(). Vielleicht kann man da am Anfang eine Säuberungsfunktion einbauen?
Ansonsten wäre es wie gesagt vermutlich zielführender, den Teil so umzubauen, dass er mit "raw"-Input klarkommt.
Für die Anzeige der Images ist übrigens auch "devices" erforderlich; falls nicht nur die Abfrageoption entfallen ist, sondern der ganze Inhalt, klappt der Teil schon mal nicht mehr...
Zitat- wie wird man auf einfach(st)e Art die Maskierung los ?
Alle Daten zum Reproduzieren hier anhaengen, und nett fragen, ob die Funktion fuer diese Variante gefixt werden koennte.
type und value ermittle ich aktuell über einen regulären Ausdruck - werden also nur "ausgeschnitten" und nicht konvertiert.
Für type egal, da nur 1 Wort; bei value führt dies nicht immer zum gewünschten Format.
- graphviz liefert als value einen für JSON konvertierten String, daher die Maskierungen
$DEVICETOPIC/bridge/response/networkmap {"data":{"routes":false,"type":"graphviz","value":"digraph G {\nnode[shape=record];\n \"0x00124b0025e70bd8\" [style=\"bold, filled\", fillcolor=\"#e04e5d\", fontcolor=\"#ffffff\", label=\"{Coordinator|0x00124b0025e70bd8 (0x0000)|0 seconds ago}\"];\n \"0x0017880103abf482\" [style=\"rounded, dashed, filled\", fillcolor=\"#fff8ce\", fontcolor=\"#000000\", label=\"{motionSensor2|0x0017880103abf482 (0x1b0b)|Philips Hue motion sensor (9290012607)|1 minute, 8 seconds ago}\"];\n \"0x0017880103abf482\" -> \"0x00124b0025e70bd8\" [penwidth=1, weight=0, color=\"#994444\", label=\"143\"]\n}"},"status":"ok"}
- raw liefert als value ein JSON-Objekt
$DEVICETOPIC/bridge/response/networkmap {"data":{"routes":false,"type":"raw","value":{"links":[{"depth":1,"linkquality":135,"lqi":135,"relationship":1,"routes":[],"source":{"ieeeAddr":"0x0017880103abf482","networkAddress":6923},"sourceIeeeAddr":"0x0017880103abf482","sourceNwkAddr":6923,"target":{"ieeeAddr":"0x00124b0025e70bd8","networkAddress":0},"targetIeeeAddr":"0x00124b0025e70bd8"}],"nodes":[{"definition":null,"failed":[],"friendlyName":"Coordinator","ieeeAddr":"0x00124b0025e70bd8","lastSeen":null,"networkAddress":0,"type":"Coordinator"},{"definition":{"description":"Hue motion sensor","model":"9290012607","supports":"temperature, occupancy, battery, illuminance_lux, illuminance, motion_sensitivity, led_indication, occupancy_timeout, linkquality","vendor":"Philips"},"friendlyName":"motionSensor2","ieeeAddr":"0x0017880103abf482","lastSeen":1645255436416,"manufacturerName":"Philips","modelID":"SML001","networkAddress":6923,"type":"EndDevice"}]}},"status":"ok"}
Um anzutesten, ob ich die Werte nicht besser von json2nameValue ermitteln lassen kann, habe ich Folgendes ausprobiert:
zigbee4mqtt/bridge/response/networkmap:.* { my %j2v = %{json2nameValue($EVENT,"",{"data_type"=>"type","data_value"=>"value"},".*(type|value).*")}; return { $j2v{'type'}=>$j2v{'value'} }; }
Ergebnis war, dass für graphviz tatsächlich der bereinigte Wert im Reading landete und somit auch die neighbor map angezeigt werden konnte. Wert vom Reading kann in dieser Form auch für externe "Apps" genutzt werden.
Für raw kam es zu einem Fehler, da in der Antwort zwar ein value vorhanden ist, aber dessen Wert wiederum ein eigenes JSON-Objekt darstellt - folglich existiert value bei Anwendung von json2nameValue nicht wirklich ...
@rudolfkoenig
Gibt es bereits bzw. besteht die Chance auf eine Möglichkeit, die Tiefe der "Auflösung" zu begrenzen (value also nicht mehr weiter aufbröseln) ?
@Beta-User
Bzgl. devices steht bei mir autom. in der readingList:
$DEVICETOPIC/bridge/devices:.* devices
Information steht lt. Doku ständig auf dem MQTT-Server bereit und wird beim MQTT-Anmelden bzw. bei jeder Änderung von Gerätedefinitionen veröffentlicht
$DEVICETOPIC/bridge/devices [{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce"],"output":["ssIasZone","ssIasWd"]},"configured_reportings":[],"scenes":[]},"110":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"12":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"13":{"bindings":[],"clusters":{"input":["genOta"],"output":[]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"3":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"4":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"47":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"5":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"6":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"8":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Coordinator","ieee_address":"0x00124b0025e70bd8","interview_completed":true,"interviewing":false,"network_address":0,"supported":false,"type":"Coordinator"},{"date_code":"20190219","definition":{"description":"Hue motion sensor","exposes":[{"access":1,"description":"Measured temperature value","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Indicates whether the device detected occupancy","name":"occupancy","property":"occupancy","type":"binary","value_off":false,"value_on":true},{"access":1,"description":"Remaining battery in %","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Measured illuminance in lux","name":"illuminance_lux","property":"illuminance_lux","type":"numeric","unit":"lx"},{"access":1,"description":"Raw measured illuminance","name":"illuminance","property":"illuminance","type":"numeric"},{"access":7,"name":"motion_sensitivity","property":"motion_sensitivity","type":"enum","values":["low","medium","high"]},{"access":7,"description":"Blink green LED on motion detection","name":"led_indication","property":"led_indication","type":"binary","value_off":false,"value_on":true},{"access":7,"name":"occupancy_timeout","property":"occupancy_timeout","type":"numeric","unit":"second","value_max":65535,"value_min":0},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"9290012607","options":[{"access":2,"description":"Number of digits after decimal point for temperature, takes into effect on next report of device.","name":"temperature_precision","property":"temperature_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the temperature value (absolute offset), takes into effect on next report of device.","name":"temperature_calibration","property":"temperature_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for illuminance, takes into effect on next report of device.","name":"illuminance_precision","property":"illuminance_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the illuminance value (percentual offset), takes into effect on next report of device.","name":"illuminance_calibration","property":"illuminance_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for illuminance_lux, takes into effect on next report of device.","name":"illuminance_lux_precision","property":"illuminance_lux_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the illuminance_lux value (percentual offset), takes into effect on next report of device.","name":"illuminance_lux_calibration","property":"illuminance_lux_calibration","type":"numeric"}],"supports_ota":true,"vendor":"Philips"},"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic"],"output":["genBasic","genIdentify","genGroups","genOnOff","genLevelCtrl","lightingColorCtrl","genScenes"]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[{"cluster":"genPowerCfg","target":{"endpoint":1,"ieee_address":"0x00124b0025e70bd8","type":"endpoint"}},{"cluster":"msIlluminanceMeasurement","target":{"endpoint":1,"ieee_address":"0x00124b0025e70bd8","type":"endpoint"}},{"cluster":"msTemperatureMeasurement","target":{"endpoint":1,"ieee_address":"0x00124b0025e70bd8","type":"endpoint"}},{"cluster":"msOccupancySensing","target":{"endpoint":1,"ieee_address":"0x00124b0025e70bd8","type":"endpoint"}}],"clusters":{"input":["genBasic","genPowerCfg","genIdentify","msOccupancySensing","msIlluminanceMeasurement","msTemperatureMeasurement"],"output":["genOta"]},"configured_reportings":[{"attribute":"batteryPercentageRemaining","cluster":"genPowerCfg","maximum_report_interval":62000,"minimum_report_interval":3600,"reportable_change":0},{"attribute":"occupancy","cluster":"msOccupancySensing","maximum_report_interval":3600,"minimum_report_interval":0,"reportable_change":0},{"attribute":"measuredValue","cluster":"msTemperatureMeasurement","maximum_report_interval":3600,"minimum_report_interval":10,"reportable_change":100},{"attribute":"measuredValue","cluster":"msIlluminanceMeasurement","maximum_report_interval":3600,"minimum_report_interval":10,"reportable_change":5}],"scenes":[]}},"friendly_name":"motionSensor2","ieee_address":"0x0017880103abf482","interview_completed":true,"interviewing":false,"manufacturer":"Philips","model_id":"SML001","network_address":6923,"power_source":"Battery","software_build_id":"6.1.1.27575","supported":true,"type":"EndDevice"}]
...demnach sollte man unterschiedlich vorgehen können, wenn
- nicht ok => nichts machen;
- wenn raw => der code lt. aktuellem attrTemplate
- wenn graphviz => die Bereinigungslogik
- sonst: "Ersatzreading"
Fisch geputzt?
Solche Konstruktionen gibt es schon ein paar, das könnte schon klappen, sprengt halt aber fast den Rahmen "des Üblichen".