FHEM Forum

FHEM => Anfängerfragen => Thema gestartet von: Jogi am 08 August 2023, 20:18:15

Titel: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: Jogi am 08 August 2023, 20:18:15
Hallo,
einer meiner Shelly 2.5 ist defekt gegangen und ich habe mir stattdessen einen Shelly plus2pm gekauft und eingebaut.
Leider scheint der Austausch aber nicht so einfach wie gedacht zu sein. Denn die bestehende Steuerung über das Shelly-Modul funktioniert nicht.
Egal, habe ich gedacht, dann mache ich es halt über MQTT. Aber auch das funktioniert nicht.
Ich bekomme den Shelly zwar ausgelsen und soweit ich das beurteilen kann sind die Daten auch korrekt, aber ich kann ihn nicht ansteuern.
Wenn ich es versuche bekomme ich folgende Fehlermeldung:
Unknown argument open, choose one of toggle:noArg off:noArg on:noArg on-for-timer off-for-timer blink on-till-overnight off-till off-till-overnight intervals on-till attrTemplate:?,General_Info,MQTT2_CLIENT_general_bridge,MQTT2_IO_ignoreRegexp_basic,MQTT2_IO_ignoreRegexp_tasmota,MQTT2_IO_ignoreRegexp_shelly,MQTT2_IO_ignoreRegexp_homeassistant,tasmota_basic,tasmota_basic_state_power1,tasmota_1ch+motion+SI7021,tasmota_POW,tasmota_POW_USB_split,tasmota_plug_with_rgbw_split,tasmota_plug_with_rgb_split,tasmota_ir,tasmota_rf,tasmota_rf_keys_example,tasmota_use_DS18x20_id,tasmota_zigbee2tasmota_bridge,tasmota_clear_readings_reset_readingsList_and_reboot,tasmota_set_lowercase_texts_and_state1,tasmota_set_uppercase_texts_and_state1,tasmota_set_power1_state_to_power,tasmota_2channel_split,tasmota_2ch_unified,tasmota_2channel_split_energy,tasmota_NSPanel_split,tasmota_2ch_shutter_invert_1,tasmota_2ch_shutter_invert_0,tasmota_4ch_two_shutters_invert_0,tasmota_2ch_shutter_venetian_invert_0,tasmota_3channel_input_shelly_i3,tasmota_4channel_split,tasmota_3socketUSB_split,tasmota_4ch_unified_basic_text,tasmota_4ch_unified_icon,tasmota_8ch_unified_icon,tasmota_8channel_split,tasmota_rgb_led_controller,tasmota_rgbw_led,tasmota_rgbcct_light,tasmota_cct_led,tasmota_TuyaMCU_dimmer,tasmota_window_sensor_MC400A,tasmota_bt2tasmota_bridge,shelly1,shellyPlus_1,shellyPlus_1pm,shellyPlus_2pm_split,shellyPlus_2pm_roller_invert_0,shellypro4pm,shellyPlus_i4,ESPurna_single_relay,eBus_daemon_splitter,ebus_update_files_from_svn,ems-esp_heater_device,ems-esp_boiler,ems-esp_thermostat_read-only,ems-esp_thermostat_simple,ems-esp_thermostat_RC35_type,WThermostatBeca,zigbee2mqtt_bridge,sonos2mqtt_bridge,sonos2mqtt_speaker,sonos2mqtt_bridge_comfort,roon,InstarCam,wled_controller,go_eCharger,go_eCharger_old,8channel_ethernet_board_split,8channel_ethernet_board_unified,6channel_ethernet_board_6input_split,6channel_ethernet_board_6input_unified,8channel_relay_board_8di_split,hoymiles_microinverter_hub_bridge,hoymiles_opendtu_hub_bridge,esp_milight_hub_bridge,OpenMQTTGateway_MCU,valetudo,worx_landroid,wallpanel_app,weewx_weather_station,McLightingWas mache ich falsch?
Hier ein List:
Internals:
   FUUID      64cf9434-f33f-8efe-a4c6-bfbf805fd73c54b2
   IODev      MQTT2_Server
   LASTInputDev MQTT2_Server
   MQTT2_Server_CONN MQTT2_Server_192.168.178.142_57045
   MQTT2_Server_MSGCNT 4038
   MQTT2_Server_TIME 2023-08-08 20:17:00
   MSGCNT     4038
   NAME       MQTT2_Shelly_Gaeste_WC_IP142_CH2
   NR         3347
   STATE      stopped
   TYPE       MQTT2_DEVICE
   eventCount 4038
   JSONMAP:
     params_switch_1_aenergy_total aenergy_total
     params_switch_1_apower apower
     params_switch_1_state state
     params_switch_1_temperature_tC temperature
     params_switch_1_temperature_tF 0
     temperature_tC temperature
     temperature_tF 0
   READINGS:
     2023-08-06 15:03:22   IODev           MQTT2_Server
     2023-08-08 20:17:00   aenergy_by_minute_1 0.000
     2023-08-08 20:17:00   aenergy_by_minute_2 0.000
     2023-08-08 20:17:00   aenergy_by_minute_3 0.000
     2023-08-08 20:17:00   aenergy_minute_ts 1691518619
     2023-08-08 20:17:00   aenergy_total   12.934
     2023-08-08 20:17:00   apower          0.0
     2023-08-06 14:38:17   associatedWith  MQTT2_Shelly_Gaeste_WC_IP142
     2023-08-06 14:38:17   attrTemplateVersion 20230111
     2023-08-08 20:17:00   current         0.000
     2023-08-08 20:17:00   current_pos     76
     2023-08-08 20:17:00   id              0
     2023-08-08 20:07:53   move_started_at 1691518070.47
     2023-08-08 20:07:53   move_timeout    2.54
     2023-08-08 20:17:00   pf              0.00
     2023-08-08 20:17:00   pos_control     true
     2023-08-08 20:17:00   source          timeout
     2023-08-08 20:17:00   state           stopped
     2023-08-06 14:57:08   subscriptions   Shelly_Gaeste_WC_IP142/command Shelly_Gaeste_WC_IP142/command/cover:0 Shelly_Gaeste_WC_IP142/command/sys shellies/command
     2023-08-08 20:07:53   target_pos      76
     2023-08-08 20:17:00   temperature_tC  55.4
     2023-08-08 20:17:00   temperature_tF  131.7
     2023-08-08 20:17:00   voltage         233.0
