I’m hoping to get some Shellys as well. I believe they released an update to their native firmware that supports MQTT natively so one doesn’t have to flash to Tasmota unless you want to. Support is only beta but the fact that they are adding this to their firmware shows this is a company that understands what we want instead of fighting against us.
Another option I could come up with is to use any sonoff with tasmota and then amazon dash buttons to control the sonoff. Is there any other option apart from the amazon dash buttons that you could think of?
Thanks for the brain-picking 
I have also found this product (I am sorry it is in Italian) which allows to monitor the consumption of energy. This could be an input for the server to understand whether the light is on or off, and it could be added as a third or fourth deviator in a normal 2 or 3 deviators setup. What do you think?
If you consider this a solution, I would pick a remote device that does not rely on the working Wi-Fi.
A sonoff RF for example can be switched by a RF remote, and this would work even if the WiFi is down.
Received two Shelly 1 yesterday and did firmware update straight away. Native MQTT support, even disabling Shelly cloud access. Hope to get them in place next week 
2 Likes
Could you please explain a bit more what you mean with multiple deviators controling your lamps.
Wiring diagramm e.g. ?
I have several lamps in my corridors which are controlled by 2 switsches each. In that case my Shelly device will be placed at the switch which has direct connection to the lamp. Switching in Shelly can be configured to be an edge switch, something like a toggle. So lamp is controllable by openHAB an still the two physical switches.
Guys, thank you so much for the support.
@hmerk: here is a wiring diagram1 of the current state for reference: 
I was thinking to use another relay placed in parallel as if it were a third deviator like the ones in the diagram so it would simply work like this diagram2 [sorry, I am allowed to post only one picture, I will link this one]: http://www.elektro.it/impianto_appartamento/impianto_appartamento_img/impianti_civili_15.gif
This relay would be controlled by a simple sonoff POW with a current sensor.
By doing this I would achieve all the objectives:
- No new cabling in the wall or mess up the current wiring diagram;
- Everything would work offline witout wifi as well, I could simply use one of the other two physical deviators;
- The server would know when the light is on even if the light were to be turned on by a physical deviator thanks to the power consumption measured by the sonoff POW (the product I linked before)
Do you think it makes sense? Do you think that with a Shelly I could achieve the same result (with less effort!)?
Thank you again!
Just a quick answer from my phone. It looks basically like my wiring, so no need for additional effort, just one shelly needed. I will have a closer look and try to add the shelly wiring to your diagramm.
One further question, do you have a hot wire (L) near the nearest switch to the lamps? Cause this is mandatory for the shelly to work. In my case, I can place them behind a switch combination where „single“ switches are in place es well. So I have hot and switched wires (L) in my wall boxes.
I am not sure yet (house is WIP), I guess not in every box. However, they put large corrugated pipes (if that’s what they are called in English) so it sould be fine to fit another wire in there!
Ok now, I have my first Shelly-1 in place, controlled via openHAB and two physical switches.
Wiring:
In Shelly settings (original firmware) configure your switches to EDGE switch (last option),
Works as expected and state in openHAB reflects real lamp state, no matter if one of the switches was used or openHAB.
2 Likes
Amazing! I just ordered a pack of 4, can’t wait to check them out.
Thanks a lot for helping and for the detailed wiring diagram.
Glad if I could help.
Hi,
Would you be willing to share Shelly 1 items config as I’m having issues getting mine to work, I’ve configured a local mqtt broker and the basic testing works but I cant get the switch to be controlled by openhab.
This is my test items file
Switch MQTT_Test "Shelly 1" { mqtt="<[mqttbr1:shellies/shelly1-059665/relay/0:state:default], >[mqttbr1:shellies/shelly1-059665/relay/0/command:command:ON:1], >[mqttbr1:shellies/shelly1-059665/relay/0/command:command:OFF:0]" }
If I turn the siwtch On/Off via the switches app/web service I can see the following errors in the openhab.log file but not sure how to fix
2018-10-17 19:27:50.663 [WARN ] [b.core.events.EventPublisherDelegate] - given new state is NULL, couldn't post update for 'MQTT_Test'
2018-10-17 19:28:08.485 [WARN ] [b.core.events.EventPublisherDelegate] - given new state is NULL, couldn't post update for 'MQTT_Test'
Should add I’m very new to MQTT so this is possibly just a noob issue.
Cheers
Kevin
Not sure what the shellie msg looks like but, your missing the } on the end of your item
if you’re willing to go the z-wave route, i have a bunch of aeotec switches. they work with or without the HA software up and running and work in conjunction with whatever switches you already have in place
As @H102 wrote, you are missing the } at the end of the line.
You even should use map transformation as the returned state 0/1 can not be interpreted by the switch item.
Hi,
The missing “}” was just a pasting error but thanks for pointing it out, I will have a look and see how I use a transformation map.
@waspie thanks I already have some of the z-wave switches however a £40-50 each its expensive so thought I’d try the Shelly/MQTT route as they are a lot cheaper.
Cheers
@hmerk Thanks the map transformations did the trick and the first Shelly1 is behaving as it should.
I was close at least
Regards
Kevin