During a Ride Countdown the primary binary_sensor goes unavailable

[edwork]

Only tested during a pre-recorded 20 minute ride, during the 60 second countdown my sensor went unavailable.

Steps to Reproduce:

• Select and start a pre-recorded ride
• Observe the binary_sensor._on_peloton sensor go Unavailable

Likely what's being returned during this time is either null or different than the expected value. This should be a trivial fix.

[ichrispod]

I’m having the same issue. When I start a ride, all sensors go ‘unavailable’. Then my watch dings that a ride has started (20-30 seconds) then another 30-45 seconds all the sensors come back.

I have an automation setup to adjust the lighting during a ride. It runs, but only after about 60 seconds into the ride. On workout completion, it’s about 20-30 seconds before the lights return to normal.

[edwork]

I'm still tracking this issue, I also have a failing automation that isn't observing the sensor going from off to on, instead going off, to unavailable, to on.

The Start Time and End Time aren't being populated initially during the countdown of most recorded workouts, and this knocks the whole sensor offline. I'm experimenting with some logic that ignores this behavior and allows the rest of the sensors to populate.

The fix should be coming soon.