Attributes:
   IODev      MQTT2_Server
   cmdIcon    open:fts_shutter_up close:fts_shutter_down stop:fts_shutter_manual half:fts_shutter_50
   comment    Channel 2 for MQTT2_Shelly_Gaeste_WC_IP142
   devStateIcon { my $light = FW_makeImage(ReadingsVal($name,'state','off')); my $cons = ReadingsNum($name,'apower',0); my $total = round(ReadingsNum($name,'aenergy_total',0)/1000,1);qq(<a href="/fhem?cmd.dummy=set $name toggle&XHR=1">${light}</a><div>Verbrauch: $cons W / Total: $total kwhC</div>) }
   devicetopic MQTT2_Shelly_Gaeste_WC_IP142
   icon       fts_shutter
   jsonMap    params_switch_1_state:state params_switch_1_aenergy_total:aenergy_total params_switch_1_apower:apower params_switch_1_temperature_tC:temperature params_switch_1_temperature_tF:0 temperature_tC:temperature temperature_tF:0
   model      shellyPlus_2pm_split
   readingList $DEVICETOPIC/events/rpc:.* { return if $EVENT !~ m{switch:1}; $EVENT =~ s/"output":true/"state":"on"/g; $EVENT =~ s/"output":false/"state":"off"/g; json2nameValue($EVENT,'',$JSONMAP) }
  $DEVICETOPIC/status/switch.1:.* { json2nameValue($EVENT, '', $JSONMAP) }
Shelly_Gaeste_WC_IP142:Shelly_Gaeste_WC_IP142/status/cover_0:.* { json2nameValue($EVENT) }
   room       MQTT
   setList    toggle:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Toggle","params": {"id":1}}
  off:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":1,"on":false}}
  on:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":1,"on":true}}
  on-for-timer $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":1,"on":true,"toggle_after":$EVTPART1}}
  off-for-timer $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Switch.Set","params": {"id":1,"on":false,"toggle_after":$EVTPART1}}
   setStateList open close half stop pct
   webCmd     :open:close:half:stop:pct

