NEWS

Umzug Windows -> Pi 4 - Shellys werden nicht gefunden


  • Starter

    Hallo,

    nachdem ich von Windows auf einen Pi4 mit Raspbian umgestiegen bin, findet der Shelly-Adapter von meinen Shellys nur einen "Shelly 1". Es fehlen 3 "Shelly 1" und ein "Shelly 2.5".

    Der Pi4 hängt über WLAN im Netzwerk und die dhcpd.conf hab ich wie folgt konfiguriert:

    interface wlan0
    static ip_address=192.168.2.141/24
    static routers=192.168.2.1
    static domain_name_servers=192.168.2.1

    Auf der Windows-Installation hat er alle Shellys problemlos gefunden.

    Mich macht stutzig, dass er einen Shelly findet, obwohl alle gleich konfiguriert sind (IP per DHCP, COAP, kein Passwort, Cloud aktiviert, aktuellste FW).

    Hat jemand vielleicht irgendwelche Tipps?

    Vielen Dank im Voraus!


  • Starter

    Re: Umzug Windows -> Pi 4 - Shellys werden nicht gefunden

    Hier noch das debuglog des Shelly-Adapters:

    2020-03-14 21:47:30.490 - info: host.raspberrypi instance system.adapter.shelly.0 started with pid 1782
    2020-03-14 21:47:31.661 - debug: shelly.0 (1782) Redis Objects: Use Redis connection: 127.0.0.1:9003
    2020-03-14 21:47:31.705 - debug: shelly.0 (1782) Objects client ready ... initialize now
    2020-03-14 21:47:31.725 - debug: shelly.0 (1782) Objects create System PubSub Client
    2020-03-14 21:47:31.727 - debug: shelly.0 (1782) Objects create User PubSub Client
    2020-03-14 21:47:31.728 - debug: shelly.0 (1782) Objects client initialize lua scripts
    2020-03-14 21:47:31.743 - debug: shelly.0 (1782) Objects connected to redis: 127.0.0.1:9003
    2020-03-14 21:47:31.748 - debug: shelly.0 (1782) objectDB connected
    2020-03-14 21:47:31.750 - debug: shelly.0 (1782) Redis States: Use Redis connection: 127.0.0.1:9002
    2020-03-14 21:47:31.757 - debug: shelly.0 (1782) States create User PubSub Client
    2020-03-14 21:47:31.760 - debug: shelly.0 (1782) States create System PubSub Client
    2020-03-14 21:47:31.769 - debug: shelly.0 (1782) States connected to redis: 127.0.0.1:9002
    2020-03-14 21:47:31.770 - debug: shelly.0 (1782) statesDB connected
    2020-03-14 21:47:32.674 - info: shelly.0 (1782) starting. Version 3.2.2 in /opt/iobroker/node_modules/iobroker.shelly, node: v12.16.1
    2020-03-14 21:47:32.722 - info: shelly.0 (1782) Starting Shelly adapter in CoAP modus.
    2020-03-14 21:47:32.786 - info: shelly.0 (1782) Listening for Shelly packets in the network
    2020-03-14 21:47:38.728 - debug: shelly.0 (1782) CoAP status package received: {"3332":"SHSW-1#F39F06#1","3412":38400,"3420":1024,"Uri-Path":"cit/s"} / {"G":[[0,112,0],[0,118,0]]}
    2020-03-14 21:47:38.731 - debug: shelly.0 (1782) Status update received for SHSW-1#F39F06#1: {"G":[[0,112,0],[0,118,0]]}
    2020-03-14 21:47:38.733 - debug: shelly.0 (1782) CoAP device description request for SHSW-1#F39F06#1 to 192.168.2.115(0)
    2020-03-14 21:47:38.768 - debug: shelly.0 (1782) CoAP response: {"3332":"SHSW-1#F39F06#1"}
    2020-03-14 21:47:38.769 - debug: shelly.0 (1782) Device description received: {"3332":"SHSW-1#F39F06#1"} / {"blk":[{"I":0,"D":"Relay0"},{"I":1,"D":"Sensors"}],"sen":[{"I":112,"T":"S","D":"Switch","R":"0/1","L":0},{"I":118,"T":"S","D":"Input","R":"0(off)/1(on)/2(longpush)","L":0}]}
    2020-03-14 21:47:38.774 - info: shelly.0 (1782) Shelly device 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1) with CoAP connected!
    2020-03-14 21:47:38.801 - debug: shelly.0 (1782) CoAP Message for SHSW-1#F39F06#1 : {"G":[[0,112,0],[0,118,0]]}
    2020-03-14 21:47:38.802 - debug: shelly.0 (1782) Create State : SHSW-1#F39F06#1.Relay0.Switch, Payload: {"G":[[0,112,0],[0,118,0]]} for SHSW-1#F39F06#1
    2020-03-14 21:47:38.802 - debug: shelly.0 (1782) Create State : SHSW-1#F39F06#1.Relay0.Switch, Payload: [object Object] for SHSW-1#F39F06#1
    2020-03-14 21:47:38.803 - debug: shelly.0 (1782) State change : SHSW-1#F39F06#1.Relay0.Switch, Value: false for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.048 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.Relay0.AutoTimerOff, Value: 900 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.050 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.Relay0.AutoTimerOn, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.051 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.version, Value: "20200312-123713/v1.6.1@112262fd" for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.155 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.ext.temperatureC1, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.156 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.ext.temperatureC2, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.157 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.ext.temperatureC3, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.158 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.ext.temperatureC4, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.158 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.ext.temperatureF1, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.159 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.ext.temperatureF2, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.160 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.ext.temperatureF3, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.161 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.ext.temperatureF4, Value: 0 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.161 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.firmware, Value: false for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.162 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.uptime, Value: "00:35:45" for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.163 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.hostname, Value: "192.168.2.115" for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    2020-03-14 21:47:39.164 - debug: shelly.0 (1782) Set state SHSW-1#F39F06#1.rssi, Value: -64 for 192.168.2.115 (shelly1 / shelly1-F39F06 / SHSW-1#F39F06#1)
    

    Und hier die ifconfig:

    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 192.168.2.141  netmask 255.255.255.0  broadcast 192.168.2.255
            inet6 fe80::efe7:4e69:b994:3b89  prefixlen 64  scopeid 0x20<link>
            inet6 2003:f9:13ca:e54c:fb18:66fb:da85:3b35  prefixlen 64  scopeid 0x0<global>
            ether dc:a6:32:7b:7c:15  txqueuelen 1000  (Ethernet)
            RX packets 20944  bytes 2774911 (2.6 MiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 29523  bytes 13543653 (12.9 MiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    

    EDIT: Mir war der Speedport Smart3 schon länger ein Dorn im Auge, weshalb ich meine Fritzbox 7490 wieder rausgekramt habe. Jetzt klappt alles ohne Probleme! Denke, dass der Speedport ein Problem mit Coap bzw. Multicast bei WLAN <-> WLAN hat...



Suggested Topics

2.0k
Online

32.2k
Users

38.8k
Topics

526.5k
Posts