search

arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
22.24k stars 4.81k forks source link

Support for Sonoff D1 Dimmer #7598

Closed klotzma closed 4 years ago

klotzma commented 4 years ago

Have you looked for this feature in other issues and in the docs?

Yes

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.

I cant't find a Template for this Device.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Sonoff has released a new dimmer, the Sonoff D1 dimmer. Is Tasmota compatible with this dimmer, if not, is it possible to add it?

Thanks Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered. Only Support. Additional context
Add any other context or screenshots about the feature request here. 1579955221551916829968913932071 1579955250365492535689669968940

(Please, remember to close the issue when the problem has been addressed)

hvbommel commented 4 years ago

Standard procedure. Configure a dimmer in domoticz. Lookup its device idx. Put that idx value in the domoticz idx setting in your dimmer. You need a broker in place and enble mqtt in Domoticz also. If you have other MQTT Sonoff's working this is simular.

jkimmel commented 4 years ago

Had module configured as Sonoff D1 (0) instead of Sonoff D1 (74) Now I can turn the dimmer on and off, but the dimming works only limited. When I set to the highest level in Domoticz, the console says 11:26:32 MQT: stat/Sonoff_Dimmer/RESULT = {"POWER": "ON", "Dimmer":15} instead of {"POWER": "ON", "Dimmer": 100}

hvbommel commented 4 years ago

You are allmost there, I have seen the same you are mentioning. Set it up like this will it. dimmer

jkimmel commented 4 years ago

@hvbommel Not quite. Whatever value I choose (dimmer%20xx) console reads 11:26:32 MQT: stat/Sonoff_Dimmer/RESULT = {"POWER": "ON", "Dimmer":15} Shutting off is working

jkimmel commented 4 years ago

I just flashed my second D1 successfully, but it does not show up in my network. Maybe something wrong with the credentials. Any chance to reset it?

ghost commented 4 years ago

Reflash it without creds and enter the creds when it boots in AP mode

hvbommel commented 4 years ago

What version of tasmota are you using? (I use 8.2.0)

jkimmel commented 4 years ago

What version of tasmota are you using? (I use 8.2.0)

Me too.

jkimmel commented 4 years ago

@hvbommel Not quite. Whatever value I choose (dimmer%20xx) console reads 11:26:32 MQT: stat/Sonoff_Dimmer/RESULT = {"POWER": "ON", "Dimmer":15} Shutting off is working

In the meantime I resetted the device and configured from scratch. I also configured a second device in the same manner. The first one still shows the above reading the second ones readings are ok. Just to mention: Access to the first by webui is very laggy Sonoff Dimmer Tasmota - Tabellenblatt1 (1).pdf

jkimmel commented 4 years ago

@hvbommel Not quite. Whatever value I choose (dimmer%20xx) console reads 11:26:32 MQT: stat/Sonoff_Dimmer/RESULT = {"POWER": "ON", "Dimmer":15} Shutting off is working

In the meantime I resetted the device and configured from scratch. I also configured a second device in the same manner. The first one still shows the above reading the second ones readings are ok. Just to mention: Access to the first by webui is very laggy Sonoff Dimmer Tasmota - Tabellenblatt1 (1).pdf

klotzma commented 4 years ago

I have successfully flashed my Sonoff dimmer, but now the lamp flickers when I dim. What can that be?

sandeep-ma commented 4 years ago

The eWeLink app and Sonoff firmware have a feature that limits the travel of the dimmer to 0% and restricts it to an adjustable minimum, treating it as the new 0%. It kind of solves the issue. You could implement the same in your code.

The D1 implements a trailing edge approach for wave trimming, so the issue is less than in other older leading edge dimmer designs. Furthermore, better quality newer dimmable LED lamps are unlikely to have an issue.

oederp1 commented 4 years ago

Hi!!! I have successfully flashed my Sonoff Dimmer, but when i set the Dimmer to >= 92% the light goes out. How can I configure the tasmota so that the maximum value of Dimmer is 92%? Thanks!!

