Hello all,
Long Post Apologies in advance, but just doing my due diligence in researching new hardware. Current Vera user and looking at possible migration. Had used automation way back in the X10 days but it just wasn’t reliable enough but when I discovered ZWave gear a couple of yrs back decided to have another try and found it to be great so ended up getting a VeraPlus as it was one of only options in Aus at the time and was relatively cheap (didn’t feel paying $1k+ for a Fibaro with only one non ZWavePlus radio was very futureproof).
While I have been overall reasonably happy with the Vera in terms of reliability/capability it is a pretty dated looking web console with almost no inbuilt logic support so you have to use plugins like PLEG/Reactor and a lot of the support for most of the HA goto DIY devices (Logitech Harmony etc) is all plugin based. What this means is that is makes for most time spent actually trying to figure out how you can implement logic using either LUA, Plugins and virtual switches and I tend to avoid setting up new automation as it seems to take way longer than it should. Enter possible migration to Homey, just wanting to get some community feedback if anyone has done similar migration and also going to list most of the devices / automation I already use to ensure compatibility.
Two minor general concerns;
Lack of actual LAN port, I generally prefer core devices hardwired. Non issue?
Also the 2.0 software update and blog post indicating the complete removal of web interface and move to mobile. I totally understand the rise of mobile but a web interface (which almost saves on dev these days by being Mac/Linux/Windows agnostic) seems a must have? Even mildly complex tasks are so much quicker on a full workstation, and it seems from recent Facebook posts the community share that concern?
Current Device Compatibility;
Core devices are mainly Aeotec Zwave including Screw in LED bulbs, Gen 5 Motion sensors, Smart Switch 6’s, Door Sensors, Quadmotes, Water Sensor?
Remotec 8 button switches
Logitech Harmony x 2 for upstairs and downstairs TV/Hifi control
Kodi for media centre x 3 through out the house
Imperihome dashboards x 3 through out the house
OpenSpinkler v3 (RasperryPi version) for Aquaponics/Retic control
Voice control via Alexa (weird delay with Vera which they admit is problem but haven’t resolved so I am forced to use Automation Bridge which itself is actually a great product but another possibly unnecessary work around)
Broadlink IR compatibility great as an option IR sender instead where a full blown Harmony hub is not required
QNAP Survellience station + HIKVision Cameras
Some other general questions;
Are there virtual switches available? Due to the way voice control works the language used for executing a scene is awkward so I often use a virtual switch to then execute a scene as the language used for switch on and off is much more natural
Unifi wifi compatibility/plugin ? There is a great plugin for Vera which I use for presence detection via phone presence on wifi, works great
Power use reporting?
Call scenes from http/api? One great thing about Vera is the ability to call a scene by http to call certain action is say Security camera software detects movement etc
LUA Scripting or equivalent?
Future integration of smoke sensors/alarms?
Apologies again for the long post, please feel free to reply regarding anything I haven’t directly addressed here that might be related to a migration.
I too am a former Vera user (only briefly) for the same reasons as you, Homey isn’t perfect, no device really is, however I have found it to be miles ahead of vera.
If you are looking for real feedback regarding the web interface then I suggest you talk to people who have upgraded their homey to v2 and have been using the app for several weeks. Rather then people who have just complained and declared Long Live the Desktop.
Lack of LAN port is a non issue for me, and I am more likely to get frustrated that bridges need it - ie what is the Hue bridge doing that it requires a gb connection to the internet.
I personally think the app is great, I have not however recreated any of my flows yet on it, as I have been busy. the really small amount of testing I have done for flows (4 flows) has gone well.
As for device support your best bet is to check each of the devices on the app store, as I doubt any one person has memorized it. However from my own personal experience Aeotec, harmony, Kodi, Alexa, Broadlink all work. And I am pretty cetain that Imperihome does not.
There are inbuilt virtual switches as well as a great app for more extended virtual switches.
I dont know
Yes, homey has extensive reporting called ‘insights’ you can see the version1 implementation here : https://www.athom.com/en/homey/insights/ - version 2 is a sleeker version of it.
I think I would need more information, there is a app which can make http request on any action you would like.
No problems, can live without the LAN port just like the reliability of it more than the throughput.
I know that there can be a tendency for ppl to to hate change but I am also conscious that change for the sake of progress isn’t necessarily innovation or a better solution. On the web console front I do feel that this would be a fairly substantial mistake, I just can’t see how writing “flows” and configuration from a mobile device (even a big screened one) can be anything but frustrating. For direct comparison Imperihome tablet dashboard is fairly wizard driven and easy to use app but the moment I look to do anything remotely more difficult that requires much typing/copy and paste etc etc I immediately look to setup a remote desktop session cos its just so damn slow or frustrating to do much more than tap/drag and drop. Also bit weird from a customer front, might pick up more general users but I don’t even know how effective that will be, SmartThings already have a fair bit of the non techy users who dont care about heavy cloud reliance market covered.
The rest looks like it should be decent, looks like Remotec switches is good, sounds like Aeotec I will have to double check that it covers all the Aus versions of the devices I have.
The http request part, I was meaning something like e.g. http://credentials:homeyipaddress/scenename could execute a homey scene so that it can be called from other applications etc
You shouldnt have to many issues with Aussie devices for fibaro/aeotec, there was a specific release for both just for us aussies, they are very quick to add the ids when one is found missing. However YMMV with other apps.
As I said, I haven’t set up my new flows yet, the mobile interface is more click and select rather than drag and drop (which was the old web interface), and if you really want a desktop for typing you can use the chrome andriod app emulator, a tablet version will be coming - later.
Hopefully someone who has created a few flows in v2 will comment. In my experience flows are not something you are constantly creating, once done they are done.
There was a REST api in version one, it was never really made public available before the webAPI replaced it, homey uses oAuth for security - so it wont be a simple matter of just calling a URL (like vera does) in order to control your homey.
Creating an end point inside homey is rather easy though ie:
Creating and modifying flows is not as bad as I thought it might be on the mobile device. Obviously the old desktop is better as you can see more and most things were only a few clicks.
I do like being able to make changes while out so having that is great but I wish it was an option rather than the only way.
Maybe Athom or a clever dev will be able to produce a web based flow editor. I guess the ideal place would be as part of the current developer section.
Yeh had noticed a few ppl were using an Android emulator, which would at least make copy/paste style operations easier etc.
@Jamie the GitHub link I assume is to a community project for a web based flow creator? Any screenshots of what that will look like?
The idea of a community based web console is definitely better than none at all but my major reason for looking to move from Vera was that the core components (logic, major device support etc) really needs to be supported in house. It’s one thing to have plugins for certain elements but half the issues with Vera are related to plugins that don’t work or aren’t updated and then some other community member than has to attempt to decipher the plugin and rework it etc.
What do ppl make of this thread;
Sounds like very similar situation to myself, in fact even sounds like he uses the same main vendor I do, the thing that swung me towards Homey was the consistent decent reviews as well as a solid GUI logic engine meaning I would be more likely to automate processes due to it taking less time. This sounds very much like he was struggling with compatibility and reliability issues?
I have seen mention of this before but I have no idea how to start with it. It sounds like a good concept.
Is it installed on homey via the CLI or on a local server?
The files on Github don’t look like any other homey app I’ve seen so I presume it is run some other way?
I also remember there was an issue getting the homey key or something so has that been resolved or is it still a case of sniffing web transactions?
Maybe you could enhance the read me to include more instructions on how to use it?
Your 100% correct as far a I am aware, the project was put on hold until v2. Its my understanding that there is also no timeline for allowing developers public oAUTH access, I linked it to show what might be possible.
no camera support - Luke is correct, there is no support for cameras at the moment. They will be coming after v2 is stable/secure.
The core logic is supported in house there is no ‘PLEG’ for homey.
Like all things you wont know until you try it, we (Australians) are pretty limited in our choices, RACV announced they are now selling smart things in Melbourne, though I doubt that it will give you the control you are used to. Otherwise - Vera, Fibaro or a more hands with a raspberry Pi and HASS or OpenHAB
That could be indeed. As with all domotica solutions there are so many factors that could impact the overall working of it. I have to disagree with him saying:
What he actually meant was: "I don’t understand why people blindly jump to the defence of something we all know in some situations doesn’t do what it supposed to do.
Yes I had also my fair share of struggles but overall in the past 3 years ( I guess ) I have to say that things work. Keep in mind that Homey has certain range issues (that are also impacted by the situation…) and that certain devices are not fully compatible. But as said. It really depends on the situation.
Also regarding the flows and the lack of the UI interface in 2.x. I have to agree at first I was a bit hesitant to use it. But now I feel it works like I would. As already stated by @Jamie you aren’t building flows every day so it would only be a pain in the ass (so to speak) in the beginning of the adoption but after that. It shouldn’t.
Yesterday I installed 3 extra door sensors and had it running within a few minutes just by using the phone. So it can be done
I have bought one the smartthings hubs from RACV and although it is just the mesh system + smartthings and not the full hub, so far it is pretty great. There are Samsung plugins that cover most things, then there are community plugins, then you can modify community plugins or create your own. The coverage is huge and so is the flexibility.
Scripting can be done on the app or you can create a type of mini app on the web interface with logic built in.
I haven’t found anything that doesn’t have a plugin yet.
Z-wave coverage is very good and device and product codes can be changed on the fly.
Response times are instantaneous.
The apps leave a bit to be desired but they are in a transition phase, this is the way to go IMO if starting from scratch.
I will hold on a little longer and keep using both, I have a lot of devices and don’t look forward to another transition.
Thanks for the replies everyone, finding them all useful. I was hoping that if I move to a new platform it will be something that will be reasonably long term as it is quite a bit mission doing a largish migration.
I was quite interested in @Luke_Fairbank experiences purely because of the similarity in situation and as it seemed to be quite the opposite of the generally ok user experiences. I had never really considered SmartThings due to not being keen on heavily cloud reliant hubs but it’s simplicity and likely future integration with truly smart Samsung home appliances is appealing.
As someone said it seems like there still isn’t quite one DIY Hub that gets the balance right between reliability, compatibility and ease of use and the commercial grade stuff is out of the question for most due to the difficulty of retrofit and huge costs.
As the FB countdown from Homey looks to be the announcement of 2.0 I might just wait a while and see what everyones experiences are before making a decision. In the meantime I have some spare hardware laying around including my original Gen5 ZWave stick that I first tested with so might even run up a trial of Homeseer. Interface looks as dated as when I used it back in the X10 days but ppl seem to say it just works.
Thought I would follow up and see what people are thinking post the release of 2.0 and the hardware updates and also where my testing is at. Sounds like there is some potential in the phone app but still plenty of the users with larger more complex scenarios saying its just a step backwards for flow design?
Also seems like a missed opportunity that they did a hardware update but kept the specs still quite minimal and bailed NFC but didn’t add a LAN port.
As I wait to see what occurs regarding the web interface I have run up the trial of Homeseer with a Gen 5 ZWave stick. So far its quite impressive;
Obviously software based means you can put as much hardware horsepower underneath it as you want so as long as the software is coded reasonably efficiently it should remove any bottlenecks from that aspect and even adds flexibility of running in a VM
Logic engine is strong, super strong in terms of the built in elements out of the box
Compatibility with Aeotec ZWave seems strong (good thing for those in Aus as the Aeotec and Fibaro brands seems to have the most options and market penetration over here). Tested out Quadmote, Multi Sensor and new Water Sensor (not even supported in Vera atm)
Compatibility with most of the DIY HA go to’s outside of ZWave is strong through plugins (Harmony, Imperihome IFTTT, Alexa etc) and the plugins seem quite in depth in terms of their feature set
Logic seems to execute reliably and lag free (really need to test at scale to verify but that is hard to do without doing a complete migration)
Downsides;
Web Interface is dated in terms of looks and def due for a change up (doesn’t matter as much as long as Logic and device support is strong and quick to generate automations as end users don’t need as much physical interact with good automation designor if they do its through Imperihome or other user centric front end etc)
Seems to be based around .Net, VBScript etc style programming where as programming these days tends to lean more towards web technologies and Python etc
Bit of a learning curve in terms of how things work and how the standard concepts of devices, rooms, pairing etc are dealt with even with a tech background
Price of $599 + $40ish per plugin is in the higher end of the DIY market especially considering no hardware included but they do seem to do some good %50 off sales each year and its not extreme if it reliably works
Phone app is only ok, not the most polished out there
Still relies on plugins for the DIY HA go to items support
I will test this for a few more days within the trial and then move to next test. I have located a previous generation Mac Mini at work and will run up Indigo. I am not much of a Mac guy (rate iOS, think MacOS is pretty average) but work with them a fair bit so will give it a spin. The Indigo application interface looks pretty good and fleet of plugins also looks strong and have heard good things about reliability. Will add to the thread once testing is done
Some moderator locked my thread and directed me to this one. Not a good start for Athom if they want me to consider moving from Vera to this device. So I was hit by a bug in my Vera that causes huge delay if commands are sent to a Fibaro Double Switch, and the delay stacks so if you have multiple switches in the script or scene it will take up to minutes for it to complete (!).
Anyway. Im looking at Athom to replace my Vera. One of the concerns is scripting, its really easy to script with lua on the Vera. Its seems direct scripting is not supported in the Homey, you need to create actual apps/plugins? Which is fine if you want to create general support for something, but I also use it for advanced control of my scenes. For example on my Vera I have a scene that listens to my projector, when it starts I iterate over all the lights that I have added to a array and looks if they are turned on. If they are it will save them to an array. When the projector goes off the projector screen goes up and the lights that were on are now turned back on and offcourse the dimming level is kept. Is this supported with Homey? It seems scripting is only available if I do a full blown application, but feels wrong for something as easy as custom scene control.
Other than that I worry about Fibaro support, for example as I understand it Roller Shutter 2 (Projector Screen) is only partially supported. But I will ask for that in the fibaro app forum
The mods are also users, not employees. Having said that : this seems like the perfect place?
As for scripting, Homey also has http://homeyscript.athom.com/ but not many people using it for now I think. Rarely needed with Homey’s UI.