Update: Switching to the drivers created by kaimyn and enabling polling does indeed fix my Tailwind state update problem, thank you @bobbo
However, this has created a new problem for me. Kaimyn's drivers do not implement actuator, sensor, and ContactSensor capabilities like dbadge's do, so this has broken my Sharptools dashboards. I found an inelegant workaround by creating a virtual garage door device that does implement the necessary capabilities and synchronizing it with the physical device through a webcore piston. Not my favorite solution to the problem, but it does functionally solve my use case of being able to see current garage door status and open/close it from Sharptools dashboard.
If anyone has further suggestions, would love to hear them.
I'm assuming what you are doing is sensing the tailwind magnetic contact sensor mounted on the rail. I connected mine to a zooz zen16 and now I have an independent view of contact sensor status via the zen16. It uses LR zwave so it reaches the garage door from my hub with no issues.
I have not been able to keep it stable, So my work around it put it in Home Assistant, and use the bridge to Hubitat. All the sensors are available on Home assistant. It is more stable. As of late the Hubitat updates have been breaking things like the tailwind, the hue intergration and at times the Govee intergration. It was more stable a few updates ago. Looking forward to them sorting that all out.
Hubitat or tailwind need to fix the problem glad you were able to get it working downgrading always is an option kind of crazy we have to do it but guess it’s a solution!
If this is not a built-in driver, then you can use Claude/Gemini/ChatGPT along with the Groovy source you have to create a version that will work with the changed/new http libraries in 2.5.1.x
I did that for an http driver that I use. Took all of about 20 minutes. I went through about 2 or 3 iterations with Gemini, using errors in the Hubitat log as feedback for Gemini.
If it is a built-in driver, then you should report it as a bug in the "Built-in Apps and Drivers" section of the community forum.