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
[Video] Homey and Doorlock
This discussion has been closed.
Comments
So for example i have;
1 GreenWave Zwave Sockets and I want to use it to switch LED lights in the kitchen.
1 Fibaro Zwave Relay and I want to use it to switch Frontgarden lights.
1 2x1.5kWh Fibaro Zwave Relay and I want to use it to switch Bathroom lights.
What do i need to configure in Homey to get this work?
I excluded them from my other controller and am experimenting with those to see what happens.
"Do you allow use to use your configuration information anonymously to improve homey's functionality? Yes/No"
If this is a checkbox during installation/configuration with a good explaination what the information is used for I'm sure you'll get enough data to build a decent database.
I'm building a generic template to support all Z-Wave devices. For some custom features devices may have there are apps. They are also used for little things to make the devices 100% plug and play.
I mentioned that the lock seems to lose connection after a while, when I reboot homey or use the lock with smartphone it becomes aviable again. Will this be fixed with the full implementation of its command class ?
So I should set group 3 to 1.
I checked the setting of the main node. Group 1 is set to 1.0 ??
If I remove that from group 1 and enter 1 in group 3, I can't save it... When I change it back to what it was, it saves right away.
Complicated
Did return the lock
Yes
Can you post a screenshot?
Yes.
Should I set the danalock to group 3 aswell?
BTW, sorry for kind of hijacking this thread
I don't know at the moment for which brand were going to make an app and what brands not. Depends if the devices need one. We'll announce it when the time is there.
Thats my last question for a while
indeed complicated.
Maybe for now a dedicated Zwave Config topic?
@Taco
Bit disappointing to read that Zwave support is that complicated and apps are needed...
When to expect the apps? X Days/months?
It's no different than with your Vera actually. Here is't called apps, in your Vera it's included in a database so you don't notice it. Different style, same result (in the future )
My point for the near future;
When will these apps be ready and can I use all my (battery powered)modules (Fibaro/GreenWave/Aeon/Philio) at delivery "OOTB"?
And its not important how it works, only that it works and for now i don't have a good feeling about that for the near future(1-2months!?).
My current controller (Kickstarter Almond+) had a lot of problems also in the beginning (still has, but it's usable now...)
When I look around, even Fibaro HC2 and other big brands have problems with new modules.
So you just need patience I guess.
I also read that a motiondetection reported by a zwave device can not (yet) be used in a flow. Is that correct, or am i missing something and is this related in the device being zwave plus or not?
If you really expect that you should be part of the MM crowd in my opinion.
No one can tell you when these apps will be ready, since they don't know. This is still a development phase in wich bugs are discovered and patched. And I'm guessing they'll want to splat the main part of the bugs before investing serious time in apps...
I'll wager an answer to your question:
No. No, you won't be able to use all of your modules OOB (fully).
But that's just an assumption on my part, and I don't see why you would expect much differently.
Athom does seem to work hard on fixing stuff. Why not try to be part of the solution instead of the problem?
And @ taco/athom, thnx for the replies, keep up the spirit
This is nice in theory but does bring some problems. For instance, people are not used to setting association groups. I think a good manual or a tooltip when adding devices should guide you to it or remind you of it. As soon as you get used to this, it shouldn't be a real problem. It is however a big drawback of Z-Wave. Not something that Athom can help.
On the other hand I only hear troubles about Zwave modules.
I only "say" what I "hear".
And the only thing i'm say about my own situations is that a lot of thing in our home are automated based on statuses of Fibaro relay, AEON plugs, Zwave Plugs and in most cases its based on Lights status and power usage.
And if Zwave is not solid enough or functions/features are not working properly, then I keep my Homey in the box (with very much pain in my )
And the only thing i'm kindly asking; which devices need a App and when can we expect these apps?
I ask that because these apps are not on the "trello-map" (or do you guys mean "Z-Wave Apps API" as "Z-Wave Device Apps" ?)
But I think the Zwave App API is the API which is needed to get these apps working. So because the Zwave API is still in the "Features we're working on" "status" the real Zwave Device Apps will be released much later.
The way of working is fundamentally different then with other controllers. Finding the correct association in the manual of the module isn't all that easy sometimes (at least not for me). So that's something that will need to be explained very well.
It seems harder than it is
There's some confusion right now because of the associations.
But basically you put your device in 'discoverable' mode, you let Homey look for it, and it's added. Simple as that