Moin zusammen,
ich habe hier zwei Shelly Smoke für meinen "Zoo" bekommen. Einen habe ich jetzt mit MQTT in Fhem eingebunden.
Ein List zeigt mir: Internals:
CID shellyplussmoke_80646fd06e08
DEF shellyplussmoke_80646fd06e08
FUUID 63f0cfa8-f33f-8a87-1e3f-0020801d6af321f5
IODev myBroker
NAME KG_HK_Shellyplussmoke
NR 1217
STATE ???
TYPE MQTT2_DEVICE
READINGS:
2023-02-26 08:41:01 IODev myBroker
2023-02-25 11:22:21 alarm false
2023-02-25 11:22:22 battery_V 2.99
2023-02-25 11:22:22 battery_percent 97
2023-02-25 11:22:17 ble {}
2023-02-25 11:22:21 cfg_rev 6
2023-02-25 11:22:17 connected true
2023-02-25 11:22:22 dst shellyplussmoke-80646fd06e08/events
2023-02-25 11:22:17 errors_1 read
2023-02-25 11:22:21 fs_free 122880
2023-02-25 11:22:21 fs_size 458752
2023-02-25 11:22:22 id 0
2023-02-25 11:22:21 kvs_rev 0
2023-02-25 11:22:21 mac 80646FD06E08
2023-02-25 11:22:22 method NotifyStatus
2023-02-25 11:22:21 mute false
2023-02-25 11:22:17 online true
2023-02-25 11:22:17 params_cloud_connected false
2023-02-25 11:22:22 params_devicepower_0_battery_V 2.99
2023-02-25 11:22:22 params_devicepower_0_battery_percent 97
2023-02-25 11:22:17 params_devicepower_0_errors_1 read
2023-02-25 11:22:22 params_devicepower_0_id 0
2023-02-25 11:22:21 params_events_1_component sys
2023-02-25 11:22:21 params_events_1_event sleep
2023-02-25 11:22:21 params_events_1_ts 1677320541.96
2023-02-25 11:22:17 params_mqtt_connected true
2023-02-25 11:22:21 params_smoke_0_alarm false
2023-02-25 11:22:17 params_smoke_0_id 0
2023-02-25 11:22:17 params_smoke_0_mute false
2023-02-25 11:22:17 params_sys_cfg_rev 6
2023-02-25 11:22:17 params_sys_fs_free 126976
2023-02-25 11:22:17 params_sys_fs_size 458752
2023-02-25 11:22:17 params_sys_kvs_rev 0
2023-02-25 11:22:17 params_sys_mac 80646FD06E08
2023-02-25 11:22:17 params_sys_ram_free 167292
2023-02-25 11:22:17 params_sys_ram_size 236072
2023-02-25 11:22:17 params_sys_restart_required false
2023-02-25 11:22:17 params_sys_uptime 1
2023-02-25 11:22:17 params_sys_wakeup_period 86400
2023-02-25 11:22:17 params_sys_wakeup_reason_boot poweron
2023-02-25 11:22:21 params_sys_wakeup_reason_cause status_update
2023-02-25 11:22:17 params_sys_webhook_rev 0
2023-02-25 11:22:22 params_ts 1677320542.43
2023-02-25 11:22:17 params_wifi_rssi -17
2023-02-25 11:22:17 params_wifi_ssid Sinclair
2023-02-25 11:22:17 params_wifi_sta_ip 192.168.179.44
2023-02-25 11:22:17 params_wifi_status got ip
2023-02-25 11:22:17 params_ws_connected false
2023-02-25 11:22:21 ram_free 166656
2023-02-25 11:22:21 ram_size 236032
2023-02-25 11:22:21 restart_required false
2023-02-25 11:22:17 rssi -17
2023-02-25 11:22:22 src shellyplussmoke-80646fd06e08
2023-02-25 11:22:17 ssid Sinclair
2023-02-25 11:22:17 sta_ip 192.168.179.44
2023-02-25 11:22:17 status got ip
2023-02-25 11:22:21 time 11:22
2023-02-25 11:22:21 unixtime 1677320541
2023-02-25 11:22:21 uptime 5
2023-02-25 11:22:21 wakeup_period 86400
2023-02-25 11:22:21 wakeup_reason_boot poweron
2023-02-25 11:22:21 wakeup_reason_cause status_update
2023-02-25 11:22:21 webhook_rev 0
Attributes:
DbLogExclude .*
event-on-change-reading .*
icon secur_smoke_detector
readingList shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/online:.* online
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/status/ble:.* ble
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/status/cloud:.* { json2nameValue($EVENT) }
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/status/devicepower_0:.* { json2nameValue($EVENT) }
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/status/mqtt:.* { json2nameValue($EVENT) }
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/status/smoke_0:.* { json2nameValue($EVENT) }
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/status/sys:.* { json2nameValue($EVENT) }
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/status/wifi:.* { json2nameValue($EVENT) }
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/status/ws:.* { json2nameValue($EVENT) }
shellyplussmoke_80646fd06e08:shellyplussmoke-80646fd06e08/events/rpc:.* { json2nameValue($EVENT) }
Leider ist der in der ersten Version angekündigte Feuchtigkeits und Temperatursensor nicht zu sehen.... Sieht jemand eine Möglichkeit den Melder mit FHEM auszulösen, oder nach Alarm abzuschalten?
Gruss
Enno
Laut der Shelly-API-Dokumentation kannst du den Alarm grds. per http-Request ausschalten:
https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Smoke
Dass die hier benannte Methode Smoke.Mute auch in MQTT vorhanden ist, ergibt sich aus der Dokumentation leider nicht. Ausprobieren ...