I was an early backer, as previously stated. I’ve used Homey for years, but the initial reason to get it for, voice commands, just doesn’t work.
It was now only performing flow controls based on other triggers which - most of the time - work. Ie, triggering actions at dusk/dawn also fails. I mean, I develop too, but I do like that builtin features perform according to expectations without glitches.
I got frustrated so much now because the promised recovery easy options don’t work and the support request process is flawed. You can’t generate a diagnostics id when Homey is offline or the button to create it is hidden very. well. I imagine I am not the first one with this issue as I understand that apparantly the eMMC becomes corrupted, or worn out due to many writes over time, or power adapter starts to fail which for these items seems to me is like a design flaw.
So yes, I expected a bit more smoother RMA process. I followed robertklep his advice and used a bogus diagnostics report id.