oederp1 commented 4 years ago

I just have the problem that the dimmer turns on / off / dims by itself without commands from HASS. When I check the log of Tasmota on the D1 I do see that a command has been set. Does anyone know more about this?

hvbommel commented 4 years ago

I am seeing the same, also in the logfile. It could be that unused GPIO inputs cause this, it is just a guess. So maybe firmware does not properly init unused input pins. But I could be wrong. Myself or someone else needs to investigate. Note, I have 2 of these dimmers, only one is doing it.

kumy commented 4 years ago

@oederp1 @hvbommel check in this thread around March for the keyword "ghost switching", some of us fixed it by unsoldering some resistors.

https://github.com/arendst/Tasmota/issues/7598#issuecomment-604329062

oederp1 commented 4 years ago

Hi Kumy thanks for your help. I don't use RF signal on my D1 Dimmer. I'm using wifi + tasmota + home assistant only. To solve the ghost switching problem , What is the simplest way? I'm terrible with welding, I have parkinson's and it's very difficult not to shake my hands. Thanks for all.

FourFoot commented 4 years ago

If you have no intention to use RF, you can just crush the resistors with a pair of snips to remove them from the board - that's what I did with a couple of mine as I was too lazy to get out the soldering iron. That was well over a month ago now, haven't had any ghost issues since.

Steun76 commented 4 years ago

This sounds like a perfect solution!!

But what's the RF resitor on the board?

kugelkopf123 commented 4 years ago

@Steun76 Just read back this Thread. There are some workarounds with pictures.

Steun76 commented 4 years ago

can't find is, it's all about flashing... as far is I can see

kugelkopf123 commented 4 years ago

can't find is, it's all about flashing... as far is I can see

from there:Link till 27. March

fapoo commented 4 years ago

Hey guys, I have the same issue with ghost switching on the D1 with Tasmota. However, I don't know, if this might be solved by a firmware update, which means waiting for it, or if I have to solder it. I would prefer an update, but is the problem even addressed? I'm not sure about that. Thank you.

digitlength commented 4 years ago

Maybe I'm missing something obvious: I can't find any Sonoff D1 option under Module type in Configure Module.

I have tried with the 8.3.1 -sensors.bin release from https://github.com/arendst/Tasmota/releases, and the -sensors.bin release from http://thehackbox.org/tasmota/.

What am I missing?

EDIT: Scrap that - I can see the option now if I flash with a normal tasmota.bin

n1tehawk commented 4 years ago

The user Pascal reported an interesting find on Discord: https://discord.com/channels/479389167382691863/490244847568158751/744194118816628806

Initially also being plagued by the D1 "ghost switching" problem, he discovered he still had a Sonoff remote lying around. After pairing the two, the switching problem apparently was gone...

Regards, NiteHawk

cpankonien commented 4 years ago

I just received my d1 today, and after remembering to set gpio0 to ground during boot i was off and running. Firmware (v8.4.0) flashed with no issues using tasmotizer, and I can now control it using Home Assistant and by voice using Google Home. I can set the lights up to 90%, anything higher and they go out, but I can set them as low as 1% and that seems to work fine. They still seem a bit bright for 1%, but it's my first dimmer so my expectations may be off (they are also the cheapest dimmable led bulbs I could find at Lowe's). Thanks to all who participate and impart knowledge!

artxxx commented 4 years ago

Maybe someone can write instruction how to flash D1?) At least please help me... which pins i should cross to boot into flash mode? Thx.

cpankonien commented 4 years ago

Have you flashed any sonoff devices before? If so, you just have to connect gpio0 to ground, and holding it like that, plug the usb cable in (power it up). That puts it into flash mode and you should be able to flash it. There is a picture above that shows where to connect to, I'll put the same pic here, thanks to @nemerdaud for providing it. So connect that gpio0 pad with a ground point (I used the same one used to flash it) during boot. If you've never flashed a sonoff device before, I can help you with that outside of this conversation, just let me know. image

