RROD after update to stable (coming from experimental)

Eternity

After the update to the latest firmware - I came from the experimental channel - I have woken up twice to find my living room lit in brothel red. Not what I had hoped to see, and completely new for me; I have never had a RROD before. Fortunately, a PTP solves this.

I have send a log, with this code: 3AFC5CA1CB

Hope this is looked into and solved; a PTP has to be performed manually and until than, my curtains are drawn (and other stuff doesn't work anymore). My smart home becomes pretty dumb ;-)

GeurtDijker

If it happens without getting an update it is something different than the RROD a lot of new Homeys (with still the old Factory Updater) and users upgrading experienced last weekend.
I guess you checked that the last FW upgrade eventually succeeded to 1.0.1

Best to create a issue in Github with your specific case
(Current FW, when you upgraded from which FW, Dit you return from Experimental to Experimental Not selected? when it aprox. happens etc.  )
https://github.com/athombv/homey

lubbertkramer

Maybe better to use the topic that already is combining users with the RROD since saturday / 1.0.1 -> https://forum.athom.com/discussion/2247/red-ring-of-death#latest

Eternity

Thanks. Will use the other topic.

GeurtDijker

@lubbertkramer ;
I would normaly aggree to stick with one thread/toppic, but I find the other thread after the discussion changes very off-topic ...
beside that I read here and in that tread two different Issues, 

I guess @Eternity  is a Homey user for a longer time.... Upgraded from Experimental to 1.0.1 and has RRODs after that.
I haven't seen that... 

The other thread as I also experienced with my second Homey:  from store the Out-of-the-Box experience of the Updating the Updater. (maybe also happens to ppl updating from 0.x but my 1st homey updating from 0.10.9 to 1.0.1 went flawless)

@Eternity,  If I am correct, Will you adjust this tread tittle and eventualy add more info? Something like "RROD - Daily Running v1.0.1" and create a GitHub Issue for that? I am sure Athom will Pick up and contact you to help you (analyzing, troubleshooting, fixing) .