Ich habe hier einen Shelly pro 1 PM und komme ein einer Stelle nicht weiter, die Werte bekomme ich mittlerweile, allerdings schaffe ich es nicht den Shelly per FHem zu schalten:
Die Befehle:
http://192.168.0.76/rpc/Switch.Set?id=0&on=false
http://192.168.0.76/rpc/Switch.Toggle?id=0
funktionieren aber.
Irgendwie steh ich auf den Schlauch wie ich den Shelly jetzt noch schaltbar bekommen kann. Ich möchte auch bei MQTT bleiben.
Vielen Dank fürs drüber schauen.
define Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac MQTT2_DEVICE shellypro1pm_30c6f789dfac
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac devicetopic shellypro1pm_30c6f789dfac:shellypro1pm-30c6f789dfac
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac genericDeviceType switch
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac group Sensor Strom
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac jsonMap switch_0_output:state\
switch_0_aenergy_total:energy_total\
switch_0_apower:power\
switch_0_temperature_tC:temperature
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac model shellyPlus_1pm
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac readingList $DEVICETOPIC/events/rpc:.* { json2nameValue($EVENT, 'rpc_', $JSONMAP) }\
$DEVICETOPIC/status/switch_0:.* { json2nameValue($EVENT, 'switch_0_', $JSONMAP) }\
$DEVICETOPIC/online:.* online\
$DEVICETOPIC/status/mqtt:.* { json2nameValue($EVENT, 'mqtt_', $JSONMAP) }
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac room Solar
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac setList toggle:noArg $DEVICETOPIC/rpc {"id":1,"src":"fhem2shelly","method":"Switch.Toggle","params": {"id":0}}\\
off:noArg $DEVICETOPIC/rpc {"id":1"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":false}}\\
on:noArg $DEVICETOPIC/rpc {"id":1,"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":true}}
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac stateFormat power W (max: powerMax)<br>Erzeugung Tag: statConsumptionDay<br>Erzeugung Ges: consumption<br> Vortag: statConsumptionDayLast
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac userReadings consumption { sprintf("%.2f",((ReadingsVal("$name","energy_total",0))/60/1000));; }, powerMax {minNum(ReadingsVal("$name","powerMax","0"), ReadingsVal("$name","power","0"))}
# CID shellypro1pm_30c6f789dfac
# DEF shellypro1pm_30c6f789dfac
# FUUID 63ef83af-f33f-49d6-325a-33da15896b513388
# IODev MQTT
# LASTInputDev MQTT
# MQTT_CONN MQTT_192.168.0.76_64366
# MQTT_MSGCNT 1117
# MQTT_TIME 2023-02-17 16:27:26
# MSGCNT 1117
# NAME Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac
# NR 882
# STATE -71.6 W (max: -105.5)<br>Erzeugung Tag: 0.00<br>Erzeugung Ges: 0.00<br> Vortag: statConsumptionDayLast
# TYPE MQTT2_DEVICE
# eventCount 1117
# .DT:
# DEVICETOPIC shellypro1pm_30c6f789dfac:shellypro1pm-30c6f789dfac
# .attraggr:
# .attrminint:
# .userReadings:
# HASH(0x5587a0576750)
# HASH(0x5587a05804e0)
# Helper:
# DBLOG:
# consumption:
# logdb:
# TIME 1676647646.46231
# VALUE 0.00
# energy_total:
# logdb:
# TIME 1676647646.37146
# VALUE 277.468
# power:
# logdb:
# TIME 1676647646.37146
# VALUE -71.6
# powerMax:
# logdb:
# TIME 1676647646.46231
# VALUE -105.5
# statConsumptionDay:
# logdb:
# TIME 1676647646.46231
# VALUE 0.00
# temperature:
# logdb:
# TIME 1676647646.37146
# VALUE 33.7
# JSONMAP:
# switch_0_aenergy_total energy_total
# switch_0_apower power
# switch_0_output state
# switch_0_temperature_tC temperature
# READINGS:
# 2023-02-17 16:22:14 IODev MQTT
# 2023-02-17 16:27:26 consumption 0.00
# 2023-02-17 16:27:26 energy_total 277.468
# 2023-02-17 16:22:42 mqtt_connected true
# 2023-02-17 16:22:42 online true
# 2023-02-17 16:27:26 power -71.6
# 2023-02-17 16:27:26 powerMax -105.5
# 2023-02-17 16:27:26 rpc_dst shellypro1pm-30c6f789dfac/events
# 2023-02-17 16:27:26 rpc_method NotifyStatus
# 2023-02-17 16:22:42 rpc_params_mqtt_connected true
# 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_by_minute_1 1169.782
# 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_by_minute_2 1203.853
# 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_by_minute_3 1234.172
# 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_minute_ts 1676647619
# 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_total 276.961
# 2023-02-17 16:27:26 rpc_params_switch_0_apower -71.6
# 2023-02-17 16:27:26 rpc_params_switch_0_current 0.378
# 2023-02-17 16:27:26 rpc_params_switch_0_id 0
# 2023-02-17 16:27:26 rpc_params_ts 1676647646.22
# 2023-02-17 16:27:26 rpc_src shellypro1pm-30c6f789dfac
# 2023-02-17 16:27:26 statConsumption Hour: 0.00 Day: 0.00 Month: 0.00 Year: 0.00 (since: )
# 2023-02-17 16:27:26 statConsumptionDay 0.00
# 2023-02-17 16:27:26 statConsumptionHour 0.00
# 2023-02-17 16:27:26 statConsumptionMonth 0.00
# 2023-02-17 16:27:26 statConsumptionYear 0.00
# 2023-02-17 16:27:26 state true
# 2023-02-17 16:27:26 switch_0_aenergy_by_minute_1 507.669
# 2023-02-17 16:27:26 switch_0_aenergy_by_minute_2 1169.782
# 2023-02-17 16:27:26 switch_0_aenergy_by_minute_3 1203.853
# 2023-02-17 16:27:26 switch_0_aenergy_minute_ts 1676647645
# 2023-02-17 16:27:26 switch_0_current 0.378
# 2023-02-17 16:27:26 switch_0_id 0
# 2023-02-17 16:27:26 switch_0_pf -0.76
# 2023-02-17 16:27:26 switch_0_source WS_in
# 2023-02-17 16:27:26 switch_0_temperature_tF 92.7
# 2023-02-17 16:27:26 switch_0_voltage 236.9
# 2023-02-17 16:27:26 temperature 33.7
# helper:
# _98_statistics Statistik
# hmccu:
#
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac -71.6 W (max: -105.5)<br>Erzeugung Tag: 0.00<br>Erzeugung Ges: 0.00<br> Vortag: statConsumptionDayLast
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:22:14 IODev MQTT
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 consumption 0.00
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 energy_total 277.468
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:22:42 mqtt_connected true
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:22:42 online true
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 power -71.6
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 powerMax -105.5
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 rpc_dst shellypro1pm-30c6f789dfac/events
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 rpc_method NotifyStatus
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:22:42 rpc_params_mqtt_connected true
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_by_minute_1 1169.782
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_by_minute_2 1203.853
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_by_minute_3 1234.172
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_minute_ts 1676647619
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:00 rpc_params_switch_0_aenergy_total 276.961
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 rpc_params_switch_0_apower -71.6
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 rpc_params_switch_0_current 0.378
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 rpc_params_switch_0_id 0
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 rpc_params_ts 1676647646.22
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 rpc_src shellypro1pm-30c6f789dfac
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 statConsumption Hour: 0.00 Day: 0.00 Month: 0.00 Year: 0.00 (since: )
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 statConsumptionDay 0.00
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 statConsumptionHour 0.00
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 statConsumptionMonth 0.00
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 statConsumptionYear 0.00
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 state true
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_aenergy_by_minute_1 507.669
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_aenergy_by_minute_2 1169.782
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_aenergy_by_minute_3 1203.853
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_aenergy_minute_ts 1676647645
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_current 0.378
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_id 0
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_pf -0.76
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_source WS_in
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_temperature_tF 92.7
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 switch_0_voltage 236.9
setstate Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 16:27:26 temperature 33.7
Zitat von: doman75 am 17 Februar 2023, 16:30:49
attr Stromerzeugung_MQTT2_shellypro1pm_30c6f789dfac devicetopic shellypro1pm_30c6f789dfac:shellypro1pm-30c6f789dfac
Ich bin mir nicht sicher, aber das sieht für mich komisch aus. Ich kenne devicetopics nur ohne Doppelpunkt und höchstens mit / als Baumtrenner.
Das setlist-Attribut sieht fast gut aus, die ID für das Parameterset ist anders (nicht zu verwechseln mit der ID des zu schaltenden Kanals).
Edit: Zum Vergleich, bei meinem 3 Pro ist das ein Teil der Definition:
defmod GAR_Deckenlicht MQTT2_DEVICE GAR_Shelly
attr GAR_Deckenlicht devicetopic shellies/GAR_Shelly
attr GAR_Deckenlicht setList toggle:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Toggle","params": {"id":0}}\
off:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":false}}\
on:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":true}}\
naja wenn readinglist automatisch erstellt wird schreibt er ja auch
" shellypro1pm_30c6f789dfac:shellypro1pm-30c6f789dfac/events/rpc:.* { json2nameValue($EVENT, 'rpc_', $JSONMAP) }"
rein, und vor dem /events steht doch das Devicetopic oder? Ich habe jetzt mal den : durch / ersetzt das bringt aber nix
Das Attribut readingList enthält auch was ganz anderes als devicetopic.
Nein, es steht im Attribut readingList vor dem Doppelpunkt das Reading und noch dem Doppelpunkt das Topic und die Inhaltsdaten bzw. was damit geschehen soll.
Das einfach zu ersetzen bringt auch nichts, es muss zu deiner Topic-Konfiguration passen. Wenn du keinen Baum angelegt hast, dann wird das shellypro1pm_30c6f789dfac als devicetopic reichen.
Ich habe in der Shelly-Konfiguration das MQTT-Präfix als "shellies/GAR_Shelly" benannt. Und alle anderen Shellys haben auch das "shellies/" vor dem eigentlichen Namen, so finde ich sie alle unter diesem Baum.
Wenn ich das DeviceTopic ändere werden auch keine Werte mehr eingelesen. Die Einstellung auf dem 1Pro habe ich unverändert gelassen, siehe Screenshot
Somit lautet dein devicetopic
shellypro1pm-30c6f789dfac
off:noArg shellypro1pm_30c6f789dfac/rpc {"id":0"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":false}}
ich habe das jetzt mal direkt so bei setlist eingegeben, der shelly wird aber nicht ausgeschaltet
Zitat[...] und vor dem /events steht doch das Devicetopic oder?
Nein, die automatisch erzeugten readingList Zeilen sind der Form
<ClientID>:<Topic>:<Message>:.* { json2NameValue... }Dabei ist <ClientID>: optional.
Bei Shelly wird ClientId und MQTT-Prefix gleich vorbelegt.
Das gezeigte devicetopic Attribut ist falsch (wie Ralli das schon erwaehnt hatte).
Wurde das Attribut vom attrTemplate so angelegt?
Ich weiß nicht genau warum jetzt geht es, ich habe als template nochmal shellyplus_1pm ausgewählt, danach verliert der der Shelly seine WLAn verbindung, nach abklemmen vor Ort und wieder anklemmen, ist er wieder im WLAN und mit den folgenden Code kann ich ihn nun auch ausschalten.
define MQTT2_shellypro1pm_30c6f789dfac MQTT2_DEVICE shellypro1pm_30c6f789dfac
attr MQTT2_shellypro1pm_30c6f789dfac alias Solar_ShellyPro1PM (Garagendach)
attr MQTT2_shellypro1pm_30c6f789dfac autocreate 0
attr MQTT2_shellypro1pm_30c6f789dfac devStateIcon ON:FS20.on OFF:FS20.off An:FS20.on Aus:FS20.off
attr MQTT2_shellypro1pm_30c6f789dfac devicetopic shellypro1pm-30c6f789dfac
attr MQTT2_shellypro1pm_30c6f789dfac eventMap on:An off:Aus
attr MQTT2_shellypro1pm_30c6f789dfac getList in_mode:noArg in_mode $DEVICETOPIC/rpc {"id": 1,"src":"$DEVICETOPIC", "method": "Switch.GetConfig", "params": {"id": 0}}
attr MQTT2_shellypro1pm_30c6f789dfac jsonMap switch_state:state switch_temperature_tC:temperature switch_temperature_tF:0 params_wifi_sta_ip:ip params_switch_0_temperature_tC:temperature params_switch_0_temperature_tF:0 req_result_in_mode:in_mode
attr MQTT2_shellypro1pm_30c6f789dfac model shellyPlus_1
attr MQTT2_shellypro1pm_30c6f789dfac readingList $DEVICETOPIC/online:.* online\
$DEVICETOPIC/events/rpc:.* { json2nameValue($EVENT,'',$JSONMAP) }\
$DEVICETOPIC/status/mqtt:.* { json2nameValue($EVENT, 'mqtt_', $JSONMAP) }\
$DEVICETOPIC/status/sys:.* { json2nameValue($EVENT, 'sys_', $JSONMAP) }\
$DEVICETOPIC/status/switch_0:.* { $EVENT =~ s/"output":true/"state":"on"/g;; $EVENT =~ s/"output":false/"state":"off"/g;; json2nameValue($EVENT, 'switch_', $JSONMAP) }\
$DEVICETOPIC/status/cloud:.* {}\
$DEVICETOPIC/rpc:.* { json2nameValue($EVENT, 'req_', $JSONMAP, 'in_mode')}\
$DEVICETOPIC/status/input_0:.* { json2nameValue($EVENT, 'input_', $JSONMAP) }\
fhem2shelly/rpc:.* {}\
shellypro1pm_30c6f789dfac:shellypro1pm-30c6f789dfac/status/wifi:.* { json2nameValue($EVENT, 'wifi_', $JSONMAP) }
attr MQTT2_shellypro1pm_30c6f789dfac room Solar
attr MQTT2_shellypro1pm_30c6f789dfac setList toggle:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Toggle","params": {"id":0}}\
off:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":false}\
on:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":0,"on":true}}
attr MQTT2_shellypro1pm_30c6f789dfac setStateList on off toggle on-for-timer off-for-timer
# .eventMapCmd An:noArg Aus:noArg
# CFGFN
# CID shellypro1pm_30c6f789dfac
# DEF shellypro1pm_30c6f789dfac
# FUUID 63efc507-f33f-49d6-6b09-54aa6b45e3ac1e0d
# IODev MQTT
# LASTInputDev MQTT
# MQTT_CONN MQTT_192.168.0.76_51774
# MQTT_MSGCNT 98
# MQTT_TIME 2023-02-17 19:48:59
# MSGCNT 98
# NAME MQTT2_shellypro1pm_30c6f789dfac
# NR 1691
# STATE An
# TYPE MQTT2_DEVICE
# eventCount 98
# .DT:
# DEVICETOPIC shellypro1pm-30c6f789dfac
# .attraggr:
# .attrminint:
# Helper:
# DBLOG:
# temperature:
# logdb:
# TIME 1676659739.59288
# VALUE 32.7
# JSONMAP:
# params_switch_0_temperature_tC temperature
# params_switch_0_temperature_tF 0
# params_wifi_sta_ip ip
# req_result_in_mode in_mode
# switch_state state
# switch_temperature_tC temperature
# switch_temperature_tF 0
# READINGS:
# 2023-02-17 19:18:47 IODev MQTT
# 2023-02-17 19:48:59 dst shellypro1pm-30c6f789dfac/events
# 2023-02-17 19:44:31 in_mode follow
# 2023-02-17 19:48:59 method NotifyStatus
# 2023-02-17 19:48:59 params_switch_0_aenergy_by_minute_1 0.000
# 2023-02-17 19:48:59 params_switch_0_aenergy_by_minute_2 0.000
# 2023-02-17 19:48:59 params_switch_0_aenergy_by_minute_3 0.000
# 2023-02-17 19:48:59 params_switch_0_aenergy_minute_ts 1676659739
# 2023-02-17 19:48:59 params_switch_0_aenergy_total 300.032
# 2023-02-17 19:40:58 params_switch_0_apower 0
# 2023-02-17 19:41:08 params_switch_0_current 0.056
# 2023-02-17 19:48:59 params_switch_0_id 0
# 2023-02-17 19:41:08 params_switch_0_output true
# 2023-02-17 19:40:58 params_switch_0_pf 0
# 2023-02-17 19:41:08 params_switch_0_source MQTT
# 2023-02-17 19:48:59 params_ts 1676659740.14
# 2023-02-17 19:48:59 src shellypro1pm-30c6f789dfac
# 2023-02-17 19:48:59 state on
# 2023-02-17 19:48:59 switch_aenergy_by_minute_1 0.000
# 2023-02-17 19:48:59 switch_aenergy_by_minute_2 0.000
# 2023-02-17 19:48:59 switch_aenergy_by_minute_3 0.000
# 2023-02-17 19:48:59 switch_aenergy_minute_ts 1676659739
# 2023-02-17 19:48:59 switch_aenergy_total 300.032
# 2023-02-17 19:48:59 switch_apower 0.0
# 2023-02-17 19:48:59 switch_current 0.056
# 2023-02-17 19:48:59 switch_id 0
# 2023-02-17 19:48:59 switch_pf -0.00
# 2023-02-17 19:48:59 switch_source MQTT
# 2023-02-17 19:48:59 switch_voltage 238.0
# 2023-02-17 19:48:59 temperature 32.7
# hmccu:
#
setstate MQTT2_shellypro1pm_30c6f789dfac An
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:18:47 IODev MQTT
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 dst shellypro1pm-30c6f789dfac/events
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:44:31 in_mode follow
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 method NotifyStatus
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 params_switch_0_aenergy_by_minute_1 0.000
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 params_switch_0_aenergy_by_minute_2 0.000
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 params_switch_0_aenergy_by_minute_3 0.000
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 params_switch_0_aenergy_minute_ts 1676659739
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 params_switch_0_aenergy_total 300.032
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:40:58 params_switch_0_apower 0
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:41:08 params_switch_0_current 0.056
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 params_switch_0_id 0
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:41:08 params_switch_0_output true
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:40:58 params_switch_0_pf 0
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:41:08 params_switch_0_source MQTT
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 params_ts 1676659740.14
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 src shellypro1pm-30c6f789dfac
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 state on
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_aenergy_by_minute_1 0.000
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_aenergy_by_minute_2 0.000
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_aenergy_by_minute_3 0.000
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_aenergy_minute_ts 1676659739
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_aenergy_total 300.032
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_apower 0.0
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_current 0.056
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_id 0
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_pf -0.00
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_source MQTT
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 switch_voltage 238.0
setstate MQTT2_shellypro1pm_30c6f789dfac 2023-02-17 19:48:59 temperature 32.7