Beiträge von joseLRD

Hi,

have you looked at the Teleperiod MQTT message? it reports the Switch state(s). It's topic ends with .../SENSOR.

If you want to ask for the state then try the command STATUS 8

Hope this still helps.

Today I completed migrating 9 Shelly1 switches to Tasmota using the mgos-to-tasmota tool mentioned earlier. All updates when smooth, no switches bricked.

Features implemented:

• automatic overnight reboot (own macro) helps keeping Shelly online and reachable
• Switchmode 2 (inverted follow) saves rotating physical wall switch on switches mounted upside down (user's complain)
• Webserver 1 (user mode) disables admin commands in the Web GUI (security), stopping tasmota-to-mgos hacks
• temperature controlled fan (using analog thermostat)
• Motion controlled lights (using STEINEL IS 180-2 bwm)

Next step is to migrate the Shelly 2.5 switches

Hi,

in a separate thread in this forum I learned of mgos-to-tasmota  and it's ability to migrate Shelly's stock firmware through OTA.

It's a great tool, I'm very happy and thankful it exists. It is allowing me to migrate from Shelly's stock firmware to the much more powerful Tasmota without having to remove the switches from the wall

However, what surprised me (and scared at the same time) is the lack of authentication / credentials for doing this. Anybody in the SAME network with the right knowledge (guest, friend or hacker) could override the device settings and/or firmware of ALL Shelly switches anytime!

If this is true I think it is a huge security exposure in Shelly's firmware and users should be made aware of it!

My expectation is that at least a password is required in order to override the firmware.

Could anybody please confirm or correct this observation?

Thanks!

Yes, that's what I mean. I saw different prices and assumed the units were different as well.

That's good news, thanks!

Hi,

Does anybody know what are the differences between the Shelly 2.5, 2.5B and 2.5B5 models?

Thx!!

Zitat von SebMai

https://github.com/yaourdt/mgos-to-tasmota

Followed the instructions on a Shelly 1 and succeeded with my first OTA migration

It is as simple as entering one URL in your browser. One minute later I had Tasmota v9.5.0 installed and ready to be configured Be carefull and make sure the IP address you specify corresponds to your target Shelly as there is no warning nor password check whatsoever you hit enter and the firmware is overwritten.

As next step I will proceed migrating first all my Shelly 1, then the 2,5 and at the end the Dimmer 2. I'll post my experiences here. If anybody else already went this path please share.

Thanks!

hi @andutgv,

I have one of the relays of a Sonoff Touch 3 connected to a Shelly Dimmer 2, however I only use it to turn the lights on/off. Dimming is done through openhab. I don't have a Shelly-Bypass (do you really need it?).

I have thougth on implementing dimming using the other relays (e.g. 33%, 66%) but have not tried it yet. For that I would NOT do any additional wiring, just configure openhab to send the corresponding command to the Shelly Dimmer 2 everytime a "button" is touched.

Perhaps this idea helps you.

Zitat von SebMai

you can do both ota.

Tasmota and shelly.

That's good news for me and will save a lot of work. Thank you!!!

Zitat

Hello,

I recently purchased a Shelly Dimmer 2 thinking it would be supported by Tasmota. It turns out that some code is in testing but not fully baked. Can someone send me a URL the original factory firmware for the Shelly Dimmer 2 so that I can reflash?

Many thanks,

Mark

Hi @mtroyer,

did you ever tried a later Tasmota version? I'm considering Tasmota and am looking for real life experience.

Hi gladiator,

perhaps a bit out of topic here, but I'm looking for experience with Tasmota on Shelly switches.
- did you get your problem solved?
- would you recommend changing to Tasmota?

thanks!

Zitat von pepsinio

... I hope that they soon make Tasmota available for dimmer 2 and get more control over such settings. I doubt Shelly will release firmware update to make this less of an issue.

Hi pepsinio, did you get this issue solved? Tasmota support for DM2 has been available for while now.

Zitat von SebMai

So I asked why you don't do it OTA.

Is it possible to update the original firmware to Tasmota Over-The-Air (OTA)?
that would simplify things for me.

Unfortunately according to the link below, it is NOT POSSIBLE to update to Tasmota using OTA. I would still need to get the switches out of the wall ... but if the feedback to my question is positive then i will do it!!

Has anyone ever tried flashing a shelly OTA? · Issue #5953 · arendst/Tasmota (github.com)

Zitat von SebMai

Sorry I can't share any experience.

But one question? Why don't you flash them OTA?

If by "OTA" you mean the Tasmota firmware, that is exactly what I'm planning to do with the next Shelly I buy. Like I wrote, I already have two Shelly 1 switches with Tasmota and they are working ok.

But before flashing all the other switches I have installed in the last 12 months (over 20 SHSW-1, SHSW-25 and SH-DM2) it would be better, faster, and perhaps of general interest to see what more experienced users think. That's whay I'm asking the forum.

Thanks anyway!

Hi everybody,

I love Shelly switches and keep adding more and more , at the same time I'm not so happy with its firmware . This forum is full of issues around wifi connectivity, ota updates, ghost switching, need for cloud connectivity and the like. For some reason Allterco does not seem able to solve these issues in a timely and reliable manner .

On the other hand I know Tasmota firmware from my Sonoff switches, zigbee bridges and others. I prefer Shelly switches over Sonoff, but the firmware experience with Tasmota is much much better. It's open source, no cloud need, feature rich, very well documented and it has an incredible knowledgable and helpful community .

I tried Tasmota on a couple of Shelly-1 with good results, but have not tried it with Shelly 2,5 or Shelly Dimmers. Before going switch by switch (take them out of the wall, flash, reinstall) I thought I would ask here in the forum .

Is there anybody willing to share their experience? There are reports of Tasmota running in multiple types of Shelly devices, but they are mostly experimental installations. I'm looking for real life feedback

That would help me (and perhaps others) a lot. Thanks!

Zitat

Same question. I have 6 shutters and for 3 of the them I have already installed 3 shelly 2.5 devices.

There is no "shortcircuit" risk, however I would try to avoid these configurations since the wall switch setting will be confusing for the "user". It is better and rather cheap to replace it with the appropiate one.

Hi,

Zitat von freank

Have you already gathered experience with one of the mentioned Products? What does your setup currently look like?

After looking around in this and other forums I decided against the Shelly RGBW2 and choosed the Paulmann MaxLED Zigbee controller 500.46 in combination with 17,5m Tunable White Strips, Artikel-Nr.: 706.30. The main reason for this decision was the lack of successfull installations and my need for a stable and reliable solution.

I already had a Zigbee gateway in place, so that Openhab could fully control the LED strips. In addition, the 500.46 controller acts as a Zigbee repeater, improving the link quality of battery operated Zigbee sensors.

Perhaps not the info you were looking for, still I hope it helps.

The API documentation for the Dimmer 2 states:

In my case, I'm getting sporadic ERROR 1 problems on two of my Dimmer2 shellies.

When this error occurs (1 every 10 tries), it's usually a few seconds after turning the wall switch ON.

At this moment the lamp goes OFF and the web GUI shows "ERROR 1".

Using the HTTP REST API I (<ip_address>/status) immediately after the error I also see:

"overtemperature":false,"loaderror":1,"overpower":false

Pressing the wall switch once more resets the error and the light goes ON.

What does "loaderror", "overload" and "overpower" exactly mean ?

What can I do to fix this problem?

Thanks!

Hallo,

die neueste Shelly 2.5 Firmware-Version hat die "SOFT REBOOT WHEN WIFI CONNECTION IS LOST" Option eingeführt. Dies ist sicherlich eine Verbesserung gegenüber dem vorherigen Zustand, aber immer noch nicht so flexibel, wie einen selbstausgelösten reboot z.B. um 4 Uhr morgens.

Eine Home Assistant Task funktioniert nur so lange die Shelly erreichbar bleibt, leider.

MfG

Hello,

the switches should be connected to the Shelly 2.5 and not directly to the blind's motor (see wiring diagrams). There is no risk if done properly.

Zitat

I have shelly's everywhere in the house, ...

it's usually just a matter of time, by a growing number of sensors, actuators and complexity, that a higher level system becomes the best option (eg. IOBroker, openHab, Home Assistant, ...). In the meantime, for a Shelly 1 I would evaluate Tasmota firmware. It has a powerful macro "language" and can send http commands.