Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[Thomas Braun]

@daniel-driessen sagte in Shelly Adapter: Warnung "Verbunden mit Gerät oder Dienst":

Leider finde ich diese Meldung nicht so richtig aussagekräftig. Daher fehlt mir leider der richtige Ansatz worin das Problem genau liegen soll.

Schau in das log file.
Z. B. mit

iobroker logs --watch

und starte den Adapter derweil mal neu.

[daniel.driessen]

@thomas-braun
Habe ich schon gemacht. Ist nichts auffälliges da.

[Thomas Braun]

@daniel-driessen
Bitte keine Screenshots vom log file.
Als Text in CodeTags </> hier rein. Und auch nichts rausfiltern.

[daniel.driessen]

@thomas-braun
Ah Ok. Sorry, das wusste ich nicht.
Nichts rausfiltern bedeutet auch nichts von anderen Adaptern?
Und welche Log-Stufe. "Silly"? "Debug"?
Danke nochmals für die Hilfe.

[Thomas Braun]

@daniel-driessen
Erstmal auf info lassen. Der Adapter-Neustart wird nämlich vom host geloggt, deswegen nicht auf Adapter-Ebene filtern.

[daniel.driessen]

@thomas-braun
OK. Hier ist der Log:

2021-05-29 17:54:09.364 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:09.425 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:12.351 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:12.383 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:15.084 - info: host.ioBrokerServer stopInstance system.adapter.shelly.0 (force=false, process=true)
2021-05-29 17:54:15.087 - info: host.ioBrokerServer stopInstance system.adapter.shelly.0 send kill signal
2021-05-29 17:54:15.088 - info: shelly.0 (166891) Got terminate signal TERMINATE_YOURSELF
2021-05-29 17:54:15.090 - info: shelly.0 (166891) Closing Adapter
2021-05-29 17:54:15.090 - info: shelly.0 (166891) terminating
2021-05-29 17:54:15.091 - info: shelly.0 (166891) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-05-29 17:54:15.354 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:15.429 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:15.645 - info: host.ioBrokerServer instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-05-29 17:54:18.134 - info: host.ioBrokerServer instance system.adapter.shelly.0 started with pid 823184
2021-05-29 17:54:18.353 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:18.391 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:19.036 - info: shelly.0 (823184) starting. Version 4.0.8 in /opt/iobroker/node_modules/iobroker.shelly, node: v12.22.1, js-controller: 3.3.11
2021-05-29 17:54:19.047 - info: shelly.0 (823184) Starting Adapter shelly.0 in version 4.0.8
2021-05-29 17:54:19.160 - info: shelly.0 (823184) Starting Shelly adapter in CoAP modus.
2021-05-29 17:54:19.186 - info: shelly.0 (823184) Listening for Shelly packets in the network
2021-05-29 17:54:20.371 - info: shelly.0 (823184) Shelly device 192.168.2.102 (shelly1pm / shelly1pm-68C63AFB6573 / SHSW-PM#68C63AFB6573#1) with CoAP connected! Polltime set to 5 sec.
2021-05-29 17:54:20.414 - info: shelly.0 (823184) Shelly device 192.168.2.105 (shelly1pm / shelly1pm-A4CF12F3CF0C / SHSW-PM#A4CF12F3CF0C#1) with CoAP connected! Polltime set to 5 sec.
2021-05-29 17:54:21.368 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:21.437 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:24.354 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:24.392 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:24.471 - info: shelly.0 (823184) Shelly device 192.168.2.100 (shelly1pm / shelly1pm-68C63AFB35AE / SHSW-PM#68C63AFB35AE#1) with CoAP connected! Polltime set to 5 sec.
2021-05-29 17:54:25.339 - info: shelly.0 (823184) Shelly device 192.168.2.101 (shellyswitch25 / shellyswitch25-BA8EC3 / SHSW-25#BA8EC3#1) with CoAP connected! Polltime set to 5 sec.
2021-05-29 17:54:25.531 - info: shelly.0 (823184) Shelly device 192.168.2.104 (shelly1pm / shelly1pm-40F5200142BA / SHSW-PM#40F5200142BA#1) with CoAP connected! Polltime set to 5 sec.
2021-05-29 17:54:26.982 - info: shelly.0 (823184) Shelly device 192.168.2.106 (shellyswitch25 / shellyswitch25-40F520050002 / SHSW-25#40F520050002#1) with CoAP connected! Polltime set to 5 sec.
2021-05-29 17:54:27.336 - info: shelly.0 (823184) Shelly device 192.168.2.103 (shellyswitch25 / shellyswitch25-40F5200499F7 / SHSW-25#40F5200499F7#1) with CoAP connected! Polltime set to 5 sec.
2021-05-29 17:54:27.361 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:27.402 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:30.358 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:30.433 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:33.358 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:33.392 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:36.358 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:36.433 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:39.358 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:39.433 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:42.358 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:42.390 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:45.368 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:45.449 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:48.362 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:48.395 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:51.362 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:51.395 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:53.493 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Wohnzimmer.Temperature.DewPoint" has to be type "number" but received type "string"
2021-05-29 17:54:53.493 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Wohnzimmer.Humidity.AbsoluteHumidity" has to be type "number" but received type "string"
2021-05-29 17:54:53.493 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Wohnzimmer.LastUpdate" has to be type "datetime" but received type "string"
2021-05-29 17:54:53.511 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Außen.Temperature.DewPoint" has to be type "number" but received type "string"
2021-05-29 17:54:53.511 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Außen.Humidity.AbsoluteHumidity" has to be type "number" but received type "string"
2021-05-29 17:54:53.512 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Außen.LastUpdate" has to be type "datetime" but received type "string"
2021-05-29 17:54:53.512 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Badezimmer.Temperature.DewPoint" has to be type "number" but received type "string"
2021-05-29 17:54:53.512 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Badezimmer.Humidity.AbsoluteHumidity" has to be type "number" but received type "string"
2021-05-29 17:54:53.512 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Badezimmer.LastUpdate" has to be type "datetime" but received type "string"
2021-05-29 17:54:53.553 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Garage.Temperature.DewPoint" has to be type "number" but received type "string"
2021-05-29 17:54:53.553 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Garage.Humidity.AbsoluteHumidity" has to be type "number" but received type "string"
2021-05-29 17:54:53.554 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Garage.LastUpdate" has to be type "datetime" but received type "string"
2021-05-29 17:54:53.555 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Schlafzimmer.Temperature.DewPoint" has to be type "number" but received type "string"
2021-05-29 17:54:53.555 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Schlafzimmer.Humidity.AbsoluteHumidity" has to be type "number" but received type "string"
2021-05-29 17:54:53.555 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Schlafzimmer.LastUpdate" has to be type "datetime" but received type "string"
2021-05-29 17:54:53.555 - info: netatmo.0 (3882) State value to set for "netatmo.0.Home-(Wohnzimmer).Regen.LastUpdate" has to be type "datetime" but received type "string"
2021-05-29 17:54:54.362 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:54.393 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:54:57.363 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:54:57.437 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:55:00.366 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:55:00.395 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:55:03.366 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:55:03.395 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:55:06.366 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:55:06.437 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:55:09.371 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:55:09.457 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:55:12.366 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:55:12.401 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:55:15.370 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:55:15.441 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"
2021-05-29 17:55:18.370 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.currentspeed.coresSpeed" has to be stringified but received type "object"
2021-05-29 17:55:18.445 - info: info.0 (2841) State value to set for "info.0.sysinfo.cpu.temperature.cores" has to be stringified but received type "object"

Denke das sollte reichen. Jedenfalls kommt keine Info mehr vom Shelly Adapter.
Wie gesagt. Ich sehe nichts Auffälliges. Aber vielleicht übersehe ich ja etwas.

[da_Woody]

@daniel-driessen welche FW version haben deine shelly? hast du objekte im ioBroker? CoIoT eingestellt?

[daniel.driessen]

@da_woody Hallo Woody,

Hier ist ein Screenshot von einer der Shellys. Sie haben alle die aktuellste Firmware:

Ja, es sind Geräte in den Objekten drin. Es fehlt auch keins. Und alle sind "live":

Und ja, ColoT ist eingestellt wie in der Beschreibung vom Shelly-Adapter vermerkt:

[da_Woody]

@daniel-driessen soweit sollte alles ok sein, warum der adapter nicht grün wird...
eventuell bei der install verschluckt? du kannst versuchen den adapter nochmal zu löschen und neu zu insten.
die 4.0.8 ist eigentlich absolut ok.

[daniel.driessen]

@da_woody OK. Habe ich eigentlich auch schon gemacht.
Wie gesagt, bisher war er eigentlich immer "grün". Warum auf einmal nicht mehr ist mir ein Rätsel.
Ich werde ihn aber nochmals neu installieren. Mal sehen, vielleicht hilft das ja. Trotzdem schonmal vielen Dank für die Hilfe!

[daniel.driessen]

Neuinstallation des Adapters hat leider auch nichts gebracht. Ich bin leider mit meinem Latein am Ende.
Trotzdem danke für die Hilfe!

[Homoran]

@da_Woody
ich habe keine shellies.
der Screenshot sieht nach der alpha admin v5 aus.
hast du auch v5?

[haselchen]

@homoran
@daniel-driessen

Stable ist 4.0.7, also warum Beta Tester spielen?

Das es Probleme geben kann steht sogar im Changelog

[da_Woody]

@homoran ich fahre admin5 und shelly 4.0.8 ohne probleme... ja, ok, der #370er. der ist mir egal. und soweit ich mir erinnern zu können, war die 4.0.7 wo der online rausgenommen wurde. weils mir keine ruhe gelassen hat, gerade mit einem shelly plug-s getestet, online funktioniert.
da fällt mir ein @daniel-driessen hast du vllt in deinem netzwerk updates gemacht? ich hatte ja was ähnliches. da war wie durch geisterhand, ohne änderung in 2 managed switches IGMP snooping aktiv. das mögen die shellys nicht.
irgendwie glaub ich da an ein netzwerk problem...

[BigMike71]

@daniel-driessen
ich habe ebenfalls diesen Fehler!
Da ich am Testen bin habe ich ein komplettes raspi4 system mit iobroker hochgezogen.
aber der Adapter gibt bei mir ebenfalls diesen fehler aus, die shellys laufen aber..

[Pat_]

@daniel-driessen
Hab das gleiche Problem. Hast du was rausgefunden?

---

Sorry.. Habs zu spät gesehen. Bin auf 4.07 zurück. Da läufts.

[RoddiEF]

@pat_ said in Shelly Adapter: Warnung "Verbunden mit Gerät oder Dienst": Bin auf 4.07 zurück. Da läufts.

Ist zwar schon länger her mit der letzten Antwort aber auch Ich hab ewig Experimentiert aber weder Neuinstallation (3x) noch der Beta-Adapter (4.0.9) hat das Problem gelöst. Erst mit Version 4.0.7 wird der Adapter wieder komplett Grün.

[Schimi]

Das gleiche problem habe ich nach dem Update auf 4.10 auch....
Nach einen Downgrade hat es sich auch nicht geändert.... den Adapter zu lösche und neu zu installieren habe ich auch versucht....

Bis auf das "nicht verbunden" funktioniert aber alles ohne probleme....

Edit
alle shellys sind mit MQTT eingebunden

[crunchip]

@roddief sagte in Shelly Adapter: Warnung "Verbunden mit Gerät oder Dienst":

aber weder Neuinstallation (3x) noch der Beta-Adapter (4.0.9) hat das Problem gelöst. Erst mit Version 4.0.7 wird der Adapter wieder komplett Grün.

nützt ja nichts die Adapterversion hin und her zu wechseln, wenn ab einer bestimmten Version CoIot benutzt werden muss, diesbezüglich muss man das auch bei jedem shelly einzeln anpassen und die Geräte neu starten.

@schimi sagte in Shelly Adapter: Warnung "Verbunden mit Gerät oder Dienst":

Das gleiche problem

welches?

[Schimi]

@crunchip

Das meine ich....

wie geschrieben, es funktioniert alles einwandfrei...