Danke für Eure Tipps.
Titel: Aw: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: Beta-User am 08 August 2023, 21:18:54
Das "split"-attrTemplate ist mAn. nicht für den Rollladen-Betrieb gedacht....

Vielleicht nimmst du das für shutter....?!?
Titel: Aw: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: Jogi am 11 August 2023, 11:22:09
Ich habe das Device jetzt noch mal gelöscht und anders (ohne split) angelegt.
Das Ergebnis ist aber dasselbe. Ich bekomme alle Daten, kann den Shelly aber nicht von FHEM aus steuern.

Internals:
   CFGFN     
   CID        Shelly_Gaeste_WC_IP142
   DEF        Shelly_Gaeste_WC_IP142
   FUUID      64d5fc18-f33f-8efe-620f-4e5bef5c8e4d7525
   IODev      MQTT2_Server
   LASTInputDev MQTT2_Server
   MQTT2_Server_CONN MQTT2_Server_192.168.178.142_57045
   MQTT2_Server_MSGCNT 40
   MQTT2_Server_TIME 2023-08-11 11:20:00
   MSGCNT     40
   NAME       MQTT2_Shelly_Gaeste_WC_IP142
   NR         416256
   STATE      online
pct
   TYPE       MQTT2_DEVICE
   eventCount 52
   JSONMAP:
     status_current_pos pct
     status_state state
     status_temperature_tC temperature
   OLDREADINGS:
   READINGS:
     2023-08-11 11:15:04   IODev           MQTT2_Server
     2023-08-11 11:20:00   aenergy_by_minute_1 564.447
     2023-08-11 11:20:00   aenergy_by_minute_2 248.748
     2023-08-11 11:20:00   aenergy_by_minute_3 49.105
     2023-08-11 11:20:00   aenergy_minute_ts 1691745599
     2023-08-11 11:20:00   aenergy_total   17.145
     2023-08-11 11:20:00   apower          0.0
     2023-08-11 11:17:09   attrTemplateVersion 20220623
     2023-08-11 11:20:00   current         0.000
     2023-08-11 11:20:00   current_pos     86
     2023-08-11 11:20:00   id              0
     2023-08-11 11:19:51   move_started_at 1691745588.15
     2023-08-11 11:19:51   move_timeout    7.88
     2023-08-11 11:20:00   pf              0.00
     2023-08-11 11:20:00   pos_control     true
     2023-08-11 11:20:00   source          timeout
     2023-08-11 11:20:00   state           stopped
     2023-08-11 11:19:51   target_pos      86
     2023-08-11 11:20:00   temperature_tC  56.4
     2023-08-11 11:20:00   temperature_tF  133.6
     2023-08-11 11:20:00   voltage         231.7
Attributes:
   cmdIcon    open:fts_shutter_up close:fts_shutter_down stop:fts_shutter_manual half:fts_shutter_50
   comment    Shelly Plus 2 PM in Roller-Mode. 100=opened / 0=closed
   devStateIcon opening:fts_shutter_up@red closing:fts_shutter_down@red true:10px-kreis-gruen false:10px-kreis-rot 0:fts_shutter_100 100:fts_shutter_10 9\d:fts_shutter_10 8\d:fts_shutter_20 7\d:fts_shutter_30 6\d:fts_shutter_40 5\d:fts_shutter_50 4\d:fts_shutter_60 3\d:fts_shutter_70 2\d:fts_shutter_80 1\d:fts_shutter_90 0\d:fts_shutter_100 set_.*:fts_shutter_updown
   devicetopic Shelly_Gaeste_WC
   icon       fts_shutter
   jsonMap    status_state:state status_current_pos:pct status_temperature_tC:temperature
   model      shellyPlus_2pm_roller_invert_0
   readingList $DEVICETOPIC/online:.* online
  $DEVICETOPIC/status/mqtt:.* { json2nameValue($EVENT, 'mqtt_', $JSONMAP) }
  $DEVICETOPIC/status/sys:.* { json2nameValue($EVENT, 'sys_', $JSONMAP) }
  $DEVICETOPIC/status/cover_0:.* { json2nameValue($EVENT, 'status_', $JSONMAP) }
  fhem2shelly/rpc:.* {}
