Beiträge von Juppo

  • ShellyPro4PM Schaltet sich aus

    Same issues here,

    LAN Connection, Unifi Network that assigns a static address, brand new Cat 6 cables.

    I have one of the preorder devices from the initial shipment. The device was working for months without problems just switching with hardware buttons, MQTT was running and just showing the state in
    iobroker shelly.1.shellypro4pm#84cca87ff81c#1.Relay<0-3>.Switch without any further actions.

    A few days ago I decided to switch the pro4pm with 2 shelly motions, one for the ground floor and one for the cellar. The switching was done with the Smartcontrol Adapter Ver. 1.2.1 and Shelly Adapter 5.1.3.

    From this day the pro4pm goes offline no later than 6 to 12 hours (happened about 8 times last week). Black display and only comes back after switching the fuse.

    My suspicion is that the pro4pm dislikes active switch orders over mqtt.

    0.9.1 0.9.3 0.10.0 beta 3 all show the same behavior

    http://192.168.1.240/rpc/Shelly.GetStatus

    Code
    {"ble":{},"cloud":{"connected":false},"eth":{"ip":"192.168.1.240"},"input:0":{"id":0,"state":null},"input:1":{"id":1,"state":null},"input:2":{"id":2,"state":false},"input:3":{"id":3,"state":false},"mqtt":{"connected":true},"switch:0":{"id":0, "source":"init", "output":false, "apower":0.0, "voltage":233.0, "current":0.000, "pf":0.00, "aenergy":{"total":0.171,"by_minute":[0.000,0.000,0.000],"minute_ts":1645092139},"temperature":{"tC":29.9, "tF":85.8}},"switch:1":{"id":1, "source":"init", "output":false, "apower":0.0, "voltage":232.9, "current":0.000, "pf":0.00, "aenergy":{"total":0.915,"by_minute":[0.000,0.000,0.000],"minute_ts":1645092139},"temperature":{"tC":29.9, "tF":85.8}},"switch:2":{"id":2, "source":"init", "output":false, "apower":0.0, "voltage":233.1, "current":0.000, "pf":0.00, "aenergy":{"total":0.000,"by_minute":[0.000,0.000,0.000],"minute_ts":1645092139},"temperature":{"tC":29.9, "tF":85.8}},"switch:3":{"id":3, "source":"init", "output":false, "apower":0.0, "voltage":233.2, "current":0.000, "pf":0.00, "aenergy":{"total":0.000,"by_minute":[0.000,0.000,0.000],"minute_ts":1645092139},"temperature":{"tC":29.9, "tF":85.8}},"sys":{"mac":"84CCA87FF81C","restart_required":false,"time":"11:02","unixtime":1645092141,"uptime":331,"ram_size":235436,"ram_free":146656,"fs_size":524288,"fs_free":290816,"cfg_rev":21,"available_updates":{"beta":{"version":"0.10.0-beta3"}}},"ui":{},"wifi":{"sta_ip":null,"status":"disconnected","ssid":null,"rssi":0}}

    http://192.168.1.240/rpc/Shelly.GetDeviceInfo

    Code
    {"name":"ShellyPro4 Treppenhauslicht","id":"shellypro4pm-84cca87ff81c","mac":"84CCA87FF81C","model":"SPSW-004PE16EU","gen":2,"fw_id":"20220117-162030/0.9.3-g354c141","ver":"0.9.3","app":"Pro4PM","auth_en":false,"auth_domain":null}

    http://192.168.1.240/rpc/mqtt.GetStatus

    Code
    {"connected":true}

    http://192.168.1.240/rpc/Shelly.getconfig

    Code
    {"ble":{"enable":false},"cloud":{"enable":false,"server":"iot.shelly.cloud:6012/jrpc"},"eth":{"enable":true,"ipv4mode":"dhcp","ip":null,"netmask":null,"gw":null,"nameserver":null},"input:0":{"id":0, "name":null, "type":"button", "invert":false},"input:1":{"id":1, "name":null, "type":"button", "invert":false},"input:2":{"id":2, "name":null, "type":"switch", "invert":false},"input:3":{"id":3, "name":null, "type":"switch", "invert":false},"mqtt":{"enable":true,"server":"192.168.1.116:1883","user":"mqttuser","pass":"paul","topic_prefix":"shellypro4pm-84cca87ff81c","rpc_ntf":true,"status_ntf":true},"switch:0":{"id":0, "name":"Treppenhaus UG","in_mode":"momentary","initial_state":"off", "auto_on":false, "auto_on_delay":60.00, "auto_off":true, "auto_off_delay": 120.00,"power_limit":4480,"voltage_limit":280,"current_limit":16.000},"switch:1":{"id":1, "name":"Treppenhaus EG","in_mode":"momentary","initial_state":"off", "auto_on":false, "auto_on_delay":60.00, "auto_off":true, "auto_off_delay": 120.00,"power_limit":4480,"voltage_limit":280,"current_limit":16.000},"switch:2":{"id":2, "name":null,"in_mode":"follow","initial_state":"match_input", "auto_on":false, "auto_on_delay":60.00, "auto_off":false, "auto_off_delay": 60.00,"power_limit":4480,"voltage_limit":280,"current_limit":16.000},"switch:3":{"id":3, "name":null,"in_mode":"follow","initial_state":"match_input", "auto_on":false, "auto_on_delay":60.00, "auto_off":false, "auto_off_delay": 60.00,"power_limit":4480,"voltage_limit":280,"current_limit":16.000},"sys":{"device":{"name":"ShellyPro4 Treppenhauslicht","mac":"84CCA87FF81C","fw_id":"20220117-162030/0.9.3-g354c141","eco_mode":false},"location":{"tz":"Europe/Berlin","lat":50.937930,"lon":6.878530},"debug":{"mqtt":{"enable":false},"websocket":{"enable":false},"udp":{"addr":null}},"ui_data":{},"rpc_udp":{"dst_addr":null,"listen_port":null},"sntp":{"server":"time.google.com"},"cfg_rev":21},"ui":{"idle_brightness":30},"wifi":{"ap":{"ssid":"ShellyPro4PM-84CCA87FF81C","is_open":true, "enable":false},"sta":{"ssid":null,"is_open":true, "enable":false, "ipv4mode":"dhcp","ip":null,"netmask":null,"gw":null,"nameserver":null},"sta1":{"ssid":null,"is_open":true, "enable":false, "ipv4mode":"dhcp","ip":null,"netmask":null,"gw":null,"nameserver":null},"roam":{"rssi_thr":-80,"interval":60}}}

  • Firmware Update fail (gelöst)

    Nach Kontakt zum Shelly Support ist in meinem Fall bestätigt dass beide Motion mit einer fehlerhaften Firmware ausgeliefert worden sind und zurück müssen.

    Falls noch jemand die master@36b0b4c9+ Firmware installiert hat welche Probleme bereitet (kein Update möglich), soll er sich direkt an den Support wenden mit dem Output von http://deviceIP/status and http://deviceIP/settings. Dort wird dann entschieden ob das Gerät ausgetauscht werden muss.

  • Firmware Update fail (gelöst)

    Zitat

    Diesen Fehler hatte ich auch, da ich einige Shelly PW geschütz habe, habe ich den Motion auch PW geschützt und der Fehler war sofort weg. Im Adapter natürlich das Pw auch eintragen.

    Ich habe 20+ Geräte davon ca. 5 mit PW, die andern laufen, obwohl im ioBroker ein PW gesetzt ist, alle ohne Fehler.

    Komisch das der Motion explizit das PW braucht, denn mit dem PW ist zumindest dieser Fehler weg, danke.

    Leider keine guten Neuigkeiten aus der Firmware Ecke, Cloud aktiv/deaktiviert MQTT aktiv/deaktiviert kein Update möglich.

    Sobald der Haken (ioBroker, Shelly Adapter) hier gesetzt war, blinkte der Motion ununterbrochen Rot/Blau im ms Takt, sah schon fast aus wie Lila, daher nehme ich an er will das Update schon machen, schafft es nur nicht bis zum Ende.

    SM4.png

  • Firmware Update fail (gelöst)

    Hallo alle,

    ich habe gestern 2 Shelly Motion bekommen, allerdings beide mit Problemen.

    Der 1. Motion lässt sich zumindest im Netz unter seiner neuen festen IP finden, macht aber kein Update.

    Code
    http://192.168.178.235/ota?url=http://repo.shelly.cloud/firmware/SHMOS-01_build.gbl ->
    Code
    {
"status": "updating","has_update": true,"new_version": "20210226-072307/v1.1.0@f31e1d2b","old_version": "20210122-122838/master@36b0b4c9+"
}

    darauf blinkt er langsam 5 sek. blau, dann 3 sek. schnell blau und dann 4 sek rot und das wars.

    Weboberfläche zeigt immer SM1.png

    Ich habe es bestimmt schon min. 20x probiert (Web, Link, Handy). Inkl. zig mal Reset (10 Sek).

    Ich vermute dass auch die alte Firmware folgende Fehler im ioBroker auslöst

    Code
    shelly.0    2021-03-03 09:06:31.589    error    (13717) Error in function httpIoBrokerState for state SHMOS-01#60A4239A6D88#1.name and request{"url":"http://192.168.1.235/settings","timeout":5000,"headers":{"Authorization":"Basic YWRtaW46cGF1bCQyN
