Closed luebbe closed 3 years ago
My guess is that there is a problem, when a color transition is triggered while there is still one in progress
Will need to look at this. My guess as well is something changing the object while it is used. There are some conditions that panic() when that sort of thing happens, but I kind of expected for those to produce a trace pointing at the culprit.
afaik HASS UI only generates an MQTT message when dragging stops? Our color widget does not do this, and sends all updates as they happen
I think this should solve it? Locking seems out-of-place right now, so is the manual panic(). I only briefly tested this, so please check it out with the current dev build
Bug description The device (H801) reboots when the color is changed by dragging the brightness/saturation selector with the mouse over the square or by dragging the color selector. It does not crash when you just click on the desired color or brightness/saturation.
My guess is that there is a problem, when a color transition is triggered while there is still one in progress Therefore I also added the device to Home Assistant in order to see if the crash also occurs when the color selector in the HA UI is dragged and the commands are received via MQTT. But in this case it works fine. No crashes. The crash only occurs, when the selector is dragged on one of the two native Espurna color selector UI controls.
This is the log output
I started dragging after the
[026028] [RELAY] #0 set to ON
line.