Shelly_Gaeste_WC_IP142:Shelly_Gaeste_WC_IP142/status/cover_0:.* { json2nameValue($EVENT) }
   room       MQTT2_DEVICE
   setList    open:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Open","params": {"id":0}}
  close:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Close","params": {"id":0}}
  half:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.GoToPosition","params": {"id":0,"pos":50}}
  stop:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Stop","params": {"id":0}}
  pct:slider,0,1,100 $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.GoToPosition","params": {"id":0,"pos":$EVTPART1}}
  x_update:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Shelly.Update","params": {"stage":"stable"}}
  x_reboot:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Shelly.Reboot"}
  x_eco:true,false $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Sys.SetConfig","params": {"config": {"device": {"eco_mode": $EVTPART1}}}}
   setStateList open close half stop pct
   stateFormat online
pct
   webCmd     :open:close:half:stop:pct
Titel: Aw: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: Beta-User am 11 August 2023, 12:56:59
Sicher, dass devicetopic nicht
Shelly_Gaeste_WC_IP142ist?!?
Titel: Aw: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: Jogi am 11 August 2023, 17:57:07
Zitat von: Beta-User am 11 August 2023, 12:56:59Sicher, dass devicetopic nicht
Shelly_Gaeste_WC_IP142ist?!?
Nein, ich bin nicht sicher.
Aber wenn ich das ändere passiert auch anderes. Ich bekomme alle Daten angezeigt, kann aber nichts steuern.
Hier ein aktualisiertes list:
Internals: CFGFN CID Shelly_Gaeste_WC_IP142 DEF Shelly_Gaeste_WC_IP142 FUUID 64d5fc18-f33f-8efe-620f-4e5bef5c8e4d7525 IODev MQTT2_Server LASTInputDev MQTT2_Server MQTT2_Server_CONN MQTT2_Server_192.168.178.142_57045 MQTT2_Server_MSGCNT 553 MQTT2_Server_TIME 2023-08-11 17:58:01 MSGCNT 553 NAME MQTT2_Shelly_Gaeste_WC_IP142 NR 416256 STATE online 100 TYPE MQTT2_DEVICE eventCount 578 JSONMAP: status_current_pos pct status_state state status_temperature_tC temperature OLDREADINGS: READINGS: 2023-08-11 11:15:04 IODev MQTT2_Server 2023-08-11 17:58:00 aenergy_by_minute_1 131.863 2023-08-11 17:58:00 aenergy_by_minute_2 0.000 2023-08-11 17:58:00 aenergy_by_minute_3 0.000 2023-08-11 17:58:00 aenergy_minute_ts 1691769479 2023-08-11 17:58:00 aenergy_total 18.489 2023-08-11 17:58:00 apower 0.0 2023-08-11 11:17:09 attrTemplateVersion 20220623 2023-08-11 17:58:00 current 0.000 2023-08-11 17:58:00 current_pos 100 2023-08-11 17:58:00 id 0 2023-08-11 17:57:21 move_started_at 1691769432.63 2023-08-11 17:57:21 move_timeout 60.00 2023-08-11 17:58:00 pct 100 2023-08-11 17:58:00 pf 0.00 2023-08-11 17:58:00 pos_control true 2023-08-11 17:58:00 source limit_switch 2023-08-11 17:58:00 state open 2023-08-11 17:58:00 status_aenergy_by_minute_1 131.863 2023-08-11 17:58:00 status_aenergy_by_minute_2 0.000 2023-08-11 17:58:00 status_aenergy_by_minute_3 0.000 2023-08-11 17:58:00 status_aenergy_minute_ts 1691769479 2023-08-11 17:58:00 status_aenergy_total 18.489 2023-08-11 17:58:00 status_apower 0.0 2023-08-11 17:58:00 status_current 0.000 2023-08-11 17:58:00 status_id 0 2023-08-11 17:57:21 status_move_started_at 1691769432.63 2023-08-11 17:57:21 status_move_timeout 60.00 2023-08-11 17:58:00 status_pf 0.00 2023-08-11 17:58:00 status_pos_control true 2023-08-11 17:58:00 status_source limit_switch 2023-08-11 17:57:21 status_target_pos 100 2023-08-11 17:58:00 status_temperature_tF 134.5 2023-08-11 17:58:00 status_voltage 231.9 2023-08-11 17:57:21 target_pos 100 2023-08-11 17:58:00 temperature 56.9 2023-08-11 17:58:00 temperature_tC 56.9 2023-08-11 17:58:00 temperature_tF 134.5 2023-08-11 17:58:00 voltage 231.9 Attributes: cmdIcon open:fts_shutter_up close:fts_shutter_down stop:fts_shutter_manual half:fts_shutter_50 comment Shelly Plus 2 PM in Roller-Mode. 100=opened / 0=closed devStateIcon opening:fts_shutter_up@red closing:fts_shutter_down@red true:10px-kreis-gruen false:10px-kreis-rot 0:fts_shutter_100 100:fts_shutter_10 9\d:fts_shutter_10 8\d:fts_shutter_20 7\d:fts_shutter_30 6\d:fts_shutter_40 5\d:fts_shutter_50 4\d:fts_shutter_60 3\d:fts_shutter_70 2\d:fts_shutter_80 1\d:fts_shutter_90 0\d:fts_shutter_100 set_.*:fts_shutter_updown devicetopic Shelly_Gaeste_WC_IP142 icon fts_shutter jsonMap status_state:state status_current_pos:pct status_temperature_tC:temperature model shellyPlus_2pm_roller_invert_0 readingList $DEVICETOPIC/online:.* online $DEVICETOPIC/status/mqtt:.* { json2nameValue($EVENT, 'mqtt_', $JSONMAP) } $DEVICETOPIC/status/sys:.* { json2nameValue($EVENT, 'sys_', $JSONMAP) } $DEVICETOPIC/status/cover_0:.* { json2nameValue($EVENT, 'status_', $JSONMAP) } fhem2shelly/rpc:.* {} Shelly_Gaeste_WC_IP142:Shelly_Gaeste_WC_IP142/status/cover_0:.* { json2nameValue($EVENT) } room MQTT setList open:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Open","params": {"id":0}} close:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Close","params": {"id":0}} half:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.GoToPosition","params": {"id":0,"pos":50}} stop:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Stop","params": {"id":0}} pct:slider,0,1,100 $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.GoToPosition","params": {"id":0,"pos":$EVTPART1}} x_update:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Shelly.Update","params": {"stage":"stable"}} x_reboot:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Shelly.Reboot"} x_eco:true,false $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Sys.SetConfig","params": {"config": {"device": {"eco_mode": $EVTPART1}}}} setStateList open close half stop pct stateFormat online pct webCmd :open:close:half:stop:pct
Titel: Aw: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: Beta-User am 12 August 2023, 10:47:26
Kannst du das nochmal löschen und dann lesbar (!) zeigen, wie das Ding von autocreate nach einem reboot angelegt wurde?