shelly.0    2021-03-03 09:06:31.589    error    (13717) Error in function httpIoBrokerState for state SHMOS-01#60A4239A6D88#1.version and request{"url":"http://192.168.1.235/settings","timeout":5000,"headers":{"Authorization":"Basic YWRtaW46cGF1bC
shelly.0    2021-03-03 09:06:31.572    error    (13717) Error in function httpIoBrokerState for state SHMOS-01#60A4239A6D88#1.rssi and request{"url":"http://192.168.1.235/status","timeout":5000,"headers":{"Authorization":"Basic YWRtaW46cGF1bCQyNA=
shelly.0    2021-03-03 09:06:31.572    error    (13717) Error in function httpIoBrokerState for state SHMOS-01#60A4239A6D88#1.hostname and request{"url":"http://192.168.1.235/status","timeout":5000,"headers":{"Authorization":"Basic YWRtaW46cGF1bCQ
shelly.0    2021-03-03 09:06:31.571    error    (13717) Error in function httpIoBrokerState for state SHMOS-01#60A4239A6D88#1.uptime and request{"url":"http://192.168.1.235/status","timeout":5000,"headers":{"Authorization":"Basic YWRtaW46cGF1bCQyN
shelly.0    2021-03-03 09:06:31.571    error    (13717) Error in function httpIoBrokerState for state SHMOS-01#60A4239A6D88#1.firmware and request{"url":"http://192.168.1.235/status","timeout":5000,"headers":{"Authorization":"Basic YWRtaW46cGF1bCQ


    Der 2. Motion bleibt immer unter der 192.168.33.1 hier hängen und ist nicht ansprechbar

    SM2.png

    SM3.png

    evtl. hat einer eine Idee bevor die 2 zurückgehen.

    Danke euch,

    Jupp