artxxx commented 4 years ago

Have you flashed any sonoff devices before? If so, you just have to connect gpio0 to ground, and holding it like that, plug the usb cable in (power it up). That puts it into flash mode and you should be able to flash it. There is a picture above that shows where to connect to, I'll put the same pic here, thanks to @nemerdaud for providing it. So connect that gpio0 pad with a ground point (I used the same one used to flash it) during boot. If you've never flashed a sonoff device before, I can help you with that outside of this conversation, just let me know.

I flashed a lot of devices, but I didn't see this picture, so I can't find GPO0. Thanks to you, I flashed D1.

digitlength commented 4 years ago

The user Pascal reported an interesting find on Discord: https://discord.com/channels/479389167382691863/490244847568158751/744194118816628806

Initially also being plagued by the D1 "ghost switching" problem, he discovered he still had a Sonoff remote lying around. After pairing the two, the switching problem apparently was gone...

Regards, NiteHawk

I've just paired my remote following the instructions here: https://sonoff.tech/product-tutorials/how-to-pair-and-clear-433-mhz-remote-controller-in-sonoff-devices

I'll report back whether the ghost-switching disappears. EDIT: It does not. Ghost switching is still happening.

For info, here is what my remote buttons do when short-pressed (as reported by Tasmota, and verified visually). This is slightly different to the manual that came with the remote:

image

premiero commented 4 years ago

The ghost dimming is not a Tasmota issue. I have original non-Tasmota flashed D1 and the same happens to me. So frustrating.

burt777 commented 4 years ago

I just managed to get Tasmota on my new Sonoff D1 Dimmer, using the template, and it works like a charm... So much fun, i'm about to get greedy...! Next question:

Can we use the RF capabilities with Tasmota? I would love to receive RF messages and "translate" them to MQTT. (And yes, it would be cool to send too). The RF-antenna seems to be attached to LNA on Pin2, which i just learnt, is designed to connect to an RF antenna, so i was hoping this would not be too hard. The fact that it isn't in the template and i can't find anything mentioned about it, makes me less optimistic.

sfromis commented 4 years ago

You have very good reason to be "less optimistic". Sonoff has a "habit" of not having the RF chip visible to the ESP8266, but send control signals directly.

robbz23 commented 4 years ago

@burt777 There is a group of us that have just accomplished this with esphome. Check out https://github.com/esphome/feature-requests/issues/611. Just yesterday I was able to reprogram all of my remote buttons to do other functions in home assistant.

On Wed, Oct 21, 2020 at 1:12 AM sfromis notifications@github.com wrote:

You have very good reason to be "less optimistic". Sonoff has a "habit" of not having the RF chip visible to the ESP8266, but send control signals directly.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7598#issuecomment-713191655, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJ3RMK5URSLL6FHAJCBJH3SLYKOVANCNFSM4KLQUEVQ .

Skydev0h commented 4 years ago

I had same problem, pressing a specific button on one of my wall remotes caused D1 to suddenly turn on and set high brightness. To solve the problem I paired a remote to a D1 and then cleared all remotes from memory (by long-pressing clear button). Afterwards ghost switching problem was solved.

It seems that it is possible that some remote control bindings were preset in the D1 memory, and therefore it might react to something it shouldnt actually. Pairing a remote and clearing bindings solves that issue. RF seems to control power and dimmer directly, and tasmota can only just report it in MQTT stat category that the change actually happened.

chopperpl commented 4 years ago

I had same problem, pressing a specific button on one of my wall remotes caused D1 to suddenly turn on and set high brightness. To solve the problem I paired a remote to a D1 and then cleared all remotes from memory (by long-pressing clear button). Afterwards ghost switching problem was solved.

