Igi
-
Posts
103 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Gallery
Posts posted by Igi
-
-
Just now, Olsche said:
OK. Missed that. What is the difference to Gen2?
-
13 hours ago, Bieniu said:
H&T Gen3 with firmware 1.2.0 reports incorrect wakeup_period=7200 when the device is powered by USB.
@Bieniu Wait...is there a new H&T device? I only know the Gen2 H&T device. And this if battery operated with periodic wakeup every 2 hours.
-
I didn't receive a status notification via outbound websocket on Plus H&T with 1.1.0-beta2. But the status update to the cloud is working. An another device with 1.0.8 is also working. Can maybe somebody confirm? Maybe is it just a problem on my side.
-
1 hour ago, Axel Radtke said:
This problem with the RGBW2 was also reported several times in the forum after updating to the latest firmware 1.14.0. I was also able to rectify this on my RGBW2. A downgrade was no longer possible so easily.
Thank you for the information.
Unfortunately, it seems to have a different cause in my case. In the meantime I have also bought a new RGBW2 device but have the same problem. I have already tried a different power supply. So it can only be the LED strip. But my knowledge is too limited to investigate this.I have also just downgraded to v1.13.1. Unfortunately it also rebooted after 1 minute.
-
Short term test result for Plus 2PM
Running with ECO mode disabled for 24 hours: average internal device temperature 58 °C.
Running with ECO mode enabled for 24 hours: average internal device temperature 40 °C
Motor: Cherubini Mod. Blue P&P plus
Performed tests for both: ECO mode disabled & enabled:
- [✅ ] Calibration works on motors, that you know it worked before- [n/a ] Calibration works on motors, that you know that calibration on Shelly 2.5 worked, but new gen2 devices did not- [✅ ] Moving Up/down (close/open) works- [ ✅] Multiple up/downs (close/open) work (abusive testing here may not work perfectly, but in normal situation 2-3 ups/downs until a end stop is hit, is fine/should work)- [✅ ] Device’s uptime is normal (e.g. device had not restarted, how to check: http://deviceip/shelly.getstatus ← uptime: X….XXseconds)- [✅ ] All of the above work in Eco mode enabled too- [n/a ] Even in cases where calibration doesn’t work or an error is thrown, the device would be allowed to move (open/close, based on the current timer settings) completelyLong term test in progress now... -
Unfortunately, the same issue with another power supply as well.
-
16 minutes ago, mschaeffler said:
Can you give me a link to the V2.1.8 SW so that I can downgrade to confirm, that this SW works really better?
What is your version? You wrote you installed rc1. At this time the 2.2.1-rc3 was released. What exactly you installed?
Older FW versions for Gen1 devices are available via Shelly Firmware Archive Link Generator:
http://archive.shelly-tools.de/
Just choose the right device (SHMOS-01 or SHMOS-02) + the version and generate the URL.
-
Maybe the update notification for these special Gen1 battery devices requires the cloud connection? It's just a guess. I always use my devices with the cloud and have no experience using them without the cloud. But the Shelly developers should be able to answer that.
Does the update notification work for wired Gen1 devices?
-
1 minute ago, mschaeffler said:
But why is it not shown on the web ui?
Do you use the cloud?
Is the device able to call internet ressources? Or blocked by firewall - only local access?
-
Gen1 prod fw:
https://api.shelly.cloud/files/firmware
Motion2 latest v.2.2.0 fw (with connection issues):
http://shelly-api-eu.shelly.cloud/firmware/SHMOS-02_build.gbl
Manaual update as described above if the Motion2 has an internet access. Otherwize download the GBL file to your local web server and update from there.
-
1
-
-
As can be read in the Facebook support group, there are connection problems with TRV with the latest FW 2.2.0 in the Unifi AP environment.
https://www.facebook.com/groups/ShellyIoTCommunitySupport/permalink/6410505649048745/
A test FW with the possible fix has already been provided for the TRV.Can we please get the fix for Motion/Motion2 as well? I also have problems with Motion2. E.g. the execution of an action takes about 1 second longer on Motion2. After dowgrade to 2.1.8 everything works "normal" again.
BTW: who is the Shelly developer behind the Facebook name "Enriqe Iglesias"?
-
1
-
-
Hello,
I have here 2x 4 year old Gen1 RGBW2. Since 2 weeks one device always crashes and restarts after the output was turned on. Always after about 5-15 minutes and then again and again after 5-15 minutes until the output is turned off again. If no light is on, it does not happen. The firmware is the latest 0.14. But it also happened with the previous 0.13 version. But I think this has nothing to do with FW. My other device with the same settings works fine.
Can it also be time aging, like the problem with the capacitors in the Shelly 2.5?
I have enabled debug log. Maybe something can be identified?
BR
RGBW2_Gen1_crash_previous_log1.txt RGBW2_Gen1_crash_current_log.txt
-
2 minutes ago, mschaeffler said:
I do not uise the App, but everlything locally with NodeRed.
Is not App above. Is Cloud Web UI https://control.shelly.cloud.
The device checks the cloud for a new fw version. Usually, the update is also rolled out in phases and your devices are not yet authorized.
Or you use NodeRed as proxy for fw update if possible. We have implemented something like this in Openhab Binding.
-
Works as expected on my DW2 devices:
Clicked on "Update", opened the window --> update started.
-
Unfortunately, I have no idea.
My device is also a "dev-prototype". But I think that has nothing to do with it.
I use a static IP, I don't use MQTT but Coiot.
Otherwise I see you set the target temperature. But I think that the 15 degrees isn't reached and so the device is not active because it seems you are from the currently warmer area.
If you think it might be the firmware, you can install an old versionn (Shelly Firmware Archive Link Generator). However, nothing has been changed in the firmware recently. The current one is 1 year old.
-
Not in general.
Bad for battery consumption are:
- weak Wifi signal
- DHCP IP instead of static IP
- permanent ping to the device (device can't switch to sleep mode)
- permanently open Web UI (device can't switch to sleep mode)How are the settings?
http://<device_ip>/settingsThis is my battery usage:
-
My all Plug-S devices (connected to the cloud + added to the app) doesn't report this version - just still 1.13.0 and this is also the version provided by the prod FW repo:
https://api.shelly.cloud/files/firmware
FW 1.13.2 is listed in the repo with test versions:
https://repo.shelly.cloud/files/firmware?force_test_fw=1&list=1
-
My Plus Plug S from the QA Pack shows an internal temperature of 76 °C when idle. The Plus Plug IT in the socket right next to it shows 26 °C.
Plus Plug S
{"ble":{},"cloud":{"connected":true},"mqtt":{"connected":false},"plugs_ui":{},"script:1":{"id":1,"running":true,"mem_used":6874,"mem_peak":7644,"mem_free":14126},"switch:0":{"id":0, "source":"WS_in", "output":false, "apower":0.0, "voltage":0.0, "current":0.000, "aenergy":{"total":0.000,"by_minute":[0.000,0.000,0.000],"minute_ts":1690284256},"temperature":{"tC":75.8, "tF":168.4}},"sys":{"mac":"441793D0ADB8","restart_required":false,"time":"13:24","unixtime":1690284257,"uptime":1221503,"ram_size":258736,"ram_free":121464,"fs_size":458752,"fs_free":73728,"cfg_rev":44,"kvs_rev":3,"schedule_rev":0,"webhook_rev":0,"available_updates":{"beta":{"version":"1.0.0-beta6"},"stable":{"version":"0.14.4"}}},"wifi":{"sta_ip":"192.168.222.56","status":"got ip","ssid":"IGI@Private","rssi":-77},"ws":{"connected":false}}Plus Plug IT:{"ble":{},"cloud":{"connected":true},"mqtt":{"connected":false},"script:1":{"id":1,"running":true,"mem_used":6874,"mem_peak":7560,"mem_free":14126},"switch:0":{"id":0, "source":"init", "output":false, "apower":0.0, "voltage":228.8, "current":0.000, "aenergy":{"total":0.000,"by_minute":[0.000,0.000,0.000],"minute_ts":1690284292},"temperature":{"tC":26.6, "tF":80.0}},"sys":{"mac":"441793D0B070","restart_required":false,"time":"13:24","unixtime":1690284293,"uptime":613128,"ram_size":258992,"ram_free":122892,"fs_size":458752,"fs_free":69632,"cfg_rev":36,"kvs_rev":1,"schedule_rev":0,"webhook_rev":0,"available_updates":{"beta":{"version":"1.0.0-beta6"},"stable":{"version":"0.14.1"}}},"wifi":{"sta_ip":"192.168.222.62","status":"got ip","ssid":"IGI@Private","rssi":-55},"ws":{"connected":false}}Do I have a hardware problem? Or is the temperature of your Plus Plug S also similarly high?
-
On 5/16/2023 at 2:04 PM, Aleksandar Krastev said:
The following features are most affected by the recent changes:
OTA update, WebHooks, Scripting, Schedules, Timers, embedded web, mDNS.mDNS / Openhab discovery still OK, inbound websocket OK, BLE scanner script is working again when BT gateway is enabled 👍
-
2
-
-
What has changed for the Plus Plug S device in version 0.14.4? There is nothing listed in the changelog https://shelly-api-docs.shelly.cloud/gen2/changelog/
After updating from 0.14.1 to 0.14.4, my BLE scanner script is no longer working when BLE gateway option is enabled (as discussed in the Alpha3 thread).
-
6 minutes ago, Lyubomir Petrov said:
I don't have OpenHAB running here, but last time I got some logs from a user, there was:
- Active web socket connection
- HTTP requests
I think that was me 🙂 At the beginning of March I sent you the diag log in this thread. Then I had disabled the device in openhab 1 month and did not notice any reboots. I re-enabled the device in Openhab and am watching the behavior.
So I think I do not need an replacement @Todor Tsvetkov but may be @Richard needs.
-
1
-
-
2 minutes ago, Lyubomir Petrov said:
Some times, yes. It really depends on the right moment and the right amount of incoming requests. We'd seen complex requests coming from systems doing 10 requests/second, which is a bit too much for an ESP32.
But I in my case - is it just 1 websocket from Openhab to the device. And the NotifyStatus data packet is trigerred by device. Additionally there is 1 HTTP call per minute from Openhab to the device. But I will also take a tcpdump to see if there happens more during the connection.
-
@Lyubomir Petrov Can a continuous status request cause a reboot? Since I disabled my devices in Openhab and there is no active websocket connection I don't have any reboots.
-
@Olsche ok, got it. I thought I need also updated the old App.
The new Control App has the version 1.13.1 on the App store. So I'm fine and ready for BLU.
Thx
Fast battery discharge with SHMOS-01 and FW 2.2.2
in Current firmware
Posted · Edited by Igi
Since FW version 2.2.2 (20231122-131719) the battery of the SHMOS-01 discharges much faster than with the previous FW version.
The graph shows the progress of the battery discharge from 100% to 20% over 10 months with the old FW. With the new FW 2.2.2, the battery level dropped from 100% to 20% in 2 months.
The motion sensor is deactivated and is in the cabinet the whole time.
I cannot see this behavior on the SHMOS-02.
BTW: There is no changelog for this version on the Shelly API Docs website.