[Can I write SOLVED !? - at least it works for me ]
The problem is evident, as in my case, when binary sensor has to notify the buzz of my intercom, which usually should be pushed for less than a second (it depends on how polite are the people ) so Iāve solved in this way:
Iāve wrote a rest_command (with pergola.fabio support) to switch OFF the binary sensor and created the automation that works after 1 second that binary_sensor is on ON state. In this way:
people need a solution and in my case it is solvedā¦ and with your response the only solution is an update of HA so, what are you talking about? in any case my question on āSolvedā was ironic but it is evident that you did not get it. Iāve done my goal and people like me who read this post now have a solution because there is this option without any hardware works, thatās why Iāve shared. Farewell
Iām very new to HA, Pi, coding and home automation (like one week old). Iām having the same problem on my very first sensor. I need the Pi GPIOās to be reliable. Looks like Iāll have to work around the issue before Iāve even got any sensors working!
I thought I had a broken Pi so I clean installed Rasbian with Node-Red. It detects GPIO state changes just fine, so, like others, I conclude itās a software issue not a hardware fault.
I use the local IP address of the Pi itself, I run HA in Docker so localhost probably would resolve to the container. For info, the Pi4 runs Raspbian (Buster).
Would this work also on a Raspberry Pi running Hassio directly?
I am facing the same problem of unreliable edge detection. My use case is for rain measurement - I have a measurement device with a reed switch that would provide a pulse every 1mm of rainfall. The signal will therefore be very short whenever the internal cup swaps from one side to another.
I would hope for a fix since the rpi_gpio approach was simple enough to fit my needs.