Shelly Olsche Posted July 31 Shelly Share Posted July 31 Dear group, Today we released a new firmware version with plenty of fixes and features Gen2 and Gen3 1.4.0 stable for Shelly Plus, Pro and Gen3 devices, that you can update to via the device's local web or app. [1.4.0] 2024-07-31 NOTE: 1.3.3 is a mandatory update before 1.4.0. Devices running versions older than 1.3.3 will not be served 1.4.0. Added KNX Integration Pro3EM Webhooks for total_current_change, total_active_power_change, total_apparent_power_change ProEM, Pro3EM CT types support RGB, RGBW Option to use current brightness, white and rgb values in button_presets and night_mode configuration Light, RGB, RGBW offset argument in Set method Light, RGB, RGBW DimUp, DimDown, DimStop methods Pro devices: emit sys_btn_down, sys_btn_up, sys_btn_push notifications from user button Pro devices: sys_btn_toggle config option to control outputs from user button Pro devices: Virtual Components and BTHome BluGw sys_led_enable toggle Virtual Components Optional id argument in Virtual.Add BTHome Optional id argument in BTHome.AddSensor and BTHome.AddDevice PlusPM Mini, PM Mini reverse config option in PM1 component PlusRGBW PM hf_mode toggle Use both cloud an generic CA bundle for cloud conenction and update checks IPv6 Devices will attempt to obtain a public address using the Neighbour Discovery Protocol. If successful, this address can then be used to reach a Shelly device on the network, and device will include it in MDNS host advertisements. Scripting Virtual APIs Fixed BLE Scanner Fix lifetime issues MQTT Require restart when use_client_cert is changed MQTT Allow more than one outstanding publish request (avoid MQTT queue overflows) Pro3EM Fix crash on phase-to-phase calibration Pro3EM Fix recovery from power_meter_failure error Pro3EM Fix reverse CT measurement in monophase profile PlusPM Mini, Plus1PM Mini, PM Mini, 1PM Mini Fix incorrect frequency reports Scripting Fix create/call ejs script from other script Ethernet Fix updating config parameters for static mode Virtual Components Fix counting of vcs without an owner HTTP: Fix processing of zero-length responses BLE Do not attempt to advertise if BT is not running BLE Update bt-common to fix a UAF in scan results processing Debug logs Fix websocket authentication Changed Update IDF to 5.2.1 Convert ca.pem to binary; ship full CA bundle on Gen3 devices Update mbedtls to 3.5.2 Repartition all 4M devices to reallocate 64K from FS to app Fix PT location for Gen3 devices Shelly.ListTimezones Paginate response BREAKING CHANGE RGB, RGBW Replace HTTP endpoint /light/{id} with /color/{id} BREAKING CHANGE Light, RGB, RGBW Apply night mode regardless of current brightness Light, RGB, RGBW Do not apply min_brightness_on_toggle when night mode is active XMOD1 Change default LED type to plain Local web Added KNX configuration pages WiFi connection status and failure reason BluGw system LED enable/disable Virtual Components and BTHome for Pro devices Show BTHome devices on dashboard Pro3EM actions based on total values Button to enable the websocket debug log Device name in the tab title Pro devices: option to control outputs from user button Fixed Schedule editor crash when invalid body is saved via RPC Invalid status for the second WiFi when only the first one is configured Cover slider not reactive sometimes BTHome information initial fetch BTHome filter only supported webhooks Section contents do not update when changing component type in URL Input field deleting decimals Cover obstacle detection can not be configured Cover auto-recovery can not be configured Cover fix incorrect "position lost" message when cover is closed RPC over UDP can not be configured ProEM actions can not be created Display detached inputs for Light Creating option for VirtualComponents::Enum is not possible sometimes PlugS, PlugUK LED indicator settings can not be configured Pro4PM, ProDualCoverPM Fix missing display settings Pro3EM Fix missing add-on card ProEM, Pro3EM CT types Fix error handling Rework diagnostics button for debug log and device data Changed Unify behavior on setting page save Unify split button Rework status bar Trigger auto detect location via button Load timezones list on setting page open AP and Range extender configuration page rework Rework script editor page Improve PlusRGBW PM color picker Please also see https://shelly-api-docs.shelly.cloud/gen2/changelog for more details. Liebe Gruppe, heute haben wir eine neue Firmware-Version mit vielen Korrekturen und Funktionen Gen2 und Gen3 1.4.0 stable für Shelly Plus, Pro und Gen3 Geräte veröffentlicht, auf die Sie über das lokale Web oder die App des Geräts aktualisieren können. [1.4.0] 2024-07-31 HINWEIS: 1.3.3 ist ein Pflichtupdate vor 1.4.0. Geräte, auf denen ältere Versionen als 1.3.3 laufen, werden nicht mit 1.4.0 versorgt. Hinzugefügt KNX-Integration Pro3EM Webhooks für total_current_change, total_active_power_change, total_apparent_power_change ProEM, Pro3EM CT Typen Unterstützung RGB, RGBW Option zur Verwendung der aktuellen Helligkeits-, Weiß- und RGB-Werte in der button_presets und night_mode Konfiguration Licht-, RGB-, RGBW-Offset-Argument in der Set-Methode Methoden Light, RGB, RGBW DimUp, DimDown, DimStop Pro-Geräte: Senden von sys_btn_down, sys_btn_up, sys_btn_push-Benachrichtigungen von der Benutzer-Taste Pro-Geräte: sys_btn_toggle-Konfigurationsoption zur Steuerung der Ausgänge von der Benutzertaste Pro-Geräte: Virtuelle Komponenten und BTHome BluGw sys_led_enable umschaltbar Virtuelle Komponenten Optionales id-Argument in Virtual.Add BTHome Optionales id-Argument in BTHome.AddSensor und BTHome.AddDevice PlusPM Mini, PM Mini reverse config Option in PM1 Komponente PlusRGBW PM hf_mode umschaltbar Cloud und generisches CA-Bündel für Cloud-Verbindung und Update-Checks verwenden IPv6-Geräte versuchen, über das Neighbour Discovery Protocol eine öffentliche Adresse zu erhalten. Im Erfolgsfall kann diese Adresse dann verwendet werden, um ein Shelly-Gerät im Netzwerk zu erreichen, und das Gerät nimmt sie in MDNS-Hostanzeigen auf. Skripting virtueller APIs Behoben BLE-Scanner Probleme mit der Lebensdauer beheben MQTT Erfordert einen Neustart, wenn use_client_cert geändert wird MQTT Erlaubt mehr als eine ausstehende Veröffentlichungsanfrage (Vermeidung von MQTT-Warteschlangenüberläufen) Pro3EM Behebt Absturz bei Phase-zu-Phase-Kalibrierung Pro3EM Behebung des Fehlers power_meter_failure Pro3EM Behebung der umgekehrten Stromwandlermessung im einphasigen Profil PlusPM Mini, Plus1PM Mini, PM Mini, 1PM Mini Behebung falscher Frequenzberichte Skripting Behebung des Erstellens/Aufrufens eines ejs-Skripts aus einem anderen Skript Ethernet Fehlerbehebung bei der Aktualisierung der Konfigurationsparameter für den statischen Modus Virtuelle Komponenten Fix Zählung von vcs ohne Besitzer HTTP: Korrektur der Verarbeitung von Antworten mit Null-Länge BLE Versucht nicht zu werben, wenn BT nicht läuft BLE bt-common aktualisieren, um einen UAF in der Verarbeitung der Scanergebnisse zu beheben Debug-Protokolle Behebung der Websocket-Authentifizierung Geändert IDF auf 5.2.1 aktualisieren ca.pem in Binärdatei konvertieren; vollständiges CA-Bündel auf Gen3-Geräten ausliefern mbedtls auf 3.5.2 aktualisieren Neupartitionierung aller 4M-Geräte, um 64K von FS auf App umzuverteilen PT-Speicherort für Gen3-Geräte korrigieren Shelly.ListTimezones Antwort paginieren BAHNBRECHENDE VERÄNDERUNG RGB, RGBW Ersetzen des HTTP-Endpunkts /light/{id} durch /color/{id} BAHNBRECHENDE VERÄNDERUNG Licht, RGB, RGBW Nachtmodus unabhängig von der aktuellen Helligkeit anwenden Licht, RGB, RGBW min_brightness_on_toggle nicht anwenden, wenn der Nachtmodus aktiv ist XMOD1 Standard-LED-Typ in einfach ändern Lokales Web hinzugefügt KNX Konfigurationsseiten WiFi Verbindungsstatus und Fehlerursache BluGw System-LED aktivieren/deaktivieren Virtuelle Komponenten und BTHome for Pro Geräte BTHome-Geräte auf dem Dashboard anzeigen Pro3EM-Aktionen basierend auf den Gesamtwerten Schaltfläche zum Aktivieren des Websocket-Debug-Protokolls Gerätename im Tab-Titel Pro-Geräte: Option zur Steuerung der Ausgänge über die Benutzerschaltfläche Behoben Absturz des Zeitplaneditors, wenn ein ungültiger Body über RPC gespeichert wird Ungültiger Status für das zweite WiFi, wenn nur das erste konfiguriert ist Abdeckungsschieber reagiert manchmal nicht BTHome-Informationen beim ersten Abruf BTHome-Filter unterstützte nur Webhooks Abschnittsinhalte werden nicht aktualisiert, wenn der Komponententyp in der URL geändert wird Eingabefeld löscht Nachkommastellen Abdeckungs-Hinderniserkennung kann nicht konfiguriert werden Automatische Wiederherstellung der Abdeckung kann nicht konfiguriert werden Abdeckung korrigiert falsche „Position verloren“-Meldung, wenn Abdeckung geschlossen wird RPC über UDP kann nicht konfiguriert werden ProEM-Aktionen können nicht erstellt werden Abgetrennte Eingänge für Licht anzeigen Erstellen von Optionen für VirtualComponents::Enum ist manchmal nicht möglich PlugS, PlugUK LED-Anzeigeeinstellungen können nicht konfiguriert werden Pro4PM, ProDualCoverPM Fehlende Anzeigeeinstellungen beheben Pro3EM Fehlende Zusatzkarte beheben ProEM, Pro3EM CT-Typen Fehlerbehandlung beheben Überarbeitung der Diagnoseschaltfläche für Debug-Log und Gerätedaten Geändert Verhalten beim Speichern der Einstellungsseite vereinheitlichen Unify Split-Schaltfläche Überarbeitung der Statusleiste Automatische Standortbestimmung über Schaltfläche auslösen Laden der Zeitzonenliste beim Öffnen der Einstellungsseite Überarbeitung der Konfigurationsseite für AP und Range Extender Überarbeitung der Skript-Editor-Seite PlusRGBW PM Farbwähler verbessern Bitte lesen Sie auch https://shelly-api-docs.shelly.cloud/gen2/changelog für weitere Details. 1 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Porup Posted July 31 Share Posted July 31 (edited) Hi. After update I have an issue. It regards my Shelly Pro Dim 2PM When adding a scene and making condition device based and choose "2nd" output on a Shelly Pro Dim 2PM, it returns the "1st" output every time. I have tried with several dimmers, an all does the same after update. Make Scene -> Condition -> Device based Device -> Pro Dimmer 2 (2. output) Device properties -> Output State (Turn On) Watch property as -> Trigger When saving, Shelly changed the 2nd out on the dimmer, to the 1st out. Everything worked last night, now I cant make new scenes with the pro dimmers. Video Added. What to do? Shelly Control – Google Chrome 2024-07-31 12-32-30.mp4 Edited July 31 by Porup adding video Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
QA members TheRegister Unique Posted July 31 QA members Share Posted July 31 (edited) Hi I am trying to update a few Gen3 devices from 1.3.2. The first step is of course to update to 1.3.3. However This update fails (stuck in "initiaizing update", 0% progress and apparently times out). In WebUI it does not even start. Needless to say that internet connection is OK, I can operate the devices from app/WebUI, etc. The devices that have already been on 1.4.0 beta update to 1.4.0 production without any problem Edited July 31 by TheRegister Unique 2 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
DavidS Posted July 31 Share Posted July 31 I have the same issue with updating to the mandatory 1.3.3. Logfile says 404, so the file to update to 1.3.3 seems to be missing on the update server. 1 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Shelly Olsche Posted July 31 Author Shelly Share Posted July 31 @TheRegister Unique & @DavidS: Thank you for the report. The problem is already known and will be investigated by the developers. Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Shelly Olsche Posted July 31 Author Shelly Share Posted July 31 1 hour ago, Porup said: After update I have an issue. It doesn't seem to be related to FW version 1.4.0, but it is still an issue that has already been reported to the developers. Thanks for the report Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
darius1706 Posted July 31 Share Posted July 31 Main problem is on ota update server, as I see in logs: 2024-07-31T22:52:20.508153+02:00 shellyplusplugs-d48afc7b30c8 183 2355.479 1 2|shelly_update.cpp:173 Checking for updates (1.0.7 20231031-152250/1.0.7-g5db02bd {"bl":263173,"ut":2355465556,"hf":138200,"hmf":117836,"fsf":139264}) 2024-07-31T22:52:20.509304+02:00 shellyplusplugs-d48afc7b30c8 184 2355.490 1 2|shelly_http_client.:302 0x3ffe08e4: HTTPS GET https://updates.shelly.cloud/update/PlusPlugS (CA shelly_cloud.pem) 2024-07-31T22:52:21.418077+02:00 shellyplusplugs-d48afc7b30c8 185 2356.400 1 2|shelly_http_client.:606 0x3ffe08e4: Finished; bytes 424, code 200, redir 0/3, auth 0, status OK 2024-07-31T22:52:26.692517+02:00 shellyplusplugs-d48afc7b30c8 186 2361.628 1 2|shos_rpc_inst.c:230 shelly.update via WS_in 192.168.88.114:57648 2024-07-31T22:52:26.692517+02:00 shellyplusplugs-d48afc7b30c8 187 2361.632 1 2|shelly_rpc_service.:300 Updating to stable 2024-07-31T22:52:26.692517+02:00 shellyplusplugs-d48afc7b30c8 188 2361.646 1 2|shelly_ota_source_ht:32 Update URL: https://fwcdn.shelly.cloud/gen2/PlusPlugS/b537c97799933584593641ea0f7ca7d3750b4020ce134d641953b92df5845220 (0x3ffdf5d8) 2024-07-31T22:52:26.692517+02:00 shellyplusplugs-d48afc7b30c8 189 2361.663 1 2|shelly_http_client.:302 0x3ffe0afc: HTTPS GET https://fwcdn.shelly.cloud/gen2/PlusPlugS/b537c97799933584593641ea0f7ca7d3750b4020ce134d641953b92df5845220 (CA shelly_cloud.pem) 2024-07-31T22:52:26.692517+02:00 shellyplusplugs-d48afc7b30c8 190 2361.678 1 2|shelly_ota.cpp:304 Starting update (0x3ffe08e8), timeout=600 commit_timeout=-1 ignore_same=0 2024-07-31T22:52:27.882277+02:00 shellyplusplugs-d48afc7b30c8 191 2362.850 1 1|shelly_ota_source_ht:73 0x3ffdf5d8 Error fetching update -110: Bad HTTP response: 404 2024-07-31T22:52:27.882425+02:00 shellyplusplugs-d48afc7b30c8 192 2362.858 1 0|shelly_ota.cpp:311 Aborting update: source error: -110: Bad HTTP response: 404 2024-07-31T22:52:27.882459+02:00 shellyplusplugs-d48afc7b30c8 193 2362.869 1 2|shelly_http_client.:606 0x3ffe0afc: Finished; bytes 529, code 404, redir 0/3, auth 0, status ABORTED: Bad HTTP response: 404 2024-07-31T22:52:27.886874+02:00 shellyplusplugs-d48afc7b30c8 194 2362.878 1 2|shelly_ota.cpp:234 OTA status error, 0 % Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Shelly Olsche Posted August 1 Author Shelly Share Posted August 1 We are currently investigating why some devices cannot be updated to the mandatory firmware 1.3.3. There will certainly be a fix for this soon. Thanks for your patience and thanks for the reports! ------------------------------------------------------------------------------------------------------ Es wird gerade untersucht, warum einige Geräte nicht auf die obligatorische Pflichtfirmware 1.3.3 aktualisiert werden können. Es wird sicherlich bald ein Fix dafür geben. Danke für die Geduld und danke für die Berichte! 2 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
MDN Posted August 1 Share Posted August 1 Seems to be working again! I just updated a few devices. --------------------------------------------------------------------------- Es scheint wieder zu funktionieren! Ich habe gerade ein paar Geräte auf den neusten Stand gebracht. 1 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Shelly Olsche Posted August 1 Author Shelly Share Posted August 1 5 minutes ago, MDN said: Seems to be working again! I just updated a few devices. Thanks for the feedback, @all there are even more positive confirmations? 1 1 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
QA members TheRegister Unique Posted August 1 QA members Share Posted August 1 I am happy to confirm that the FW update to 1.3.3 now works flawlessly. 2 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
DavidS Posted August 1 Share Posted August 1 Works for me now! Thanks! 1 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
darius1706 Posted August 1 Share Posted August 1 6 hours ago, Olsche said: We are currently investigating why some devices cannot be updated to the mandatory firmware 1.3.3. There will certainly be a fix for this soon. Thanks for your patience and thanks for the reports! ------------------------------------------------------------------------------------------------------ Es wird gerade untersucht, warum einige Geräte nicht auf die obligatorische Pflichtfirmware 1.3.3 aktualisiert werden können. Es wird sicherlich bald ein Fix dafür geben. Danke für die Geduld und danke für die Berichte! Now everything seems working 1 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
AndyRoc Posted August 1 Share Posted August 1 Hello, i am using the Shelly devices to best utilize pv generation using the Sma home manager 2.0. This update seems to break the integration. Kind regards Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Fabulous82 Posted August 1 Share Posted August 1 2 hours ago, AndyRoc said: Hello, i am using the Shelly devices to best utilize pv generation using the Sma home manager 2.0. This update seems to break the integration. Kind regards Hello, same thing here, I have 4 Shelly plus 1PM and after the Update to 1.4.0 it is no longer possible to control them using the SMA Home Manager 2.0. My Pro4PM still works fine with 1.4.0. Is it possible to go back to 1.3.3?? Unfortunately I can't find a way to download an older version. Best regards Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Tamer Salah Posted August 1 Share Posted August 1 hi all and thanks for following up , can I get the firmware for the device shelly plug S gen3 ? its currently on firmware 1.2.2 I guess , and there is no ota for the device since I connect it to internet . Best Regards Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Tamer Salah Posted August 1 Share Posted August 1 i already tried to reset it few times but still unable to fetch any firmware updates and cant add it to my account Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Shelly Olsche Posted August 2 Author Shelly Share Posted August 2 @Tamer Salah Can you please provide us with the debug log that is created when searching for new updates? Have you checked your firewall settings? Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
AndyRoc Posted August 2 Share Posted August 2 13 hours ago, Fabulous82 said: Hello, same thing here, I have 4 Shelly plus 1PM and after the Update to 1.4.0 it is no longer possible to control them using the SMA Home Manager 2.0. My Pro4PM still works fine with 1.4.0. Is it possible to go back to 1.3.3?? Unfortunately I can't find a way to download an older version. Best regards Yes, please. I also urgently want to downgrade. I know the firmware archive link generator but could you please let me know which Shelly type to choose for the plus 1 pm? 1 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Fabulous82 Posted August 2 Share Posted August 2 I just analysed the issue where the Shelly plus1PM doesn't work with the SMA Home Manager 2.0. It seems that they work correctly after reboot for a short while and then they won't react on HTTP Get requests. I took two device logs, one from a plus1PM and one from the still working Pro4PM. Best regards. diagnostics-shelly-plus1pm-debug-log (1).txt diagnostics-shelly-pro4pm-debug-log.txt Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
AndyRoc Posted August 2 Share Posted August 2 5 minutes ago, Fabulous82 said: I just analysed the issue where the Shelly plus1PM doesn't work with the SMA Home Manager 2.0. It seems that they work correctly after reboot for a short while and then they won't react on HTTP Get requests. I took two device logs, one from a plus1PM and one from the still working Pro4PM. Best regards. diagnostics-shelly-plus1pm-debug-log (1).txt 13 kB · 0 downloads diagnostics-shelly-pro4pm-debug-log.txt 117.43 kB · 0 downloads I can also confirm this. They work correctly for a short while after rebooting. Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
tvbshelly Posted August 2 Share Posted August 2 2 hours ago, AndyRoc said: I know the firmware archive link generator but could you please let me know which Shelly type to choose for the plus 1 pm? Firmwares in this link are for gen1 devices. For Gen2/3 devices you can only update firmware using Shelly Smart Control app or directly using device webUI. Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Speiche Posted August 2 Share Posted August 2 Das neue Update 1.4.0 führt zuR fehlerhaften Kommunikation mit dem SMA Home Manager 2.0. Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
AndyRoc Posted August 2 Share Posted August 2 Does this mean there is no way to downgrade? Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Shelly Olsche Posted August 2 Author Shelly Share Posted August 2 nope, no way 1 Quote Translate Revert translation? English (American) Finnish French German Italian Portuguese (European) Spanish Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.