Unit is up, and found on network, went to screen saying "Hubitat Elevation Update Tool"
But after half hour did not update. So I unplugged and tried again.
Now it says on same page, "Unknown status, please try again"
Any suggestions?
Unit is up, and found on network, went to screen saying "Hubitat Elevation Update Tool"
But after half hour did not update. So I unplugged and tried again.
Now it says on same page, "Unknown status, please try again"
Any suggestions?
In addition, went to main page, and it says "select one of the following versions to switch to:"
But no selection, just a Submit button
Definitely give support@hubitat.com a shout.
Check your browser, I use Chrome.
Hope all gets sorted.
I am, and I was using firefox, so now going to reboot and try chrome. If it ends up being browser I will report back for future users.
Are you redirected there automatically after typing in the IP Address? That port and page is for switching firmwares I think...
What happens if you go to http://192.168.0.248:80 ??
Did you start at portal.hubitat.com ?
Ok so dont try and be tech savvy like me. Using the IP address. Use the portal address, there must be a token being passed from Habitat to the device. It finally updated and completed. Again, on any setup failure, use the portal to reconnect to the device.
For 1st time Boot, yes. Portal works to Register the device and does a token or key exchange. For a lot of people, plugging in the Hub is so exciting, nothing stands in the way..
But it's important to make an IP reservation in DHCP using the MAC address on the bottom of the Hub. The hub really needs a static address.
However, once you get past registration, if you're on portal and hover over the hub's link, it's just your local IP address. Feel free to go direct after registration is complete.
Well I did set a fixed address by mac address in my router, of course this is better and did that from the beginning. When I registered it via the portal, it wanted to update, which is fine, apparently it will not be fully registered until after the update. And I had started accessing it via the local address, so that was where my failure to understand was. When I went back to the portal on the failed update, it was able to finally update and register and all is good.
Now I don't want the developers to get a big head, but I am truly impressed! Moving from a wink hub that didn't pickup up temp sensors in some of my devices that had that additional ability, or the ability to adjust the sensitivity of the motion sensor absolutely rocks@!
So keep up the good work, and as soon as I can sell my wink hub, I am getting a second one for another location of mine!
One more thing I forgot to mention, is I was afraid of not having some remote control, such as an app. In actuality I feel the web page for status and control of devices is just fine, other than a bit kludgy on sliders when your trying to change by 1% settings. Maybe adding a < or > above slider to increment/decrement by 1% at a time? Just a though.
I prefer remotely not to have access to configuration so I am very happy with being able to remote access and control devices only through the cloud.hubitat.com and this works great.
Really looking forward to do a bit of programming with this when I get time.
I've gone out on a limb and said aloud that I think Wink is on the list of HomeAutomation products to die out. I'm saddened because I think Wink and StaplesConnect got the radios right. But being closed systems, they could never keep up with the flow of new products and thus StaplesConnect has died, and will soon, in my opinion, for Wink.
The question then is.. how do we, the Hubitat Community, assist Wink migration. Maybe it's as simple as a translation table... Wink calls it This.. Hubitat calls it That... More likely there are features of Wink, and I know that their Lutron support is mighty inferior to Hubitat, but requires an additional SmartBridge PRO to achieve that, which should be clear right from the beginning.
Any other ex Wink'rs here?
Your right I believe, wink was rock solid stable and pretty easy for anybody to configure. But is closed like you said and not extensible by user. Also lacked basic controls to some devices. Donβt know if they will go the way of the dodo bird.
Depends on weather they change attitude on being bit more open or not.
I really like the local processing, and community work, and hope to be able to contribute when I have time. But I do electronic design programming and component level design for space all day long lol so helping will be after learning the framework and understanding of the lower level stuff before I can contribute quality contributions.
You guys have a great developing product. Keep it up!
@csteele, you must have seen this one on Reddit. It is something for Hubitat folks to consider for the near future.
Actually no, hadn't seen it... can only take Reddit in short doses.
I was reacting really to the influx of Iris users and specifically their frustrations. The time between Lowes saying "looking for a buyer" and "closing the site in a month" was way too short for anyone, and Hubitat specifically, to get the "translation table" going.
I'm not on any campaign to be a "wink is dead" voice. My opinion is.. if a wink user, for themselves, decides Wink is dead, couldn't we have a pile of words and screen shots, to assist them?
Maybe not a pile of words or even a bunch of long threaded conversations.
I think back on my move from Wink to STs. While some have no problems with those GE link bulbs and those newer Cree bulbs, my HA life got much easier and had better outcomes including much higher WAF the day I replaced all of those bulbs with Sengled bulbs.
Then when I picked up a ST v2 hub I made the choice to add nothing but repeaters first and to make sure they were each repeating properly for the spaces I needed each of them to cover, things improved again.
And finally I added zwave pieces and added nothing but the wired pieces first just as I had zigbee repeaters.
Now today, I'd seriously consider not doing zwave at all. There's a reason Amazon only added a zigbee radio to one of their Alexa devices and I suspect it's because they realize all of those pairing, repairing, and removal issues that zwave brings to the party.
And then the final piece is I'd consider what type of zigbee devices I want to use in my system and then carefully pick the best repeaters for those devices.