Es sollte v.a. auch "subsriptions" zu sehen sein.

PS: wer irgendwas umbenennt, darf nicht damit rechnen, das Automatismen wie attrTemplate damit einfach so klar kommen.

PPS: uU. muss der mqtt-Modus per Web-Interface noch auf "generic" (o.ä.) eingestellt werden.
Titel: Aw: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: Jogi am 13 August 2023, 16:36:59
Zitat von: Beta-User am 12 August 2023, 10:47:26Kannst du das nochmal löschen und dann lesbar (!) zeigen, wie das Ding von autocreate nach einem reboot angelegt wurde?

Es sollte v.a. auch "subsriptions" zu sehen sein.

PS: wer irgendwas umbenennt, darf nicht damit rechnen, das Automatismen wie attrTemplate damit einfach so klar kommen.

PPS: uU. muss der mqtt-Modus per Web-Interface noch auf "generic" (o.ä.) eingestellt werden.
Also,
ich hab das Device nochmal gelöscht.
So sieht es aus, wenn es von FHEM erkannt wird:
Internals:
  CFGFN     
  CID        Shelly_Gaeste_WC_IP142
  DEF        Shelly_Gaeste_WC_IP142
  FUUID      64d8e8c2-f33f-8efe-5399-4c3f29b476e81b0b
  IODev      MQTT2_Server
  LASTInputDev MQTT2_Server
  MQTT2_Server_CONN MQTT2_Server_192.168.178.142_57064
  MQTT2_Server_MSGCNT 13
  MQTT2_Server_TIME 2023-08-13 16:30:36
  MSGCNT    13
  NAME      MQTT2_Shelly_Gaeste_WC_IP142
  NR        76732
  STATE      stopped
  TYPE      MQTT2_DEVICE
  eventCount 16
  READINGS:
    2023-08-13 16:29:22  IODev          MQTT2_Server
    2023-08-13 16:30:36  aenergy_by_minute_1 57.598
    2023-08-13 16:30:36  aenergy_by_minute_2 90.076
    2023-08-13 16:30:36  aenergy_by_minute_3 0.000
    2023-08-13 16:30:36  aenergy_minute_ts 1691937031
    2023-08-13 16:30:36  aenergy_total  21.062
    2023-08-13 16:30:36  apower          0.0
    2023-08-13 16:30:36  current        0.000
    2023-08-13 16:30:36  current_pos    91
    2023-08-13 16:30:36  id              0
    2023-08-13 16:30:33  move_started_at 1691937029.56
    2023-08-13 16:30:33  move_timeout    1.02
    2023-08-13 16:30:36  pf              0.00
    2023-08-13 16:30:36  pos_control    true
    2023-08-13 16:30:36  source          timeout
    2023-08-13 16:30:36  state          stopped
    2023-08-13 16:29:22  subscriptions  Shelly_Gaeste_WC_IP142/command Shelly_Gaeste_WC_IP142/command/cover:0 Shelly_Gaeste_WC_IP142/command/sys shellies/command
    2023-08-13 16:30:33  target_pos      91
    2023-08-13 16:30:36  temperature_tC  56.1
    2023-08-13 16:30:36  temperature_tF  133.0
    2023-08-13 16:30:36  voltage        233.7
