ZitatLeider fordert am Wochenende die Freundin ihr Recht.
Zitat von: schwatter am 17 April 2026, 12:52:59jetzt verstehe ich, auf was du hinaus willst.
Zitat von: Beta-User am 14 April 2026, 07:42:32Via https://curlconverter.com/javascript/ bin ich dann auf diesen Testcode gekommen:Es geht also letztlich darum, auf der FHEM-Seite js-Code zu generieren, den man dann in einer bestimmten Instanz (derzeit) einer FHEMWEB-Verbindung browserseitig ausführen läßt. Der Code an sich soll sich
.Internals:
CID zigbee_Kinderzimmer
DEF zigbee_Kinderzimmer
FUUID 698a423e-f33f-e93f-71cc-cae690e15ea08048
IODev myBroker
LASTInputDev myBroker
MSGCNT 3351
NAME Kinderzimmer
NR 403
STATE desired-temp
TYPE MQTT2_DEVICE
eventCount 3506
myBroker_CONN myBroker_192.168.187.76_54192
myBroker_MSGCNT 3351
myBroker_TIME 2026-04-17 16:03:40
JSONMAP:
Battery battery_low
current_heating_setpoint desired-temp
local_temperature temperature
system_mode mode
READINGS:
2026-03-09 12:58:48 IODev myBroker
2026-04-16 20:29:51 associatedWith zigbee2mqtt
2026-02-09 21:28:32 attrTemplateVersion 20251221
2026-04-17 16:03:40 batteryState ok
2026-04-17 16:03:40 battery_low false
2026-04-17 16:03:40 child_lock UNLOCK
2026-04-17 16:03:40 desired-temp 0
2026-04-17 16:03:40 frost_protection ON
2026-04-17 16:03:40 linkquality 153
2026-04-17 16:03:40 local_temperature_calibration 4
2026-04-17 16:03:40 mode off
2026-04-17 16:03:40 running_state idle
2026-04-17 16:03:40 scale_protection ON
2026-04-17 16:03:40 schedule_friday 06:00/21.0 08:00/16.0 12:00/21.0 14:00/16.0 18:00/21.0 22:00/16.0
2026-04-17 16:03:40 schedule_monday 06:00/21.0 08:00/16.0 12:00/21.0 14:00/16.0 18:00/21.0 22:00/16.0
2026-04-17 16:03:40 schedule_saturday 06:00/21.0 08:00/16.0 12:00/21.0 14:00/16.0 18:00/21.0 22:00/16.0
2026-04-17 16:03:40 schedule_sunday 06:00/21.0 08:00/16.0 12:00/21.0 14:00/16.0 18:00/21.0 22:00/16.0
2026-04-17 16:03:40 schedule_thursday 06:00/21.0 08:00/16.0 12:00/21.0 14:00/16.0 18:00/21.0 22:00/16.0
2026-04-17 16:03:40 schedule_tuesday 06:00/21.0 08:00/16.0 12:00/21.0 14:00/16.0 18:00/21.0 22:00/16.0
2026-04-17 16:03:40 schedule_wednesday 06:00/17.0 08:00/17.0 12:00/17.0 14:00/16.0 20:00/16.0 22:00/16.0
2026-04-16 20:30:13 set z2m/Kinderzimmer/set 10
2026-04-17 16:03:40 state desired-temp
2026-04-17 16:03:40 temperature 21
Attributes:
comment For use with weekprofile, additional configuration and code would be needed, 6 Transitions required, format example: "HH:MM/C HH:MM/C HH:MM/C HH:MM/C HH:MM/C HH:MM/C"
devStateIcon lock.LOCK:secur_locked:child_lock+UNLOCK lock.UNLOCK:secur_open:child_lock+LOCK modus.auto:sani_heating_automatic modus.heat:sani_heating_manual modus.off:sani_heating_level_0
devicetopic z2m/Kinderzimmer
getList desired-temp:noArg desired-temp $DEVICETOPIC/get {"current_heating_setpoint": ""}
temperature:noArg temperature $DEVICETOPIC/get {"local_temperature": ""}
attr zigbee_Kinderzimmer periodicCmd temperature:55
group Heizung
icon temp_control
jsonMap current_heating_setpoint:desired-temp local_temperature:temperature Battery:battery_low system_mode:mode
model zigbee2mqtt_thermostat_AVATTO_TRV06_TS0601
readingList $DEVICETOPIC:.* { json2nameValue($EVENT,'',$JSONMAP) }
z2m/Kinderzimmer/set:.* set
room Geräte,MQTT2_DEVICE
setList desired-temp:slider,5.0,0.5,30.0,1 $DEVICETOPIC/set {"current_heating_setpoint": $EVTPART1 }
child_lock:LOCK,UNLOCK $DEVICETOPIC/set {"child_lock": "$EVTPART1"}
schedule_monday:textField { my $payload = $EVENT;$payload =~ s/$EVTPART0 //; qq($DEVICETOPIC/set {"schedule_monday":"$payload"})}
schedule_tuesday:textField { my $payload = $EVENT;$payload =~ s/$EVTPART0 //; qq($DEVICETOPIC/set {"schedule_tuesday":"$payload"})}
schedule_wednesday:textField { my $payload = $EVENT;$payload =~ s/$EVTPART0 //; qq($DEVICETOPIC/set {"schedule_wednesday":"$payload"})}
schedule_thursday:textField { my $payload = $EVENT;$payload =~ s/$EVTPART0 //; qq($DEVICETOPIC/set {"schedule_thursday":"$payload"})}
schedule_friday:textField { my $payload = $EVENT;$payload =~ s/$EVTPART0 //; qq($DEVICETOPIC/set {"schedule_friday":"$payload"})}
schedule_saturday:textField { my $payload = $EVENT;$payload =~ s/$EVTPART0 //; qq($DEVICETOPIC/set {"schedule_saturday":"$payload"})}
schedule_sunday:textField { my $payload = $EVENT;$payload =~ s/$EVTPART0 //; qq($DEVICETOPIC/set {"schedule_sunday":"$payload"})}
mode:heat,auto,off $DEVICETOPIC/set {"system_mode": "$EVTPART1"}
pi_heating_demand:slider,0,1,100,1 $DEVICETOPIC/set {"pi_heating_demand": $EVTPART1 }
frost_protection:ON,OFF $DEVICETOPIC/set {"frost_protection": "$EVTPART1"}
scale_protection:ON,OFF $DEVICETOPIC/set {"scale_protection": "$EVTPART1"}
local_temperature_calibration:slider,-9.0,1,9.0,1 $DEVICETOPIC/set {"local_temperature_calibration": $EVTPART1 }
x_send_set_payload:textField { my $payload = $EVENT;$payload =~ s/$EVTPART0 //; qq($DEVICETOPIC/set $payload)}
userReadings batteryState:battery_low.* {ReadingsVal($name,'battery_low','false') eq 'false'?'ok':'low'}
verbose 0<li data-row="3" data-col="1" data-sizex="2" data-sizey="2">
<header class="large">Kinderzimmer</header>
<div class="vbox top-space">
<div data-type="thermostat"
data-device="Kinderzimmer"
data-get="desired-temp"
data-set="desired-temp"
data-temp="temperature"
data-height="200"
data-width="200"
data-step="0.5"
data-min="5.0"
data-max="30">
</div>
</div>
</li>
Zitat von: roadrunnner am 17 April 2026, 13:41:02ich habe hier einen Ecoflow x Shelly Pro3EM (model_ID EFPEM-003CEBEU120). Ist ein leicht abgewandelter Shelly Pro3EM.Was ist denn bei diesem Shelly außer der model_ID noch anders?
attr <name> model shellypro3em via FHEM Kommandozeile gelingen.