It seems that it is possible that some remote control bindings were preset in the D1 memory, and therefore it might react to something it shouldnt actually. Pairing a remote and clearing bindings solves that issue. RF seems to control power and dimmer directly, and tasmota can only just report it in MQTT stat category that the change actually happened.

Which remote have you cleared? There is no clear button on RF433

premiero commented 4 years ago

There is such button but it does not help. It is bottom left one. Press it for 5 seconds after tuning D1 on to power and wait for two beeps.

wt., 3 lis 2020, 08:33 użytkownik chopperpl notifications@github.com napisał:

I had same problem, pressing a specific button on one of my wall remotes caused D1 to suddenly turn on and set high brightness. To solve the problem I paired a remote to a D1 and then cleared all remotes from memory (by long-pressing clear button). Afterwards ghost switching problem was solved.

It seems that it is possible that some remote control bindings were preset in the D1 memory, and therefore it might react to something it shouldnt actually. Pairing a remote and clearing bindings solves that issue. RF seems to control power and dimmer directly, and tasmota can only just report it in MQTT stat category that the change actually happened.

Which remote have you cleared? There is no clear button on RF433

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7598#issuecomment-720952702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGRHRDMKA77ROFSYXKSV35DSN6W5PANCNFSM4KLQUEVQ .

chopperpl commented 4 years ago

Ahh, the pairing button... It’s not working. I had cleared that when initially setting it up and ghosting still happens. FYI, I’m still on stack firmware with eWeLink app.

Pobierz aplikację Outlook dla systemu iOShttps://aka.ms/o0ukef