Attributes:
  readingList Shelly_Gaeste_WC_IP142:Shelly_Gaeste_WC_IP142/status/cover_0:.* { json2nameValue($EVENT) }
  room      MQTT2_DEVICE
Und so sieht es aus, wenn ich das Template gesetzt habe:
Internals:
  CFGFN     
  CID        Shelly_Gaeste_WC_IP142
  DEF        Shelly_Gaeste_WC_IP142
  FUUID      64d8e8c2-f33f-8efe-5399-4c3f29b476e81b0b
  IODev      MQTT2_Server
  LASTInputDev MQTT2_Server
  MQTT2_Server_CONN MQTT2_Server_192.168.178.142_57064
  MQTT2_Server_MSGCNT 26
  MQTT2_Server_TIME 2023-08-13 16:33:00
  MSGCNT    26
  NAME      MQTT2_Shelly_Gaeste_WC_IP142
  NR        76732
  STATE      online
96
  TYPE      MQTT2_DEVICE
  eventCount 31
  JSONMAP:
    status_current_pos pct
    status_state state
    status_temperature_tC temperature
  OLDREADINGS:
  READINGS:
    2023-08-13 16:29:22  IODev          MQTT2_Server
    2023-08-13 16:32:15  attrTemplateVersion 20220623
    2023-08-13 16:33:00  pct            96
    2023-08-13 16:33:00  state          stopped
    2023-08-13 16:33:00  status_aenergy_by_minute_1 35.669
    2023-08-13 16:33:00  status_aenergy_by_minute_2 0.000
    2023-08-13 16:33:00  status_aenergy_by_minute_3 57.598
    2023-08-13 16:33:00  status_aenergy_minute_ts 1691937179
    2023-08-13 16:33:00  status_aenergy_total 21.097
    2023-08-13 16:33:00  status_apower  0.0
    2023-08-13 16:33:00  status_current  0.000
    2023-08-13 16:33:00  status_id      0
    2023-08-13 16:32:37  status_move_started_at 1691937154.41
    2023-08-13 16:32:37  status_move_timeout 0.56
    2023-08-13 16:33:00  status_pf      0.00
    2023-08-13 16:33:00  status_pos_control true
    2023-08-13 16:33:00  status_source  timeout
    2023-08-13 16:32:37  status_target_pos 96
    2023-08-13 16:33:00  status_temperature_tF 133.1
    2023-08-13 16:33:00  status_voltage  233.6
    2023-08-13 16:33:00  temperature    56.2
