I think I finally got the full picture, sorry . Do you actually ever see your thing go offline?
In an ideal world the thing would go immediately offline as something happens to it. It is the job of the binding implementation to make that happen. In reality that is often not easy to accomplish for the binding. If something bad happens to the device that the device becomes aware of itself then the device can inform the binding in real-time. However, more often than not the very problem that happened to the device prevents it from telling the binding (device breaks, loss of power, loss of connectivity). For those cases the binding can only infer that the device has problems by lack of response. But checking whether the device is alive comes at a cost - network bandwidth, overall system load - we don’t want to check every couple milliseconds. The binding will decide how often to check based on that cost. For your Hue light checks are very frequent as they are not too costly (bit of network load). For Zwave however, where many devices run on battery, connections are kept to a minimum as each connection impacts battery life. That’s why you see a slower response to detect problems for ZWave devices. If I remove my Aeotec Multisensor’s power it takes ~2 minutes (which is its configured reporting interval) for it to go offline. While that is not real-time it is quite reasonable for most use cases given that a device going offline should be a very rare occurrence.
The problem is that you have a frequent connection issue. Hopefully the debug logging will tell us more about the issue. BTW, how far away is your garage device from the next zwave device or controller?
I am curious about one other thing - would you do me a favor? You say the switch is normally ON and then you press it. That means you are sending an OFF command to the device. I am curious what happens when you send an ON command to the device. It is interesting that Aeotec exposed the toggle behavior of the garage door as a switch, because as you said it’s a trigger and not a switch. My guess would be that sending ON or OFF will both trigger, but would love to see.
To test this easily you can replace your sitemap entry with
Switch item=Garage_Door_Controller_Fibaro mappings=[“ON”=“On”, “OFF”=“Off”] icon=“garage”
Now the UI will render the switch with two push buttons - that way you decide at any time whether you want to send an ON or an OFF command. Could you try both commands and report what happens?
Side note: Once you are past the failing connection a single button is probably a nice UI choice to let the user operate the door as it avoids the weird “switch goes to off and then back on”, something like:
Switch item=Garage_Door_Controller_Fibaro mappings=[“ON”=“Operate”] icon=“garage”