I have a RatGdo connected to Home Assistant that’s then being pulled into Sharptools. It’s worked great for years, but recently it started not going from “closing” to “closed” about 50% of the time.
The status is always correct within home assistant. The other status transitions seem to work fine, like closed>opening>open. It’s only closing>closed that seems to be getting stuck about half the time.
Edit: Sent Doc ID to support@sharptools.com
Has something changed with the device driver, the device firmware, or the Home Assistant software versions recently that might coincide with the timing of the issues?
For internal diagnostic purposes, we have an event cache that temporarily holds recent events so I replied to your email with a snapshot of those events.
It looks like the device tends to spew events for the intermediary states of closing and opening. I suspect that those events are coming in so fast across near the end of the closing → closed transition that the system is unable to determine which one is the newest / last one in.
Take for example, the 12:37 transition from open to closed just recently today. The device emitted 25 closing events and it looks like the final set of 3-4 closing events and the closed event all came in within the same second.
| Date | Time | TZ | attribute | value |
|---|---|---|---|---|
| 10/3/25 | 12:37:08.912 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:08.912 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:08.912 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:08.912 PM | UTC-5 | door | closed |
| 10/3/25 | 12:37:08.855 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:05.054 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:05.054 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:04.262 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:04.262 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:04.262 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:02.748 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:02.748 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:01.797 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:00.914 PM | UTC-5 | door | closing |
| 10/3/25 | 12:37:00.420 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:59.970 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:59.403 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:58.892 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:58.505 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:57.891 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:57.385 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:56.882 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:56.384 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:55.869 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:55.369 PM | UTC-5 | door | closing |
| 10/3/25 | 12:36:54.884 PM | UTC-5 | door | closing |
| 10/3/25 | 11:56:59.117 AM | UTC-5 | door | open |