Attributes:
  cmdIcon    open:fts_shutter_up close:fts_shutter_down stop:fts_shutter_manual half:fts_shutter_50
  comment    Shelly Plus 2 PM in Roller-Mode. 100=opened / 0=closed
  devStateIcon opening:fts_shutter_up@red closing:fts_shutter_down@red true:10px-kreis-gruen false:10px-kreis-rot 0:fts_shutter_100 100:fts_shutter_10 9\d:fts_shutter_10 8\d:fts_shutter_20 7\d:fts_shutter_30 6\d:fts_shutter_40 5\d:fts_shutter_50 4\d:fts_shutter_60 3\d:fts_shutter_70 2\d:fts_shutter_80 1\d:fts_shutter_90 0\d:fts_shutter_100 set_.*:fts_shutter_updown
  devicetopic Shelly_Gaeste_WC_IP142
  icon      fts_shutter
  jsonMap    status_state:state status_current_pos:pct status_temperature_tC:temperature
  model      shellyPlus_2pm_roller_invert_0
  readingList $DEVICETOPIC/online:.* online
  $DEVICETOPIC/status/mqtt:.* { json2nameValue($EVENT, 'mqtt_', $JSONMAP) }
  $DEVICETOPIC/status/sys:.* { json2nameValue($EVENT, 'sys_', $JSONMAP) }
  $DEVICETOPIC/status/cover_0:.* { json2nameValue($EVENT, 'status_', $JSONMAP) }
  fhem2shelly/rpc:.* {}
  room      MQTT2_DEVICE
  setList    open:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Open","params": {"id":0}}
  close:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Close","params": {"id":0}}
  half:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.GoToPosition","params": {"id":0,"pos":50}}
  stop:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.Stop","params": {"id":0}}
  pct:slider,0,1,100 $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Cover.GoToPosition","params": {"id":0,"pos":$EVTPART1}}
  x_update:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Shelly.Update","params": {"stage":"stable"}}
  x_reboot:noArg $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Shelly.Reboot"}
  x_eco:true,false $DEVICETOPIC/rpc {"id":0,"src":"fhem2shelly","method":"Sys.SetConfig","params": {"config": {"device": {"eco_mode": $EVTPART1}}}}
  setStateList open close half stop pct
  stateFormat online
pct
  webCmd    :open:close:half:stop:pct
In den Shelly MQTT-Einstellungen habe ich alle Optionen akitiviert:
Enable "MQTT Control" ?
Enable RPC over MQTT
RPC status notifications over MQTT
Generic status update over MQTT
Connection Type steht auf "No SSL".

Steuern lässt sich leider immer noch nichts.

Titel: Aw: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: Beta-User am 13 August 2023, 19:04:55
OK, da scheint sich was an dem command-topic geändert (?) zu haben .../command statt .../rpc?

Kannst du das mal ändern und testen? (Ggf. mal die shelly-doku bemühen).
Titel: Aw: MQTT: Kann Shelly plus2pm im Rolladenmodus zwar auslesen, aber nicht ansteuern
Beitrag von: kschi am 04 Januar 2024, 14:23:26
Hallo,
ich habe mir auch einen Shelly Plus2PM zugelegt und genau das selbe Problem wie Jogi. Alle Vorschläge habe ich auch umgesetzt.

Nachdem ich hier schon meine Frage posten wollte, habe ich es dann doch hinbekommen. Neben den Einstellungen in den MQTT Einstellungen im Shelly muss beim Auswählen des Templates shellyPlus_2pm_roller_invert_0 die Frage nach dem Shelly name in the topic beantwortet werden. Hier kommt der Name hinein, der in der Shelly MQTT Konfiguration angegeben wurde.

Jetzt funktioniert es bei mir. Auch ohne Umbenennung von /rpc auf /command