I want to avoid any duplication where possible, in my current ST environment I have both Alexa and GH (Alexa is in the process of being kicked out) but I don't link either of those ecosystems to Hue directly for example otherwise I end up with the same device twice and that just ends up causing more issues than it solves..
Just want to get to the point of having one central hub as the master and then spoke anything else off it, obviously the central point would need to be Hubitat due to the local side of things..
Referring to my earlier comment on the forums being too locked down for prospective buyers and need to either have a specific area for these users (as I expect you guys don’t want to do anything to make it difficult for potential customers to get in contact)… I can’t appear to send a private message to an admin… copying in @bobbyD if you could PM me please about something unrelated, but also perhaps look at at least allowing DMs to admins
It's legally not "pre-release" once you can just buy it from an open website, which you can now do with this.
However, I'm one of those people who reads the warranty and the user manual before I buy something. And the warranty statement on hubitat is very clear that it still in the development stage and is not warranteed as a finished product yet.
When you put it in your cart, there is a "terms and conditions" link before you complete the purchase. That's where the warranty is.
Customer acknowledges that the Hubitat Platform is under continuous development, is not complete or otherwise at the final stage of development and that Hubitat makes no representation that the Hubitat Platform is error or bug free. Customer acknowledges and agrees that the Hubitat Platform may experience unscheduled downtime and agrees that Hubitat shall not be liable for any harm resulting from unscheduled downtime.
So the information was there at the time of purchase, although I know a lot of people don't bother to read terms and conditions.
I understand the “early adopter” concept and have read the Hubitat “Warranty” statement. From what I read, they will replace a defective product. just are not warranting it in use or purpose. That kind of statement would not be foreign in a great many written warranty statements. So for me, I’m good with the understanding that i have a (90) day warranty against defects.
I’ve enjoyed reading this thread and will be ordering my Hubitat in just a few minutes. Exiting the world of SmartThings outages and dependency upon the Cloud is very attractive to me. Looking forward to using the Hubitat and helping it grow in use.
New owner today (3/22/18)! Working great so far. Moved over about 14 devices from Smartthings. Still have about 100 to go. One room at a time. Also using the ’ Other Hub Event Pusher’ app so I can control them using Google Home and ActionTiles.
One question though, I can’t seem to start new threads or reply to most on here. I’m logged into the forums the same as I am for the hub, using my google account. Is there something that needs to be done so I become an owner on the forums? @bravenel thanks
Hi All, Just joined the forum. I haven’t bought the hub yet but I’m absorbing as much as I can from the forum. I’m hoping to get most all devices and automations transferred over in a weekend. After I purchase, I’ll probably start looking at Rule Machine and plan out how to rewrite all my WebCoRE pistons.
I don’t believe I have anything that’s incompatible except Google Assistant, but it looks like I can get that to talk to ST, and then to Hubitat. I do have a few ST_Anything devices going on, but it looks like @ogiewon is here already, so I’m not worried.
In the event I have to hang onto the ST Hub for a few things, am I right in thinking I can have virtual switches in Hubitat that control ST devices?
Do ALL groovy device handlers work with Hubitat without modification?
Migrating does take some planning and consideration.
Keep in mind you will need repeaters in both for end battery devices to stay working.
Depending on distance from hub or nearest router (z-wave or zigbee plugged in / self powered) I’d start with the repeaters first and then endpoints, room by room.
Okay. I’ve got about 90 devices. So the procedure should be to start with the wired devices. Exclude from ST, then include into HE. Then move onto battery devices. Automations last. I only have about 3 direct associations so I assume I’ll have to reassociate them. I don’t want to end up with messy ghost devices and other loose ends and such. Has anyone put together a step-by-step perchance?
Ah I see what you mean. So theoretically I could run a Z-Wave Repair, followed by a Zigbee refresh (unplug+remove battery for 15mins) after ripping apart my mesh.
But yeah, this is why I want to get it all done in a weekend.
