This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed
Homey v1.0.2
This discussion has been closed.
Comments
It was after this successful update, that I read the horror stories of others...
Great improvement in Greenwave powernode status; so far no green LED's. I also see that z-wave response seems faster (I use flows that are triggered by motion sensors).
the flows are worthless if u loos all devices
the only thing and maybe there are others also,if i give a voice commando you should see that in the speech-input
page but it is totally blank
- Using Linux (bootable USB disk can be made from this version: https://www.ubuntu.com/download/desktop, you can boot off the ISO and open the terminal)
- Follow the steps here (OSX, Linux or Raspi) https://forum.athom.com/discussion/comment/18032/#Comment_18032
- At the end of the procedure (step 13) you'll see and endless loop of the terminal trying to connect, at that point the reset has been done and Homey is back at 0.8.17
- Boot it up, then after a minute hold it upside down and wait for the countdown (10...0)
- Put it back on its feet and go to setup.athom.com using Chrome and follow the instructions there
It'll install a hotfix and then download and install 1.0.0.2. After that, choose Keep my data (if you want) and you're done!
My Homey recovered with the above procedure with zero data loss (that I can find). Good luck!
<removed>
Credits to @jeroenbos22 and many others on Slack for supporting! Power to the community!
A quick edition to step 1) URL for Recovery-Files:
<removed>
This is also listed in the topic a few posts above the linked one.
To others experiencing the PROUD (Purple Ring Of Update Development-mode) issue.
Please report them (also if successfully solved with above procedure) in this topic or at the Github issue (https://github.com/athombv/homey/issues/1107#issuecomment-263052753) to be able to track how many users / Homey's suffer from this issue
https://github.com/athombv/homey/issues/1107#issuecomment-263080401
You need to create a USB-Bootable Linux.
You can use this tool: http://www.linuxliveusb.com/ and this image https://www.ubuntu.com/download/desktop
So you only have to boot from your usb stick and you've got Linux running.
They have a product now which has been released to retail / general public and should not only depend on (the excellent, yet limited) support from the community throughout the weekend...
Athom needs to create a windows application at least, but at best it would create a fail safe recovery (should have bootstages anyway) that only requires the Homey. But if that is not possible, then I should (as common Windows user) be able to connect it to my PC and use a Windows app that performs the tasks.
Another thing:
I know that users of the fist hour are most likely Linux users. They are used to this. I am a developer, but a Visual Studio C# developer used to the most powerful and productive development tools. I wanted to create an application (Bose Soundtouch), but the way you need to program and debug your app is masochism. So, I stopped even trying.
Once there is a Homey emulator (or something like that on the PC) and I can debug within Visual Studio (set breakpoints etc.) I am willing to program applications. But not like this, using writing to the console to see what happens. We have passed that stage, at least I have.
2) The desktop app which is the only "browser" officially supported will have a restore option. This is to be expected in a month but won't be necessary for stable firmwares...
As for breakpoints etc, I'm no programmer but is this possible when using asynchronous javascript?
I am a C# developer, but now at work I now also need to program the front end. We use e.g. angular and stuff. Debugging can be done ok. But with Homey it is just too tedious and for me too frustrating. It is like building a sky scraper with only straw, clay and bare hands.
Seems that homey isn't listening that good as before.
I have more problems that my Hue lights are not switched on. Since the update to 1.0.1 (and the fix 1.0.2) the hue lights are not switched on. Not by using sunset trigger nor by using a specific time. For more than a week the lights are not switched on and I am almost in a state where I pull the plug from Homey and let the Hue Hub control the lights again.
But I will try what you said: press the add button for Hue devices.
I will let you know this evening if this did the trick.
edit: done, and now see what happens this evening.
That is strange because i can control my hue thru the hue-app.
Do i have to pair the hue bridge again?