Od: premiero notifications@github.com Wysłane: Tuesday, November 3, 2020 9:47:42 AM Do: arendst/Tasmota Tasmota@noreply.github.com DW: chopperpl adam.janiec@gmail.com; Comment comment@noreply.github.com Temat: Re: [arendst/Tasmota] Support for Sonoff D1 Dimmer (#7598)

There is such button but it does not help. It is bottom left one. Press it for 5 seconds after tuning D1 on to power and wait for two beeps.

wt., 3 lis 2020, 08:33 użytkownik chopperpl notifications@github.com napisał:

I had same problem, pressing a specific button on one of my wall remotes caused D1 to suddenly turn on and set high brightness. To solve the problem I paired a remote to a D1 and then cleared all remotes from memory (by long-pressing clear button). Afterwards ghost switching problem was solved.

It seems that it is possible that some remote control bindings were preset in the D1 memory, and therefore it might react to something it shouldnt actually. Pairing a remote and clearing bindings solves that issue. RF seems to control power and dimmer directly, and tasmota can only just report it in MQTT stat category that the change actually happened.

Which remote have you cleared? There is no clear button on RF433

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7598#issuecomment-720952702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGRHRDMKA77ROFSYXKSV35DSN6W5PANCNFSM4KLQUEVQ .

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/arendst/Tasmota/issues/7598#issuecomment-720982251, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOKZZOG26Z5QL6LOWYVJQ53SN67S5ANCNFSM4KLQUEVQ.

robbz23 commented 4 years ago

@chopperpl I had ghost switching issues with mine for a while. I was able to finally stop them by clearing RF codes and repairing the remote. When I paired the remote I did it immediately after applying power and holding the remote right next to the D1. I havent had a ghost switch issue since.

The ghost switching is independent of the firmware you are using. Because the rf chip talks to the chip that controls the dimming directly. Since firmware is only running on the ESP chip stock or any other firmware will have the same issue.

On Tue, Nov 3, 2020 at 9:54 AM chopperpl notifications@github.com wrote:

Ahh, the pairing button... It’s not working. I had cleared that when initially setting it up and ghosting still happens. FYI, I’m still on stack firmware with eWeLink app.

Pobierz aplikację Outlook dla systemu iOShttps://aka.ms/o0ukef

Od: premiero notifications@github.com Wysłane: Tuesday, November 3, 2020 9:47:42 AM Do: arendst/Tasmota Tasmota@noreply.github.com DW: chopperpl adam.janiec@gmail.com; Comment <comment@noreply.github.com

Temat: Re: [arendst/Tasmota] Support for Sonoff D1 Dimmer (#7598)

There is such button but it does not help. It is bottom left one. Press it for 5 seconds after tuning D1 on to power and wait for two beeps.

wt., 3 lis 2020, 08:33 użytkownik chopperpl notifications@github.com napisał:

I had same problem, pressing a specific button on one of my wall remotes caused D1 to suddenly turn on and set high brightness. To solve the problem I paired a remote to a D1 and then cleared all remotes from memory (by long-pressing clear button). Afterwards ghost switching problem was solved.

It seems that it is possible that some remote control bindings were preset in the D1 memory, and therefore it might react to something it shouldnt actually. Pairing a remote and clearing bindings solves that issue. RF seems to control power and dimmer directly, and tasmota can only just report it in MQTT stat category that the change actually happened.

Which remote have you cleared? There is no clear button on RF433

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7598#issuecomment-720952702, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AGRHRDMKA77ROFSYXKSV35DSN6W5PANCNFSM4KLQUEVQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/arendst/Tasmota/issues/7598#issuecomment-720982251>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AOKZZOG26Z5QL6LOWYVJQ53SN67S5ANCNFSM4KLQUEVQ

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7598#issuecomment-720985339, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJ3RMOUWWEUXRNRILI6NH3SN7ALVANCNFSM4KLQUEVQ .

sandeep-ma commented 4 years ago

What do you mean by: "repairing the remote"

premiero commented 4 years ago

He meant re pairing.

śr., 4 lis 2020, 03:52 użytkownik sandeep-ma notifications@github.com napisał:

What do you mean by: "repairing the remote"

From: robbz23 notifications@github.com Sent: Tuesday, November 3, 2020 8:27:06 AM To: arendst/Tasmota Tasmota@noreply.github.com Cc: sandeep-ma sandeep@live.ca; Mention mention@noreply.github.com Subject: Re: [arendst/Tasmota] Support for Sonoff D1 Dimmer (#7598)

@chopperpl I had ghost switching issues with mine for a while. I was able to finally stop them by clearing RF codes and repairing the remote. When I paired the remote I did it immediately after applying power and holding the remote right next to the D1. I havent had a ghost switch issue since.

The ghost switching is independent of the firmware you are using. Because the rf chip talks to the chip that controls the dimming directly. Since firmware is only running on the ESP chip stock or any other firmware will have the same issue.

On Tue, Nov 3, 2020 at 9:54 AM chopperpl notifications@github.com wrote:

Ahh, the pairing button... It’s not working. I had cleared that when initially setting it up and ghosting still happens. FYI, I’m still on stack firmware with eWeLink app.

Pobierz aplikację Outlook dla systemu iOShttps://aka.ms/o0ukef

Od: premiero notifications@github.com Wysłane: Tuesday, November 3, 2020 9:47:42 AM Do: arendst/Tasmota Tasmota@noreply.github.com DW: chopperpl adam.janiec@gmail.com; Comment < comment@noreply.github.com

Temat: Re: [arendst/Tasmota] Support for Sonoff D1 Dimmer (#7598)

There is such button but it does not help. It is bottom left one. Press it for 5 seconds after tuning D1 on to power and wait for two beeps.

wt., 3 lis 2020, 08:33 użytkownik chopperpl notifications@github.com napisał:

I had same problem, pressing a specific button on one of my wall remotes caused D1 to suddenly turn on and set high brightness. To solve the problem I paired a remote to a D1 and then cleared all remotes from memory (by long-pressing clear button). Afterwards ghost switching problem was solved.

It seems that it is possible that some remote control bindings were preset in the D1 memory, and therefore it might react to something it shouldnt actually. Pairing a remote and clearing bindings solves that issue. RF seems to control power and dimmer directly, and tasmota can only just report it in MQTT stat category that the change actually happened.

Which remote have you cleared? There is no clear button on RF433

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/arendst/Tasmota/issues/7598#issuecomment-720952702 , or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AGRHRDMKA77ROFSYXKSV35DSN6W5PANCNFSM4KLQUEVQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub< https://github.com/arendst/Tasmota/issues/7598#issuecomment-720982251>, or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AOKZZOG26Z5QL6LOWYVJQ53SN67S5ANCNFSM4KLQUEVQ

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7598#issuecomment-720985339, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABJ3RMOUWWEUXRNRILI6NH3SN7ALVANCNFSM4KLQUEVQ

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub< https://github.com/arendst/Tasmota/issues/7598#issuecomment-721114483>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AK4G564NP4QZUJ4C3LNBOP3SOAAKVANCNFSM4KLQUEVQ

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7598#issuecomment-721482585, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGRHRDJHJNI6T2YJN22GPI3SOC6X5ANCNFSM4KLQUEVQ .

craigsheppard commented 4 years ago

Regarding 'ghost switching', I would like to confirm that the solution tried by @kumy (and @kugelkopf123) has worked for me:

R6 R7 R8 R9 + R11 R12 R13 R14 removed, let's see how it goes

I had 2 D1's which switched on their own every hour or so. I don't have an RF remote (nor will I). I put them under rework and flicked off the resistors, and there have been ZERO issues since (2 days so far).

IMG_8388

Thanks all for the great conversation here!

kumy commented 4 years ago

@craigsheppard I also confirm that ghost switching never appeared again.

ai-xyz commented 4 years ago

Does anyone with the Sonoff D1 and remote also has the possibility to sniff the 433MHz code the remote is sending during pairing? Could be interesting to fake a remote signal with some 433MHz sender (maybe even the Sonoff Bridge or some other sender) for those who are having a Sonoff D1 but not a remote.

sfromis commented 4 years ago

I've got neither, but as I understand it, you can "just" pair the dimmer with the remote code you choose to use, as long as it is the right protocol.

sandeep-ma commented 4 years ago

Right, I had no trouble in pairing it with some other random remote. Only issue was that D1 uses a dedicated Off button while generic remotes use on/off toggle. The I cannot turn it off.

HNJAMeindersma commented 4 years ago

It looks like removing R6 R7 R8 R9 R11 R12 R13 R14 has solved my ghost switching problem (#9493) as well. 48 hours now without any ghost switching. Seems indeed to be a bad RF design.

chopperpl commented 4 years ago

so I have un-paired the RF433 and now there are no more ghost switching. The light is controlled through the HA and Aqara smart button. It seems to me like the RF433 was sending ghost signals to D1, but this may be just my case. At least it is usable now. Cheers,

On 20 Nov 2020, at 11:42, Rick notifications@github.com wrote:

It looks like removing R6 R7 R8 R9 R11 R12 R13 R14 has solved my ghost switching problem as well. 48 hours now without any ghost switching. Seems indeed to be a bad RF design.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/arendst/Tasmota/issues/7598#issuecomment-731091937, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOKZZOGVISM6PH4D5ESW3XTSQZBXTANCNFSM4KLQUEVQ.

digitlength commented 4 years ago

To solve the problem I paired a remote to a D1 and then cleared all remotes from memory (by long-pressing clear button). Afterwards ghost switching problem was solved.

I can confirm that this procedure seems to have gotten rid of my ghost switching issues too:

Currently 4 days up, and no ghost switching!

jan-gerard commented 4 years ago

I have no remote at all, never paired the D1 with any device, and still ghost switching is happening. Since I see in the Tasmota console log that the source for the ghost switching is "SRC: Switch", couldn't the Tasmota firmware restore the previous state immediately? I imagine a configurable 'bug-fix' option that counteracts the Switch behavior. Or can I create a rule locally that restores the previous state? The issue may be to retrieve the state of the dimmer before the ghost trigger occurred, since the present state is the altered one.