I have this issue as well. Even on multiple shelly devices.
Did any of you solve this?
Tried various fw versions.
Same behaviour.
Using neutral line.
Cloud off.
Dimming 6x 5w ikea bulbs.
Funny thing is the device have been running fine for a few months.
Then all of a sudden I get this issue.
Thinking about getting rid of all my shellies and instead buy something else that is more stable.
Or just go with zigbee bulbs.
ahh that makes sense.. Didnt think of that.
thanks for the reply !!
hi..
I have installed yet another dimmer 2 in my home.
flashed it to 1.9.4.
its connected to the cloud fine.
local web ui gives me:
Current version: 20210115-103951/v1.9.4@e2732e05
You have latest version on your device!
my other dimmer 2 devices were last moth all updated to latest beta FW which at the time of writing is: 1.10.0-rc1
i remember it was an option within the local WEB ui.
but this new dimmer will not give me the option for BETA firmwares.
Going crazy here...
Hi..
Currently running around 12 x shelly dimmer 2 devices in my house.
Yesterday I installed yet another device which are powering 4 ikea dimmable bulbs.
I flashed to the latest 1.9.4 FW
To my surprise the shelly device suddenly completely locks up.
I cant turn light on/off using the physical wall switch. Nor can I adjust brightness levels.
The web interface does not respond.
The small RED led indication light on the unit itself is off.
(Normally its always on - atleast this is the case when looking at my other working devices.)
The device temperature feels normal when touching the chassis. Its not dead cold.
I tried hard resetting the device with AC line still connected. Pushing the reset button. Nothing happens.
The only thing that works is if I disconnect the AC line. eg. by turning the breaker off.
Then turning the breaker on again.
Essentially power cycling the unit.
Sometimes this makes the unit work again.. Sometimes not.
Often I have to repeat this process a few times.
Once it works.. it will work for about an hour or so. Then it ceases completely.
What can I do to fix this ?
I have a few other shellies that are waiting to be installed. I could try and swap this one out.
I could try and revert to earlier FW version.
Infact I remember I had this issue before on one of my other shelly dimmer 2 installations.
It was exactly the same deal. No red LED indication lights. No access to it. Couldn't turn on lights with physical button and so on.
I remember I removed all the wires and placed it on my test table where I connected AC + Neutral only. No consumer (lights), no switch.
The LED indication began emitting red light. It connected to AP and I was able to confirm it was working.
Back to the old installation again. Wired exactly the same. Haven't had any issues since then.
Back to the current problematic device. This one seems a lot more stubborn.
To me it sounds like a bad unit.
Anyone out there experienced anything like this ?
setup:
NEUTRAL line connected.
using "one button mode" + calibrated trailing edge dimming mode.
I have several shelly dimmer 2 devices in my household.
More recently one of those devices started to exhibit a problem.
When I turn on the problematic lights they will turn off again within 10 sec to several minutes.
It doesn't seem to matter at what brightness level I am using.
The LEDs (3 pieces) have a total wattage of around max 20w
When the error occurs the webpage of the culprit device reports: "ERROR 1" and the device has the "turned off" icon/symbol.
"ERROR 1" I can see relates to potential problems with zero crossing as well as general noise on the AC line.
* Tried changing the LED bulbs with no effect as this was easy to do.
* Tried running 1 LED alone, removing the other 2.
* Tried calibrating both leading and trailing edge dimmer modes. No effect.
* Tried to factory reset the device. Didn't help.
As the device had been running stable (at some point) I decided to try some different firmware versions.
The one that seems stable (so far) is F/W v1.8.5.!!
I also tried the following here, but all with bad results.
v1.9.0..ERROR1
v1.9.3-rc3 ..ERROR1
v1.9.3-rc4 ..ERROR1
So something in the firmware between 1.8.5 and 1.9.0 apparently seems to have made things worse for me.
I should also mention that I have 3 other shelly dimmer 2 devices which are all running F/W v1.9.3-rc3 and they do not exhibit problems like this at all.
here's the dump of the device at the point of failure.
{ "wifi_sta":{ "connected":true, "ssid":"xxx", "ip":"192.168.1.181", "rssi":-61 }, "cloud":{ "enabled":false, "connected":false }, "mqtt":{ "connected":false }, "time":"16:41", "unixtime":1608136912, "serial":621, "has_update":true, "mac":"40F5200165A5", "cfg_changed_cnt":18, "actions_stats":{ "skipped":0 }, "lights"[Blockierte Grafik: https://static.xx.fbcdn.net/images/emoji.php/v9/tcb/1/16/1f641.png] { "ison":false, "source":"http", "has_timer":false, "timer_started":0, "timer_duration":0, "timer_remaining":0, "mode":"white", "brightness":67 } ], "meters"[Blockierte Grafik: https://static.xx.fbcdn.net/images/emoji.php/v9/tcb/1/16/1f641.png] { "power":0.00, "overpower":0.00, "is_valid":true, "timestamp":1608136912, "counters"[Blockierte Grafik: https://static.xx.fbcdn.net/images/emoji.php/v9/tcb/1/16/1f641.png] 0.000, 0.000, 0.000 ], "total":980 } ], "inputs"[Blockierte Grafik: https://static.xx.fbcdn.net/images/emoji.php/v9/tcb/1/16/1f641.png] { "input":0, "event":"S", "event_cnt"[Blockierte Grafik: https://static.xx.fbcdn.net/images/emoji.php/v9/eb4/1/16/FACE_WITH_COLON_THREE.png] }, { "input":0, "event":"", "event_cnt":0 } ], "tmp":{ "tC":50.67, "tF":123.20, "is_valid":true }, "calibrated":true, "calib_progress":100, "calib_status":0, "wire_mode":1, "overtemperature":false, "loaderror":1, "overpower":false, "debug":0, "update":{ "status":"pending", "has_update":true, "new_version":"20201124-092706/v1.9.0@57ac4ad8", "old_version":"20201202-141422/v1.9.3-rc3@50c6ab57", "beta_version":"20201202-141422/v1.9.3-rc3@50c6ab57" }, "ram_total":48368, "ram_free":35556, "fs_size":233681, "fs_free":113954, "uptime":19377
}
hi.
Here's a small feature request that I hope that others could find useful as well.
----------------------------
using the shelly 2 dimmer along with
FW Current version: 20201124-092706/v1.9.0@57ac4ad8
using one button mode
----------------------------
When I double tap my wall switch the lights turn on with 100% brightness.
When I double tap it once more, the lights are turned off.
What I would want to happen is this:
double tap #1, go to full brightness
double tap #2, go to minimum brightness
repeat the cycle.
I got this idea from my old dimmer that I had before I bought the shelly device.
Its a convenient way of going to lowest or highest brightness mode.
I will create a feature request for this 
using the shelly 2 dimmer
FW Current version: 20201124-092706/v1.9.0@57ac4ad8
using one button mode
When I single press my wall switch it lights up my LEDs fine full brightness (100%).
100% because, this was the state the dimmer was in before the user switched off the lights.
I now press and hold the switch down. It does not DIMM down.
Maybe the brightness direction is intially interpreted as "UP" ?
It cant go any further up, as we are at 100% already initially.
Now, if I release the switch and then once again press and hold the switch down, then it starts correctly do dim down the LEDs as the dimming direction has been changed from UP to DOWN.
Expected behaviour:
when I turn on the lights with a normal "press and release" activity on the switch the dimming direction should adjust itself to what
the current dimming setting is.
As this could ideally save the user from having to press the switch multiple times in order to dimm down.
If its already at 100%, then dimming direction should initially be "DOWN/LOW"
One could argue that intial dimming direction should be down if the initial dimming level is in the range of lets say 80-100%.
Maybe introduce a user defineable percentage value?
If its in the 1-79%, then dimming direction should initially be "UP".
I will submit this as a feature request.
