Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter Shelly 10.4.x (LATEST / BETA)

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.1k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.1k

Test Adapter Shelly 10.4.x (LATEST / BETA)

Scheduled Pinned Locked Moved Tester
mcm1957shelly
54 Posts 11 Posters 5.4k Views 14 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • haus-automatisierungH haus-automatisierung

    @rene55 Bindestriche sind egal. Sollten in der aktuellen Version auch direkt entfernt werden, wenn man den EncryptionKey unbestätigt schreibt (was man ja eh immer bei „fremden“ Datenpunkten so macht)

    Rene55R Offline
    Rene55R Offline
    Rene55
    wrote on last edited by
    #33

    @haus-automatisierung Ok, die Bindestriche sind luxus. Heißt das auch, dass der encriptionKey immer mit ack=false stehen bleibt?

    Host: Fujitsu Intel(R) Pentium(R) CPU G4560T, 32 GB RAM, Proxmox 8.x + lxc Ubuntu 22.04
    ioBroker (8 GB RAM) Node.js: 20.19.1, NPM: 10.8.2, js-Controller: 7.0.6, Admin: 7.6.3
    Wetterstation: Froggit WH3000SE V1.6.6

    haus-automatisierungH 1 Reply Last reply
    0
    • Rene55R Rene55

      @haus-automatisierung Ok, die Bindestriche sind luxus. Heißt das auch, dass der encriptionKey immer mit ack=false stehen bleibt?

      haus-automatisierungH Online
      haus-automatisierungH Online
      haus-automatisierung
      Developer Most Active
      wrote on last edited by
      #34

      @rene55 Version 10.1.0 sollte den Schlüssel bestätigen und entsprechend mit ack true neu schreiben.

      🧑‍🎓 Autor des beliebten ioBroker-Master-Kurses
      🎥 Tutorials rund um das Thema DIY-Smart-Home: https://haus-automatisierung.com/
      📚 Meine inoffizielle ioBroker Dokumentation

      Rene55R 1 Reply Last reply
      1
      • icebearI Online
        icebearI Online
        icebear
        wrote on last edited by icebear
        #35

        Ich hab jetzt auch nochmals auf die Version 10.1.0 geupdatet in der Hoffung das die Fehlermeldung vom Shelly Adapter verschwinden, aber ich bekomme immer noch die folgenden Fehlermeldungen die das Log zumüllen:

        [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"
        

        bei allen Shelly Plugs die ich einsetzte.

        Debug Log (Auszug)

        shelly.0
        2025-07-08 09:55:30.347	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1125876
        
        shelly.0
        2025-07-08 09:55:29.111	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on
        
        shelly.0
        2025-07-08 09:55:29.111	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761
        
        shelly.0
        2025-07-08 09:55:29.110	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00
        
        shelly.0
        2025-07-08 09:55:20.774	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"
        
        shelly.0
        2025-07-08 09:55:20.763	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"
        
        shelly.0
        2025-07-08 09:55:20.723	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)
        
        shelly.0
        2025-07-08 09:55:20.723	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 09:55:20.722	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 09:55:20.695	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)
        
        shelly.0
        2025-07-08 09:55:20.695	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 09:55:20.695	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 09:55:20.694	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"
        
        shelly.0
        2025-07-08 09:55:20.605	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)
        
        shelly.0
        2025-07-08 09:55:20.605	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 09:55:20.604	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 09:55:14.535	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1125860
        
        shelly.0
        2025-07-08 09:55:14.503	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761
        
        shelly.0
        2025-07-08 09:55:10.577	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1"]
        
        shelly.0
        2025-07-08 09:55:10.349	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1"]
        
        shelly.0
        2025-07-08 09:55:10.143	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplus1#b0a7324c9984#1"]
        
        shelly.0
        2025-07-08 09:55:08.400	debug	[deviceStatusUpdate] shellyplus1#78ee4cc5972c#1: false
        
        shelly.0
        2025-07-08 09:55:07.159	debug	[MQTT Server] Close for 192.168.178.63 ((undefined / undefined / undefined))
        
        shelly.0
        2025-07-08 09:55:07.159	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 09:55:07.159	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: false
        
        shelly.0
        2025-07-08 09:55:07.159	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1)
        
        shelly.0
        2025-07-08 09:55:07.159	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) (false)
        
        shelly.0
        2025-07-08 09:55:07.158	debug	[MQTT Server] End for 192.168.178.63 ((shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1))
        
        shelly.0
        2025-07-08 09:55:06.609	debug	[MQTT Server] Close for 192.168.178.76 ((undefined / undefined / undefined))
        
        shelly.0
        2025-07-08 09:55:06.609	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 09:55:06.609	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: false
        
        shelly.0
        2025-07-08 09:55:06.609	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1)
        
        shelly.0
        2025-07-08 09:55:06.609	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) (false)
        
        shelly.0
        2025-07-08 09:55:06.608	debug	[MQTT Server] End for 192.168.178.76 ((shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1))
        
        shelly.0
        2025-07-08 09:55:06.372	debug	[MQTT Server] Close for 192.168.178.44 ((undefined / undefined / undefined))
        
        shelly.0
        2025-07-08 09:55:06.372	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 09:55:06.371	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: false
        
        shelly.0
        2025-07-08 09:55:06.371	debug	[BaseClient] Destroying (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1)
        
        shelly.0
        2025-07-08 09:55:06.371	info	[MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) (false)
        
        shelly.0
        2025-07-08 09:55:06.362	debug	[MQTT Server] End for 192.168.178.44 ((shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1))
        
        shelly.0
        2025-07-08 09:55:06.278	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#441793ab4310#1","shellyplus1#b0a7324c9984#1"]
        
        shelly.0
        2025-07-08 09:55:05.963	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#441793ab4310#1"]
        
        host.iobroker
        2025-07-08 09:55:05.612	info	instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 26785
        
        shelly.0
        2025-07-08 09:55:05.391	debug	[onlineCheck] Checking shellyplus1#78ee4cc5972c#1 on 192.168.178.78:80
        
        shelly.0
        2025-07-08 09:55:05.000	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: true
        
        shelly.0
        2025-07-08 09:55:04.997	debug	[onlineCheck] Checking shellyplus1#b0a7324c9984#1 on 192.168.178.76:80
        
        shelly.0
        2025-07-08 09:55:04.383	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: true
        
        shelly.0
        2025-07-08 09:55:04.376	debug	[onlineCheck] Checking shellyplus1#441793ab4310#1 on 192.168.178.63:80
        
        shelly.0
        2025-07-08 09:55:03.352	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: true
        
        shelly.0
        2025-07-08 09:55:03.349	debug	[onlineCheck] Checking shellyplusplugs#e465b85e4500#1 on 192.168.178.44:80
        
        shelly.0
        2025-07-08 09:55:03.257	debug	[deviceStatusUpdate] SHPLG-1#8FF28C#1: true
        
        shelly.0
        2025-07-08 09:55:03.196	debug	[onlineCheck] Checking SHPLG-1#8FF28C#1 on 192.168.178.43:80
        
        shelly.0
        2025-07-08 09:55:00.508	warn	[mqtt controlFunction] Unable to perform request - device (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) is offline
        
        shelly.0
        2025-07-08 09:55:00.508	debug	[onStateChange] "shelly.0.shellyplus1#441793ab4310#1.Relay0.Switch" state changed: {"val":false,"ack":false,"ts":1751961300038,"q":0,"c":"script.js.Energie_Strom.TestWW","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1751885460060} - forwarding to objectHelper
        

        Und noch ein weiteres Log

        
        shelly.0
        2025-07-08 10:12:01.160	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"
        
        shelly.0
        2025-07-08 10:12:01.120	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"
        
        shelly.0
        2025-07-08 10:12:01.117	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)
        
        shelly.0
        2025-07-08 10:12:01.117	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 10:12:01.117	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 10:12:01.054	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)
        
        shelly.0
        2025-07-08 10:12:01.054	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 10:12:01.054	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 10:12:00.997	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"
        
        shelly.0
        2025-07-08 10:12:00.948	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)
        
        shelly.0
        2025-07-08 10:12:00.947	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 10:12:00.947	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 10:11:59.212	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on
        
        shelly.0
        2025-07-08 10:11:59.212	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761
        
        shelly.0
        2025-07-08 10:11:59.211	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00
        
        shelly.0
        2025-07-08 10:11:58.026	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1"]
        
        shelly.0
        2025-07-08 10:11:56.630	debug	[MQTT Server] Close for 192.168.178.76 ((undefined / undefined / undefined))
        
        shelly.0
        2025-07-08 10:11:56.630	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 10:11:56.630	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: false
        
        shelly.0
        2025-07-08 10:11:56.630	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1)
        
        shelly.0
        2025-07-08 10:11:56.630	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) (false)
        
        shelly.0
        2025-07-08 10:11:56.629	debug	[MQTT Server] End for 192.168.178.76 ((shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1))
        
        shelly.0
        2025-07-08 10:11:52.882	debug	[deviceStatusUpdate] shellyplus1#78ee4cc5972c#1: false
        
        shelly.0
        2025-07-08 10:11:52.877	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#b0a7324c9984#1"]
        
        shelly.0
        2025-07-08 10:11:52.290	debug	[MQTT Server] Close for 192.168.178.63 ((undefined / undefined / undefined))
        
        shelly.0
        2025-07-08 10:11:52.290	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 10:11:52.290	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: false
        
        shelly.0
        2025-07-08 10:11:52.290	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1)
        
        shelly.0
        2025-07-08 10:11:52.289	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) (false)
        
        shelly.0
        2025-07-08 10:11:52.289	debug	[MQTT Server] End for 192.168.178.63 ((shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1))
        
        shelly.0
        2025-07-08 10:11:50.193	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplusplugs#e465b85e4500#1","shellyplus1#b0a7324c9984#1"]
        
        shelly.0
        2025-07-08 10:11:50.040	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplusplugs#e465b85e4500#1"]
        
        shelly.0
        2025-07-08 10:11:49.919	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126856
        
        shelly.0
        2025-07-08 10:11:49.875	debug	[onlineCheck] Checking shellyplus1#78ee4cc5972c#1 on 192.168.178.78:80
        
        shelly.0
        2025-07-08 10:11:49.345	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: true
        
        shelly.0
        2025-07-08 10:11:49.336	debug	[onlineCheck] Checking shellyplus1#b0a7324c9984#1 on 192.168.178.76:80
        
        shelly.0
        2025-07-08 10:11:48.720	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: true
        
        shelly.0
        2025-07-08 10:11:48.716	debug	[onlineCheck] Checking shellyplus1#441793ab4310#1 on 192.168.178.63:80
        
        shelly.0
        2025-07-08 10:11:48.478	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: true
        
        shelly.0
        2025-07-08 10:11:48.474	debug	[onlineCheck] Checking shellyplusplugs#e465b85e4500#1 on 192.168.178.44:80
        
        shelly.0
        2025-07-08 10:11:48.456	debug	[deviceStatusUpdate] SHPLG-1#8FF28C#1: true
        
        shelly.0
        2025-07-08 10:11:48.434	debug	[onlineCheck] Checking SHPLG-1#8FF28C#1 on 192.168.178.43:80
        
        shelly.0
        2025-07-08 10:11:48.317	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) for mode: <not set>
        
        shelly.0
        2025-07-08 10:11:46.640	info	[MQTT] Device with client id "shellyplus1-b0a7324c9984" connected from 192.168.178.76!
        
        shelly.0
        2025-07-08 10:11:46.639	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 10:11:46.637	debug	[BaseClient] Destroying 192.168.178.76 (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 10:11:46.636	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":96,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-b0a7324c9984","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}
        
        shelly.0
        2025-07-08 10:11:46.632	debug	[MQTT Server] New connection from 192.168.178.76
        
        shelly.0
        2025-07-08 10:11:45.244	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1"]
        
        shelly.0
        2025-07-08 10:11:44.794	debug	[MQTT Server] Close for 192.168.178.44 ((undefined / undefined / undefined))
        
        shelly.0
        2025-07-08 10:11:44.793	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 10:11:44.793	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: false
        
        shelly.0
        2025-07-08 10:11:44.793	debug	[BaseClient] Destroying (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1)
        
        shelly.0
        2025-07-08 10:11:44.793	info	[MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) (false)
        
        shelly.0
        2025-07-08 10:11:44.791	debug	[MQTT Server] End for 192.168.178.44 ((shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1))
        
        shelly.0
        2025-07-08 10:11:43.188	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) for mode: <not set>
        
        shelly.0
        2025-07-08 10:11:42.296	info	[MQTT] Device with client id "shellyplus1-441793ab4310" connected from 192.168.178.63!
        
        shelly.0
        2025-07-08 10:11:42.296	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 10:11:42.296	debug	[BaseClient] Destroying 192.168.178.63 (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 10:11:42.296	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":96,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-441793ab4310","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}
        
        shelly.0
        2025-07-08 10:11:42.295	debug	[MQTT Server] New connection from 192.168.178.63
        
        shelly.0
        2025-07-08 10:11:35.819	debug	[createObjects] Starting object creation of (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) for mode: <not set>
        
        shelly.0
        2025-07-08 10:11:34.796	info	[MQTT] Device with client id "shellyplusplugs-e465b85e4500" connected from 192.168.178.44!
        
        shelly.0
        2025-07-08 10:11:34.795	debug	[MQTT] Destroying
        
        shelly.0
        2025-07-08 10:11:34.795	debug	[BaseClient] Destroying 192.168.178.44 (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 10:11:34.795	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":82,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplusplugs-e465b85e4500","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}
        
        shelly.0
        2025-07-08 10:11:34.794	debug	[MQTT Server] New connection from 192.168.178.44
        
        shelly.0
        2025-07-08 10:11:33.660	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126839
        
        shelly.0
        2025-07-08 10:11:29.209	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on
        
        shelly.0
        2025-07-08 10:11:29.208	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761
        
        shelly.0
        2025-07-08 10:11:29.207	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00
        
        host.iobroker
        2025-07-08 10:11:24.910	info	instance system.adapter.dwd.0 having pid 27773 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
        
        dwd.0
        2025-07-08 10:11:23.252	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
        
        shelly.0
        2025-07-08 10:11:18.409	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.rssi, value: -63
        
        shelly.0
        2025-07-08 10:11:18.409	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126824
        
        shelly.0
        2025-07-08 10:11:12.338	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"
        
        shelly.0
        2025-07-08 10:11:12.291	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)
        
        shelly.0
        2025-07-08 10:11:12.291	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 10:11:12.290	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 10:11:12.258	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"
        
        shelly.0
        2025-07-08 10:11:12.149	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)
        
        shelly.0
        2025-07-08 10:11:12.148	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 10:11:12.147	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        
        shelly.0
        2025-07-08 10:11:12.144	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"
        
        shelly.0
        2025-07-08 10:11:12.073	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)
        
        shelly.0
        2025-07-08 10:11:12.073	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
        
        shelly.0
        2025-07-08 10:11:12.073	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
        

        was kann ich tun?

        mcm1957M 1 Reply Last reply
        0
        • icebearI icebear

          Ich hab jetzt auch nochmals auf die Version 10.1.0 geupdatet in der Hoffung das die Fehlermeldung vom Shelly Adapter verschwinden, aber ich bekomme immer noch die folgenden Fehlermeldungen die das Log zumüllen:

          [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"
          

          bei allen Shelly Plugs die ich einsetzte.

          Debug Log (Auszug)

          shelly.0
          2025-07-08 09:55:30.347	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1125876
          
          shelly.0
          2025-07-08 09:55:29.111	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on
          
          shelly.0
          2025-07-08 09:55:29.111	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761
          
          shelly.0
          2025-07-08 09:55:29.110	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00
          
          shelly.0
          2025-07-08 09:55:20.774	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"
          
          shelly.0
          2025-07-08 09:55:20.763	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"
          
          shelly.0
          2025-07-08 09:55:20.723	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)
          
          shelly.0
          2025-07-08 09:55:20.723	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 09:55:20.722	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 09:55:20.695	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)
          
          shelly.0
          2025-07-08 09:55:20.695	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 09:55:20.695	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 09:55:20.694	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"
          
          shelly.0
          2025-07-08 09:55:20.605	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)
          
          shelly.0
          2025-07-08 09:55:20.605	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 09:55:20.604	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 09:55:14.535	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1125860
          
          shelly.0
          2025-07-08 09:55:14.503	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761
          
          shelly.0
          2025-07-08 09:55:10.577	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1"]
          
          shelly.0
          2025-07-08 09:55:10.349	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1"]
          
          shelly.0
          2025-07-08 09:55:10.143	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplus1#b0a7324c9984#1"]
          
          shelly.0
          2025-07-08 09:55:08.400	debug	[deviceStatusUpdate] shellyplus1#78ee4cc5972c#1: false
          
          shelly.0
          2025-07-08 09:55:07.159	debug	[MQTT Server] Close for 192.168.178.63 ((undefined / undefined / undefined))
          
          shelly.0
          2025-07-08 09:55:07.159	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 09:55:07.159	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: false
          
          shelly.0
          2025-07-08 09:55:07.159	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1)
          
          shelly.0
          2025-07-08 09:55:07.159	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) (false)
          
          shelly.0
          2025-07-08 09:55:07.158	debug	[MQTT Server] End for 192.168.178.63 ((shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1))
          
          shelly.0
          2025-07-08 09:55:06.609	debug	[MQTT Server] Close for 192.168.178.76 ((undefined / undefined / undefined))
          
          shelly.0
          2025-07-08 09:55:06.609	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 09:55:06.609	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: false
          
          shelly.0
          2025-07-08 09:55:06.609	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1)
          
          shelly.0
          2025-07-08 09:55:06.609	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) (false)
          
          shelly.0
          2025-07-08 09:55:06.608	debug	[MQTT Server] End for 192.168.178.76 ((shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1))
          
          shelly.0
          2025-07-08 09:55:06.372	debug	[MQTT Server] Close for 192.168.178.44 ((undefined / undefined / undefined))
          
          shelly.0
          2025-07-08 09:55:06.372	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 09:55:06.371	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: false
          
          shelly.0
          2025-07-08 09:55:06.371	debug	[BaseClient] Destroying (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1)
          
          shelly.0
          2025-07-08 09:55:06.371	info	[MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) (false)
          
          shelly.0
          2025-07-08 09:55:06.362	debug	[MQTT Server] End for 192.168.178.44 ((shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1))
          
          shelly.0
          2025-07-08 09:55:06.278	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#441793ab4310#1","shellyplus1#b0a7324c9984#1"]
          
          shelly.0
          2025-07-08 09:55:05.963	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#441793ab4310#1"]
          
          host.iobroker
          2025-07-08 09:55:05.612	info	instance system.adapter.weatherunderground.0 in version "3.7.0" started with pid 26785
          
          shelly.0
          2025-07-08 09:55:05.391	debug	[onlineCheck] Checking shellyplus1#78ee4cc5972c#1 on 192.168.178.78:80
          
          shelly.0
          2025-07-08 09:55:05.000	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: true
          
          shelly.0
          2025-07-08 09:55:04.997	debug	[onlineCheck] Checking shellyplus1#b0a7324c9984#1 on 192.168.178.76:80
          
          shelly.0
          2025-07-08 09:55:04.383	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: true
          
          shelly.0
          2025-07-08 09:55:04.376	debug	[onlineCheck] Checking shellyplus1#441793ab4310#1 on 192.168.178.63:80
          
          shelly.0
          2025-07-08 09:55:03.352	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: true
          
          shelly.0
          2025-07-08 09:55:03.349	debug	[onlineCheck] Checking shellyplusplugs#e465b85e4500#1 on 192.168.178.44:80
          
          shelly.0
          2025-07-08 09:55:03.257	debug	[deviceStatusUpdate] SHPLG-1#8FF28C#1: true
          
          shelly.0
          2025-07-08 09:55:03.196	debug	[onlineCheck] Checking SHPLG-1#8FF28C#1 on 192.168.178.43:80
          
          shelly.0
          2025-07-08 09:55:00.508	warn	[mqtt controlFunction] Unable to perform request - device (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) is offline
          
          shelly.0
          2025-07-08 09:55:00.508	debug	[onStateChange] "shelly.0.shellyplus1#441793ab4310#1.Relay0.Switch" state changed: {"val":false,"ack":false,"ts":1751961300038,"q":0,"c":"script.js.Energie_Strom.TestWW","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1751885460060} - forwarding to objectHelper
          

          Und noch ein weiteres Log

          
          shelly.0
          2025-07-08 10:12:01.160	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"
          
          shelly.0
          2025-07-08 10:12:01.120	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"
          
          shelly.0
          2025-07-08 10:12:01.117	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)
          
          shelly.0
          2025-07-08 10:12:01.117	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 10:12:01.117	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 10:12:01.054	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)
          
          shelly.0
          2025-07-08 10:12:01.054	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 10:12:01.054	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 10:12:00.997	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"
          
          shelly.0
          2025-07-08 10:12:00.948	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)
          
          shelly.0
          2025-07-08 10:12:00.947	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 10:12:00.947	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 10:11:59.212	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on
          
          shelly.0
          2025-07-08 10:11:59.212	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761
          
          shelly.0
          2025-07-08 10:11:59.211	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00
          
          shelly.0
          2025-07-08 10:11:58.026	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1"]
          
          shelly.0
          2025-07-08 10:11:56.630	debug	[MQTT Server] Close for 192.168.178.76 ((undefined / undefined / undefined))
          
          shelly.0
          2025-07-08 10:11:56.630	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 10:11:56.630	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: false
          
          shelly.0
          2025-07-08 10:11:56.630	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1)
          
          shelly.0
          2025-07-08 10:11:56.630	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) (false)
          
          shelly.0
          2025-07-08 10:11:56.629	debug	[MQTT Server] End for 192.168.178.76 ((shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1))
          
          shelly.0
          2025-07-08 10:11:52.882	debug	[deviceStatusUpdate] shellyplus1#78ee4cc5972c#1: false
          
          shelly.0
          2025-07-08 10:11:52.877	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplusplugs#e465b85e4500#1","shellyplus1#b0a7324c9984#1"]
          
          shelly.0
          2025-07-08 10:11:52.290	debug	[MQTT Server] Close for 192.168.178.63 ((undefined / undefined / undefined))
          
          shelly.0
          2025-07-08 10:11:52.290	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 10:11:52.290	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: false
          
          shelly.0
          2025-07-08 10:11:52.290	debug	[BaseClient] Destroying (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1)
          
          shelly.0
          2025-07-08 10:11:52.289	info	[MQTT] Client Close: (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) (false)
          
          shelly.0
          2025-07-08 10:11:52.289	debug	[MQTT Server] End for 192.168.178.63 ((shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1))
          
          shelly.0
          2025-07-08 10:11:50.193	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplusplugs#e465b85e4500#1","shellyplus1#b0a7324c9984#1"]
          
          shelly.0
          2025-07-08 10:11:50.040	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1","shellyplusplugs#e465b85e4500#1"]
          
          shelly.0
          2025-07-08 10:11:49.919	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126856
          
          shelly.0
          2025-07-08 10:11:49.875	debug	[onlineCheck] Checking shellyplus1#78ee4cc5972c#1 on 192.168.178.78:80
          
          shelly.0
          2025-07-08 10:11:49.345	debug	[deviceStatusUpdate] shellyplus1#b0a7324c9984#1: true
          
          shelly.0
          2025-07-08 10:11:49.336	debug	[onlineCheck] Checking shellyplus1#b0a7324c9984#1 on 192.168.178.76:80
          
          shelly.0
          2025-07-08 10:11:48.720	debug	[deviceStatusUpdate] shellyplus1#441793ab4310#1: true
          
          shelly.0
          2025-07-08 10:11:48.716	debug	[onlineCheck] Checking shellyplus1#441793ab4310#1 on 192.168.178.63:80
          
          shelly.0
          2025-07-08 10:11:48.478	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: true
          
          shelly.0
          2025-07-08 10:11:48.474	debug	[onlineCheck] Checking shellyplusplugs#e465b85e4500#1 on 192.168.178.44:80
          
          shelly.0
          2025-07-08 10:11:48.456	debug	[deviceStatusUpdate] SHPLG-1#8FF28C#1: true
          
          shelly.0
          2025-07-08 10:11:48.434	debug	[onlineCheck] Checking SHPLG-1#8FF28C#1 on 192.168.178.43:80
          
          shelly.0
          2025-07-08 10:11:48.317	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-b0a7324c9984 / shellyplus1#b0a7324c9984#1) for mode: <not set>
          
          shelly.0
          2025-07-08 10:11:46.640	info	[MQTT] Device with client id "shellyplus1-b0a7324c9984" connected from 192.168.178.76!
          
          shelly.0
          2025-07-08 10:11:46.639	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 10:11:46.637	debug	[BaseClient] Destroying 192.168.178.76 (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 10:11:46.636	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":96,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-b0a7324c9984","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}
          
          shelly.0
          2025-07-08 10:11:46.632	debug	[MQTT Server] New connection from 192.168.178.76
          
          shelly.0
          2025-07-08 10:11:45.244	debug	[deviceStatusUpdate] Online devices: ["SHPLG-1#8FF28C#1","shellyplus1#441793ab4310#1"]
          
          shelly.0
          2025-07-08 10:11:44.794	debug	[MQTT Server] Close for 192.168.178.44 ((undefined / undefined / undefined))
          
          shelly.0
          2025-07-08 10:11:44.793	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 10:11:44.793	debug	[deviceStatusUpdate] shellyplusplugs#e465b85e4500#1: false
          
          shelly.0
          2025-07-08 10:11:44.793	debug	[BaseClient] Destroying (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1)
          
          shelly.0
          2025-07-08 10:11:44.793	info	[MQTT] Client Close: (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) (false)
          
          shelly.0
          2025-07-08 10:11:44.791	debug	[MQTT Server] End for 192.168.178.44 ((shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1))
          
          shelly.0
          2025-07-08 10:11:43.188	debug	[createObjects] Starting object creation of (shellyplus1 / shellyplus1-441793ab4310 / shellyplus1#441793ab4310#1) for mode: <not set>
          
          shelly.0
          2025-07-08 10:11:42.296	info	[MQTT] Device with client id "shellyplus1-441793ab4310" connected from 192.168.178.63!
          
          shelly.0
          2025-07-08 10:11:42.296	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 10:11:42.296	debug	[BaseClient] Destroying 192.168.178.63 (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 10:11:42.296	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":96,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplus1-441793ab4310","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}
          
          shelly.0
          2025-07-08 10:11:42.295	debug	[MQTT Server] New connection from 192.168.178.63
          
          shelly.0
          2025-07-08 10:11:35.819	debug	[createObjects] Starting object creation of (shellyplusplugs / shellyplusplugs-e465b85e4500 / shellyplusplugs#e465b85e4500#1) for mode: <not set>
          
          shelly.0
          2025-07-08 10:11:34.796	info	[MQTT] Device with client id "shellyplusplugs-e465b85e4500" connected from 192.168.178.44!
          
          shelly.0
          2025-07-08 10:11:34.795	debug	[MQTT] Destroying
          
          shelly.0
          2025-07-08 10:11:34.795	debug	[BaseClient] Destroying 192.168.178.44 (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 10:11:34.795	debug	[MQTT] Client connected: {"cmd":"connect","retain":false,"qos":0,"dup":false,"length":82,"topic":null,"payload":null,"protocolId":"MQTT","protocolVersion":4,"will":{"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}},"clean":true,"keepalive":60,"clientId":"shellyplusplugs-e465b85e4500","username":"mqttuser","password":{"type":"Buffer","data":[109,113,116,116,117,115,101,114]}}
          
          shelly.0
          2025-07-08 10:11:34.794	debug	[MQTT Server] New connection from 192.168.178.44
          
          shelly.0
          2025-07-08 10:11:33.660	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126839
          
          shelly.0
          2025-07-08 10:11:29.209	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0, qos: 0, payload: on
          
          shelly.0
          2025-07-08 10:11:29.208	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/energy, qos: 0, payload: 66761
          
          shelly.0
          2025-07-08 10:11:29.207	debug	[MQTT] Publish: 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1) - topic: shellies/Backofen/relay/0/power, qos: 0, payload: 0.00
          
          host.iobroker
          2025-07-08 10:11:24.910	info	instance system.adapter.dwd.0 having pid 27773 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          
          dwd.0
          2025-07-08 10:11:23.252	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          
          shelly.0
          2025-07-08 10:11:18.409	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.rssi, value: -63
          
          shelly.0
          2025-07-08 10:11:18.409	debug	[httpIoBrokerState] State change 192.168.178.43 (shellyplug / shellyplug-8FF28C / SHPLG-1#8FF28C#1): state: SHPLG-1#8FF28C#1.uptime, value: 1126824
          
          shelly.0
          2025-07-08 10:11:12.338	error	[MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-e465b85e4500"
          
          shelly.0
          2025-07-08 10:11:12.291	debug	[setIP] New IP for device undefined: 192.168.178.44 (source: MQTT connect)
          
          shelly.0
          2025-07-08 10:11:12.291	debug	[MQTT] Last will for client id "shellyplusplugs-e465b85e4500" saved: {"retain":true,"qos":0,"topic":"Fridge/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 10:11:12.290	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 10:11:12.258	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-b0a7324c9984"
          
          shelly.0
          2025-07-08 10:11:12.149	debug	[setIP] New IP for device undefined: 192.168.178.76 (source: MQTT connect)
          
          shelly.0
          2025-07-08 10:11:12.148	debug	[MQTT] Last will for client id "shellyplus1-b0a7324c9984" saved: {"retain":true,"qos":0,"topic":"shellyplus1-b0a7324c9984/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 10:11:12.147	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          
          shelly.0
          2025-07-08 10:11:12.144	error	[MQTT] Unable to get mqttprefix of client with id "shellyplus1-441793ab4310"
          
          shelly.0
          2025-07-08 10:11:12.073	debug	[setIP] New IP for device undefined: 192.168.178.63 (source: MQTT connect)
          
          shelly.0
          2025-07-08 10:11:12.073	debug	[MQTT] Last will for client id "shellyplus1-441793ab4310" saved: {"retain":true,"qos":0,"topic":"shellyplus1-441793ab4310/online","payload":{"type":"Buffer","data":[102,97,108,115,101]}}
          
          shelly.0
          2025-07-08 10:11:12.073	debug	[createObjects] Finished object creation of (undefined / undefined / undefined)
          

          was kann ich tun?

          mcm1957M Online
          mcm1957M Online
          mcm1957
          wrote on last edited by
          #36

          @icebear
          Das Problem ist bekannt. Die Ursache leider nicht. @haus-automatisierung konnte bisher keine Ursache eingrenzen und daher leider auch nichts unternehmen.

          Siehe z.B.
          https://github.com/iobroker-community-adapters/ioBroker.shelly/issues/931

          Danke jedenfalls für den Log.

          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
          Support Repositoryverwaltung.

          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

          LESEN - gute Forenbeitrage

          1 Reply Last reply
          1
          • haus-automatisierungH haus-automatisierung

            @rene55 Version 10.1.0 sollte den Schlüssel bestätigen und entsprechend mit ack true neu schreiben.

            Rene55R Offline
            Rene55R Offline
            Rene55
            wrote on last edited by
            #37

            @haus-automatisierung Mit 10.1.0 und nochmaligem Eingeben des Encryption-Keys ist er jetzt ohne Bindestriche und bestätigt.

            Host: Fujitsu Intel(R) Pentium(R) CPU G4560T, 32 GB RAM, Proxmox 8.x + lxc Ubuntu 22.04
            ioBroker (8 GB RAM) Node.js: 20.19.1, NPM: 10.8.2, js-Controller: 7.0.6, Admin: 7.6.3
            Wetterstation: Froggit WH3000SE V1.6.6

            1 Reply Last reply
            1
            • mcm1957M mcm1957
              Aktuelle Test Version 10.4.1
              Veröffentlichungsdatum 3.11.2025
              Github Link https://github.com/iobroker-community-adapters/ioBroker.shelly

              Zum Thema Shelly gibt es mehrere aktive Topics. Bitte das am besten passende Topic benutzen:

              Shelly Topics
              Shelly ALPHA Tests https://forum.iobroker.net/topic/80649/test-adapter-shelly-alpha-versionen
              Shelly STABLE Fragen https://forum.iobroker.net/topic/81297/shelly-adapter-genereller-support

              Für den Adapter ioBroker.shelly steht eine neue Release im BETA / LATEST Repository (ab dem nächsten Update) zu Testzwecken zur Verfügung.

              Hinweis:
              Dieses Topic behandelt die offizielle LATEST Version des Adapters. Informationen zu ALPHA Versionen findet sich hier: https://forum.iobroker.net/topic/80649/test-adapter-shelly-alpha-versionen

              Feedback jeder Art - insbesondere auch ok - funktioniert ist gerne gesehen.

              Changelog

              9.3.0 (2025-04-14)

              • (@klein0r) Adapter requires admin 7.4.10 now.
              • (@mcm1957) Added Shelly Outdoor Plug S Gen3
              • (@mcm1957) Missing energy values for Switches (i.e. Shelly Outdoor Plug S Gen3) have been added
              • (@mcm1957) Missing energy values for pmminigen3 have been added

              9.4.0 (2025-04-16)

              • (@klein0r) Added Gen4 devices (see documentation for details)

              9.4.1 (2025-04-17)

              • (@mcm1957) Minimum value for min_brightness fixed for dimmer1/2 [#1166]

              9.5.0 (2025-05-03)

              • (@mcm1957) Added Shelly Pro Dimmer 0/1-10V PM (shellypro0110pm).
              • (@mcm1957) Added Shelly Pro RGBWW PM (shellyprorgbwwpm) - Note: CCT component still missing.
              • (@mcm1957) Added Shelly AZ Plug (shellyazplug).
              • (@mcm1957) Added Shelly EM Gen 3 (shellyemg3).
              • (@mcm1957) Added 'total returned energy' to Gen2+ EM devices.
              • (@mcm1957) Added 'Relay' to Shelly Pro EM 50 [#1038].
              • (@mcm1957) Added Ogemray 25A (ogemray25a).
              • (@mcm1957) Added energy states to Shelly Plus RBGW PM (shellyrgbwpm) [#1099].
              • (@mcm1957) Added energy states to Shelly Pro Dimmer 1 PM (shellyprodm1pm) [#1129].
              • (@mcm1957) Added energy states to Shelly Pro Dimmer 2 PM (shellyprodm2pm) [#1067, #1056, #1037].
              • (@mcm1957) Added energy states to Shelly Plus 0-10V Dimmer Gen 3 (shelly0110dimg3) [#1103].

              9.5.1 (2025-05-10)

              • (@mcm1957) ATTENTION: Reworked configuration of inputs could effect some devices.
              • (@mcm1957) ResetPower has been added to Shelly switches supporting power measurement. [#1156]
              • (@mcm1957) ResetPower has been added to Gen2+ PM type devices.
              • (@mcm1957) Shelly Plus Uni (shellyplusuni) - configuration of inputs reworked.
              • (@mcm1957) Shelly Plus Uni (shellyplusuni) - support to reset counters added.
              • (@mcm1957) Added sensors (Temperature, Voltmeter, Humidity, analog Input) to Shelly Plus Uni (shellyplusuni).
              • (@mcm1957) Issues reported by repositor checker have been fixed.
              • (@mcm1957) Dependencies have been updated

              10.0.0 (2025-05-30)

              • (@klein0r) Moved BTHome decoding to adapter (save memory on devices)
              • (@klein0r) Allow encrypted payloads of BTHome devices (set encryption key in state)

              10.1.0 (2025-06-30)

              • (@klein0r) Allow infinite event listeners
              • (@klein0r) Added transformed voltage for voltmeter
              • (@klein0r) Improved logging of mqtt authentication failures
              • (@klein0r) Acknowledge new encryption keys for bthome encryption

              10.2.0 (2025-09-09)

              • (@mcm1957) Role definitions for anergy states has been corrected [#1195].
              • (@mcm1957) Shelly Dali Dimmer Gen 3 (shellyddimmerg3) has been added.
              • (@mcm1957) Shelly1L Gen 3 (shelly1lg3) has been added.
              • (@mcm1957) Shelly2L Gen 3 (shelly2lg3) has been added.
              • (@mcm1957) Shelly2PM Gen 4 (shelly2pmg4) has been added. (*)
              • (@klein0r) Shelly Shutter Gen 3 (shellyshutter) has been added.
              • (@klein0r) admin 7.6.17 and js-controller 6.0.11 (or later) are required now.
              • (@mcm1957) Dependencies have been updated

              10.3.0 (2025-10-06)

              • (@klein0r) Rssi for ble has been added to script.
              • (@mcm1957) Shelly Flood Gen 4 (shellyfloodg4) has been added.
              • (@mcm1957) Shelly Power Strip Gen 4 (shellypstripg4) has been added with partial support. (*)

              (*) slat functionality not yet implemented

              10.4.0 (2025-10-13)

              • (@mcm1957) Slat control added to Shelly ProDualCoverPM, Shelly Pro2PM, Shelly Shutter, Shelly Plus 2PM, Shelly 2PM Gen 3 and Shelly 2PM Gen 4.
              • (@mcm1957) Log adapter version if unknown device is detected.
              • (@mcm1957) posControl indicator has been added to devices supporting cover operation.
              • (@mcm1957) Dependencies have been updated

              10.4.1 (2025-11-03)

              • (@mcm1957) Shelly pro 3em400 has been added as dedicated device to improve detectio (shellypro3em400) [#1269].
              • (@mcm1957) Missing energy states have been added to Shelly Dimmer Gen 3 (shellydimmerg3) [#1274].
              • (@klein0r) Added distance support to ble sensors
              • (@mcm1957) Dependencies have been updated
              HumidorH Offline
              HumidorH Offline
              Humidor
              wrote on last edited by Humidor
              #38

              @mcm1957 Hallo! erstmal wieder Danke für eure tolle Arbeit!
              ich habe auf die letzte Version vom Adapter und das 1.0 Script für die BLE installiert.
              Leider bekomme ich keine Infos mehr von den BLE BT Geräten mehr?
              Tja, wo muss ich denn da jetzt nachsehen? BG
              in der Shelly App sind die Geräte drin und zeigen den korrekten Zustand
              im Shelly BLE Server ist das Script 1.0 gestartet und läuft

              -> hab grad nachgesehen, das Script ist nicht gelaufen, ich habe es gestartet, OK.. neu gestartet und JA es funktoniert natürlich wieder ! 👍

              BG

              mcm1957M 1 Reply Last reply
              1
              • HumidorH Humidor

                @mcm1957 Hallo! erstmal wieder Danke für eure tolle Arbeit!
                ich habe auf die letzte Version vom Adapter und das 1.0 Script für die BLE installiert.
                Leider bekomme ich keine Infos mehr von den BLE BT Geräten mehr?
                Tja, wo muss ich denn da jetzt nachsehen? BG
                in der Shelly App sind die Geräte drin und zeigen den korrekten Zustand
                im Shelly BLE Server ist das Script 1.0 gestartet und läuft

                -> hab grad nachgesehen, das Script ist nicht gelaufen, ich habe es gestartet, OK.. neu gestartet und JA es funktoniert natürlich wieder ! 👍

                mcm1957M Online
                mcm1957M Online
                mcm1957
                wrote on last edited by
                #39

                @humidor
                Dankje fürs Feedback. UInd sorry, dass ich nicht früher antworten konnte.

                Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                Support Repositoryverwaltung.

                Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                LESEN - gute Forenbeitrage

                mcm1957M 1 Reply Last reply
                1
                • mcm1957M mcm1957

                  @humidor
                  Dankje fürs Feedback. UInd sorry, dass ich nicht früher antworten konnte.

                  mcm1957M Online
                  mcm1957M Online
                  mcm1957
                  wrote on last edited by
                  #40

                  @mcm1957

                  Release 10.2.0 wurde ins Latest entlassen.
                  Details siehe Releasenotes.

                  Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                  Support Repositoryverwaltung.

                  Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                  LESEN - gute Forenbeitrage

                  mcm1957M 1 Reply Last reply
                  0
                  • mcm1957M mcm1957

                    @mcm1957

                    Release 10.2.0 wurde ins Latest entlassen.
                    Details siehe Releasenotes.

                    mcm1957M Online
                    mcm1957M Online
                    mcm1957
                    wrote on last edited by
                    #41

                    Release 10.2.0 wurde ins STABLE Repository entlassen.

                    Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                    Support Repositoryverwaltung.

                    Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                    LESEN - gute Forenbeitrage

                    mcm1957M 1 Reply Last reply
                    1
                    • mcm1957M mcm1957

                      Release 10.2.0 wurde ins STABLE Repository entlassen.

                      mcm1957M Online
                      mcm1957M Online
                      mcm1957
                      wrote on last edited by
                      #42

                      Release 10.3.0 wurde ins Latest entlassen.
                      Details siehe Releasenotes.

                      Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                      Support Repositoryverwaltung.

                      Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                      LESEN - gute Forenbeitrage

                      1 Reply Last reply
                      2
                      • mcm1957M Online
                        mcm1957M Online
                        mcm1957
                        wrote on last edited by
                        #43

                        Release 10.4.0 wurde ins Latest entlassen.
                        Details siehe Releasenotes.

                        Die wesentliche Änderung ist der Support der slat Funktion (Lamellenneigung) bei allen Shellies die diese Funktion unterstützen.

                        Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                        Support Repositoryverwaltung.

                        Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                        LESEN - gute Forenbeitrage

                        mcm1957M 1 Reply Last reply
                        2
                        • mcm1957M mcm1957

                          Release 10.4.0 wurde ins Latest entlassen.
                          Details siehe Releasenotes.

                          Die wesentliche Änderung ist der Support der slat Funktion (Lamellenneigung) bei allen Shellies die diese Funktion unterstützen.

                          mcm1957M Online
                          mcm1957M Online
                          mcm1957
                          wrote on last edited by mcm1957
                          #44

                          Release 10.4.0 wurde ins STABLE entlassen.

                          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                          Support Repositoryverwaltung.

                          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                          LESEN - gute Forenbeitrage

                          mcm1957M 1 Reply Last reply
                          2
                          • mcm1957M mcm1957

                            Release 10.4.0 wurde ins STABLE entlassen.

                            mcm1957M Online
                            mcm1957M Online
                            mcm1957
                            wrote on last edited by mcm1957
                            #45

                            Release 10.4.1 steht ab morgen im LATEST zum Testen zur Verfügung.

                            User des SHELLY DIMMER G3 bitte testen ob nun die Energieanzeigen vorhanden sind.

                            User des SHELLY PRO 3EM 400 bitte testen ob dieser nun erkannt wird.

                            Und wer schon den DISTANZ SENSOR hat bitte testen ob bei diesem die Distanzanzeige vorhanden ist und funktioniert. (DANKE an Mathias der sichum die BLE kümmert!)

                            Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                            Support Repositoryverwaltung.

                            Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                            LESEN - gute Forenbeitrage

                            FabioF haus-automatisierungH S 3 Replies Last reply
                            3
                            • mcm1957M mcm1957

                              Release 10.4.1 steht ab morgen im LATEST zum Testen zur Verfügung.

                              User des SHELLY DIMMER G3 bitte testen ob nun die Energieanzeigen vorhanden sind.

                              User des SHELLY PRO 3EM 400 bitte testen ob dieser nun erkannt wird.

                              Und wer schon den DISTANZ SENSOR hat bitte testen ob bei diesem die Distanzanzeige vorhanden ist und funktioniert. (DANKE an Mathias der sichum die BLE kümmert!)

                              FabioF Offline
                              FabioF Offline
                              Fabio
                              wrote on last edited by Fabio
                              #46

                              @mcm1957 @haus-automatisierung vielen vielen Dank.👍 👍 👍
                              Herzliche Grüße
                              Fabio

                              Iobroker:

                              • Für mich persöhnlich, gibt es nichts besseres, ich liebe es.

                              • Das hat unser Smarthome erst zu Smarthome gemacht.

                              • Du wächst mit ioBroker und ioBroker wächst mit dir.

                              • Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                              1 Reply Last reply
                              0
                              • mcm1957M mcm1957

                                Release 10.4.1 steht ab morgen im LATEST zum Testen zur Verfügung.

                                User des SHELLY DIMMER G3 bitte testen ob nun die Energieanzeigen vorhanden sind.

                                User des SHELLY PRO 3EM 400 bitte testen ob dieser nun erkannt wird.

                                Und wer schon den DISTANZ SENSOR hat bitte testen ob bei diesem die Distanzanzeige vorhanden ist und funktioniert. (DANKE an Mathias der sichum die BLE kümmert!)

                                haus-automatisierungH Online
                                haus-automatisierungH Online
                                haus-automatisierung
                                Developer Most Active
                                wrote on last edited by
                                #47

                                @mcm1957 sagte in Test Adapter Shelly 10.4.x (LATEST / BETA):

                                Und wer schon den DISTANZ SENSOR hat bitte testen ob bei diesem die Distanzanzeige vorhanden ist und funktioniert.

                                Gerne Feedback liefern - ist blind implementiert worden, da ich das Gerät nicht habe

                                🧑‍🎓 Autor des beliebten ioBroker-Master-Kurses
                                🎥 Tutorials rund um das Thema DIY-Smart-Home: https://haus-automatisierung.com/
                                📚 Meine inoffizielle ioBroker Dokumentation

                                mcm1957M 1 Reply Last reply
                                2
                                • haus-automatisierungH haus-automatisierung

                                  @mcm1957 sagte in Test Adapter Shelly 10.4.x (LATEST / BETA):

                                  Und wer schon den DISTANZ SENSOR hat bitte testen ob bei diesem die Distanzanzeige vorhanden ist und funktioniert.

                                  Gerne Feedback liefern - ist blind implementiert worden, da ich das Gerät nicht habe

                                  mcm1957M Online
                                  mcm1957M Online
                                  mcm1957
                                  wrote on last edited by mcm1957
                                  #48

                                  @haus-automatisierung
                                  Du hast einen Shelly nicht 🙂 ?

                                  DANKE fürs einbaun.

                                  Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                  Support Repositoryverwaltung.

                                  Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                  LESEN - gute Forenbeitrage

                                  haus-automatisierungH 1 Reply Last reply
                                  0
                                  • mcm1957M mcm1957

                                    @haus-automatisierung
                                    Du hast einen Shelly nicht 🙂 ?

                                    DANKE fürs einbaun.

                                    haus-automatisierungH Online
                                    haus-automatisierungH Online
                                    haus-automatisierung
                                    Developer Most Active
                                    wrote on last edited by
                                    #49

                                    @mcm1957 sagte in Test Adapter Shelly 10.4.x (LATEST / BETA):

                                    Du hast einen Shelly nicht ?

                                    Da momentan gefühlt jeden Monat 4 neue Produkte auf den Markt kommen, ist es schwierig dran zu bleiben 🙂

                                    🧑‍🎓 Autor des beliebten ioBroker-Master-Kurses
                                    🎥 Tutorials rund um das Thema DIY-Smart-Home: https://haus-automatisierung.com/
                                    📚 Meine inoffizielle ioBroker Dokumentation

                                    1 Reply Last reply
                                    2
                                    • mcm1957M mcm1957

                                      Release 10.4.1 steht ab morgen im LATEST zum Testen zur Verfügung.

                                      User des SHELLY DIMMER G3 bitte testen ob nun die Energieanzeigen vorhanden sind.

                                      User des SHELLY PRO 3EM 400 bitte testen ob dieser nun erkannt wird.

                                      Und wer schon den DISTANZ SENSOR hat bitte testen ob bei diesem die Distanzanzeige vorhanden ist und funktioniert. (DANKE an Mathias der sichum die BLE kümmert!)

                                      S Offline
                                      S Offline
                                      StealthAngel
                                      wrote on last edited by
                                      #50

                                      @mcm1957 said in Test Adapter Shelly 10.4.x (LATEST / BETA):

                                      Release 10.4.1 steht ab morgen im LATEST zum Testen zur Verfügung.

                                      ....

                                      Und wer schon den DISTANZ SENSOR hat bitte testen ob bei diesem die Distanzanzeige vorhanden ist und funktioniert. (DANKE an Mathias der sichum die BLE kümmert!)

                                      Ich habe einen Distance Sensor. In aber zu blöd den Adapter 10.4.1 zu installieren.
                                      Auch wenn ich das repository auf Beta umstelle kann ich die 10.4.1 nicht installieren.

                                      Kann mir jemand sagen, wie das geht?

                                      Vielen Dank
                                      Andreas

                                      mcm1957M 1 Reply Last reply
                                      0
                                      • S StealthAngel

                                        @mcm1957 said in Test Adapter Shelly 10.4.x (LATEST / BETA):

                                        Release 10.4.1 steht ab morgen im LATEST zum Testen zur Verfügung.

                                        ....

                                        Und wer schon den DISTANZ SENSOR hat bitte testen ob bei diesem die Distanzanzeige vorhanden ist und funktioniert. (DANKE an Mathias der sichum die BLE kümmert!)

                                        Ich habe einen Distance Sensor. In aber zu blöd den Adapter 10.4.1 zu installieren.
                                        Auch wenn ich das repository auf Beta umstelle kann ich die 10.4.1 nicht installieren.

                                        Kann mir jemand sagen, wie das geht?

                                        Vielen Dank
                                        Andreas

                                        mcm1957M Online
                                        mcm1957M Online
                                        mcm1957
                                        wrote on last edited by mcm1957
                                        #51

                                        @stealthangel

                                        Variante 1)
                                        Repositry auf BETA / LATEST umstellen
                                        'Nach Update suchen' (kreisförmiger Pfeil Button oben) - oder warten bis sich dein lokaler Cache neu synchronisiert (1x täglich typisch).
                                        Dann sollte die neue Release angezeigt werden

                                        Variante 2)
                                        Expertenmodus ein
                                        Katze (Guthub Symbol) ankliocken und 'Von npm installieren' auswählen
                                        shelly Adapter auswählen

                                        Variante 3)
                                        Auf der commandline iobroker upgrade shelly@latest

                                        Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                        Support Repositoryverwaltung.

                                        Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                        LESEN - gute Forenbeitrage

                                        S 1 Reply Last reply
                                        0
                                        • mcm1957M mcm1957

                                          @stealthangel

                                          Variante 1)
                                          Repositry auf BETA / LATEST umstellen
                                          'Nach Update suchen' (kreisförmiger Pfeil Button oben) - oder warten bis sich dein lokaler Cache neu synchronisiert (1x täglich typisch).
                                          Dann sollte die neue Release angezeigt werden

                                          Variante 2)
                                          Expertenmodus ein
                                          Katze (Guthub Symbol) ankliocken und 'Von npm installieren' auswählen
                                          shelly Adapter auswählen

                                          Variante 3)
                                          Auf der commandline iobroker upgrade shelly@latest

                                          S Offline
                                          S Offline
                                          StealthAngel
                                          wrote on last edited by StealthAngel
                                          #52

                                          @mcm1957 said in Test Adapter Shelly 10.4.x (LATEST / BETA):

                                          Variante 1)
                                          Repositry auf BETA / LATEST umstellen
                                          'Nach Update suchen' (kreisförmiger Pfeil Button oben) .....

                                          Danke, das hat mir gefehlt.

                                          Jetzt wird die Distanz angezeigt:

                                          7d09a51f-7821-43ad-bff6-02890659799e-image.png

                                          was auch tatsächlich richtig ist 😉

                                          a5c2bdf2-71e8-434a-8ff2-21507775539d-image.png

                                          Schade ist allerdings, dass der Füllstand in % nicht übertragen wird. Liegt aber an der API, da ist der Wert leider nicht vorhanden...

                                          Danke für Eure Arbeit / Mühe

                                          Andreas

                                          mcm1957M haus-automatisierungH 2 Replies Last reply
                                          1
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          720

                                          Online

                                          32.4k

                                          Users

                                          81.4k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe