My suggestion pertains to the magnetic contact reed switch input. It would be beneficial to incorporate debounce capability into the software code for this input. This enhancement would provide the opportunity to modify the device’s operation, allowing the connection of external switches or relays to this input, thereby expanding the device’s capabilities.
I think it’s a hardware suggestion, and here I’d like to cue @Daniel_Zhan from SONOFF team for further investigation.
Thank you for your reply.
I think both hardware and software solutions could rectify the problem, but I still believe that the software one is easier and more cost-effective.
I use the switch for a lot of things. Just use the dry contact of an external switch and connect it parallel to the reed switch. What i miss is the possibility to change the icon in eWeLink. Maybe a few more icons should be added.
I use it for instance as a twilight switch, a rain switch, a water leak switch, and it would be nice, when I could change the icon. The web interface shows it as a “Door Sensor”, so it would also be nice, if we could change the name. When I use it on my windows, “Window Sensor” would be a better name.
You are right, I also use the switch the same way as you described. The main problem, as I mentioned in my previous message, is the absence of debounce functionality, which causes issues with the way the eWeLink website treats the switch state status (the log file on the website is filled with many entries), and ultimately, the switch status displayed on the website is not reliable.
I managed to overcome the issue by incorporating external hardware debounce functionality, and since then, it has been working without any problems. It is a standard procedure to introduce debounce functionality, either through hardware or software, when dealing with mechanical contacts as inputs to a microcontroller.
Where can I find the log file on the website? I never had a problem with the debounce function.
You can access the log file through the eWeLink App by following these steps: (select sensor, device settings, logs).
You are right, in my case, it was quite the opposite. I tested it with two different sensors.