While fibaro is ignorant regarding z-wave locks....

[Guest shapa]

Short how-to

1) Buy MicasaVerde vera3 / lite. It is not expensive, a bit more pricy than Fibaro sensors

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

2) Add z-wave lock on HC2, it will be a "generic" device.

3) Add Vera as a _secondary_ controller (do not forget to switch "z-wave auto configure" off on vera) to your network.

4) Vera will copy all devices information from HC2 and will be able to work with all your z-wave devices, but not configure them (exactly what we are looking for)

5) Create required scenes on vera (like "lock door", "unlock door", etc) with your lock (it will be recognized and work fine)

6) Create virtual device on HC2 with "lock" and "unlock", use it in your LUA scenes (I'm using with a key fob and wall panel)

Example http code to run a scene on vera from HC2:

HC2 = Net.FHttp("172.16.1.99",3480)

response ,status, errorCode = HC2:GET("/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=1")

fibaro:log("Lock command sent")

Job done!

p.s. obviously, you can use huge amount of additional plugins / devices developed for vera to manage them from HC2. You can get info from RFX devices (like Oregon Scientific weather sensors), manage LighwaveRF and may other RF-based devices, control Sonos / Sony / Samsung / Panasonic / etc AV devices... So many things.

p.p.s. i.e. you can control any z-wave device which is supported by Vera (virtually any) but not yet supported by HC2

p.p.p.s. yes, you can control Insteon devices as well.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

[ARIAS 2]

Work Vera a z-wave repeater too?

[Guest shapa]

Interesting question... Don't know easy way to check. It works with whole network independently (you can power-off HC2 for example) and could be used as "backup" controller, but I'm not really sure about repeater.

[Guest jrkalf]

Don't make such ugly topics, just because you can... It's a blunt move and a wildly inappropriate claim to the subject. Perhaps a device as the one you're using isn't supported yet for not having any customer requests to implement it...

A great product isn't made by just bitching about it and claiming greatness to finding other competitor solutions, it's about helping make the product even better and putting in your € 0.02 to make it happen.

have you filed a support ticket with fibaro or a bugzilla request to add this lock as a feature? Perhaps even took the time to send them the manual with all command sets and end-user configuration variables?

A quick search on the forums, (Yes, I believe you to be capable of doing such a search as well), should have shown you there's about 3 to 4 actual z-wave enabled locks being questioned about in the past 7 months. All just 1 simple but not very helpful question: Is it supported. Never has there been a topic with the actual request to add a new z-wave enabled lock device including the basic requirements to actually make it happen. Every z-wave enabled product has the used command sets written down in the manual. Every single one, as if it's mandatory by the z-wave alliance; (Perhaps it actually is). So both the command set to use the device as the end-user configuration parameters are to be found in every manual. How hard is it to send those to fibaro and request this feature to be added?

It's what I do with every device I see unsupported. Also open up the box for developer access if they need access to testing material.

in any other things, enjoy the micasaverde, I found the device to be very slow due to it being based on router hardware. I hope they've improved this in the last 16 months since having parted with it.

[Guest Kuuno]

usually i dont do this but ok...

i had a potential customer choosing between HC2 and micasa. He chose micasa because of little better price. I got to see the solution then and come on...these 2 controllers are not comparable.

the UI of HC2 is much more friendly and has tons of more functionalities. Im sure the z-wave lock support is also coming soon...

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[ARIAS 2]

Interesting question... Don't know easy way to check. It works with whole network independently (you can power-off HC2 for example) and could be used as "backup" controller, but I'm not really sure about repeater.

Thank you shapa, very nice/interesting post.

[Guest shapa]

jrkalf,

"It's a blunt move and a wildly inappropriate claim to the subject. "

bla-bla-bla.

Vera3 is not only about "unsupported currently devices", but also about devices which are probably _never_ will be supported by Fibaro - especially RFXcom (like LightwaveRF) and many others.

My approach is to use my old hardware (or non-standart, which is not Z-wave enabled at all) and integrate everything in a single management system but not to trash it, your approach is very selfish and not smart at all.

BTW, I've got more than 100 z-wave devices at home and more than 40 without z-wave (integrated to Vera).

According to your angry letter, I should remove everything and lost a lot of money.

Normally, people can answer something "go f#ck yourself" on such suggestions, but I'm a gentleman

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

"Is it supported. Never has there been a topic with the actual request to add a new z-wave enabled lock device including the basic requirements to actually make it happen" - sorry, but this is complete *.

Please login or register to see this link.

To be honest - Fibaro support is far from the best, but I could understand that the team is small and they are very busy.

They are _randomly_ answering on emails, ignoring requests, etc.

Yes, for sure I already tried to ask about locks - without any feedback.

[ Added: 2013-04-24, 21:07 ]

Kuuno,

You are right, the process could be used to migrate slowly from Vera3 to HC2 for example (while features are added / bugs fixed - they could live together for years

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> ).

[TANE 12]

Example http code to run a scene on vera from HC2:

HC2 = Net.FHttp("172.16.1.99",3480)

response ,status, errorCode = HC2:GET("/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=1")

fibaro:log("Lock command sent")

Do you have more examples about how to controlling a device.

it will be great also to read the values from the vera.

[LBDuckers 0]

Shapa

Can you please explain how I can get the oregon scientific readings which are being displayed in Vera that can then be replicated / duplicated into HC2 so I can then trigger scenes, etc based on temperature from Oregon scientific devices plus measure temperature of my wine fridge

Many thanks

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />

LBDuckers

[valitasca 3]

Hello Shapa,

I moved all my modules from VERA 3 to HC2, but i can't do anything with ZXT 120 and with SQ BLASTER.

Please give me an idea how to controle them from HC2 and VERA.

Thank you!

Vali

[PIAS 0]

shapa, Hi Shapa..

I keep getting connection timed out while waiting for info when i ask vera to get hc2 devices... help?

[ Added: 2013-09-21, 09:14 ]

valitasca, shapa, how did you move your devices. My hc2 says timed out waiting for information... Did you do anything special to hc2 to go look for the devices?... Maybe as step by step will help..

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

Please login or register to see this image.

/emoticons/default_icon_redface.gif" alt=":oops:" />

[Skaven 0]

Can somebody pleas explain to my how I setup so I can us RFX I wanto turn on and off my nexa lamp, it work on my Vera 3, but now I haw made it to slave it has ip 192.168.1.47 and user login whit pass, and my nexa wall plug has id 22

[Rami 0]

This is exactly what i was looking for Shapa , Just got my HCL and i'm missing a lot of features from Vera . Will try this tonight

[Guest shapa]

Hi guys, just noted some questions here.

Added (yesterday) Night Latch (US-model

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />) ) to my UK house.

The idea is the same - any device on Vera can be easily managed.

But, I realized that it is better to add locks and Vera itself in stand-alone mode (not to the single network) and just to manage it remotely. Avoid "slave" controller mode as Fibaro is unreliable (which in not acceptable for security stuff like locks).

This is much better way as Vera is completely independent from HC2 (which is still very buggy).

I.e., add your locks to Vera3 / Lite and control them via virtual devices in HC2.

Code is very basic (note DeviceNum=6 - it means sixth device on Vera3):

Open button:

HC2 = Net.FHttp("172.16.1.111",3480)

response,status,errorCode = HC2:GET("/data_request?id=action&output_format=xml&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:DoorLock1&action=SetTarget&newTargetValue=1")

fibaro:log("Night Latch Lock command sent")

Close button:

HC2 = Net.FHttp("172.16.1.111",3480)

response,status,errorCode = HC2:GET("/data_request?id=action&output_format=xml&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:DoorLock1&action=SetTarget&newTargetValue=0")

fibaro:log("Night Latch Unlock command sent")

Request status and change icon:

local selfId = fibaro:getSelfId();

HC2 = Net.FHttp("172.16.1.33",3480)

response,status,errorCode = HC2:GET("/data_request?id=variableget&DeviceNum=6&serviceId=urn:micasaverde-com:serviceId:DoorLock1&Variable=Status")

fibaro:log(response)

if response == "0" then

fibaro:log(status)

fibaro:call(selfId, "setProperty", "currentIcon", "1004")

--fibaro:log("lock opened" )

else

fibaro:call(selfId, "setProperty", "currentIcon", "1003")

-- fibaro:log("lock closed")

end

fibaro:sleep(60*1000);

[ Added: 2014-03-29, 20:15 ]

Exactly the same idea can be used for virtually any Vera device including RFXcom (I'm managing my LWRF sockets on HC2 via Vera3 RFXcom plugin)

[Rami 0]

I did the same thing , i tried vera as a secondary controller but then i decided to use it as main controller with the devices that doesn't work with HCL , i'm using http commands to execute scenes on vera from HCL , created a virtual device that has all my Vera scenes and devices i want to use , makes it easy to integrate them with scenes

[Smartelite 0]

jrkalf

I really like the word "request" I have asked Fibaro about ZXT 120 more than 20 times and no answer they always (for 1 year) tell me to wait. In the form you can read "be patient" in one of Fibaro's post

I did what is written here before reading the post

Anyway, I have many ZXT120 around the house and I want to use one vera only as a secondary controller and use the rest of the z-wave network as repeaters with HC2 primary controller

I just have started today

What do you think guys?

No one answered if vera would be like a repeater

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[ Added: 2014-04-03, 12:37 ]

Is there anyway i can see the routing table?

[stevenvd 51]

have you guys read the alpha feature list?

- cooperation with Z-Wave locks

So yeah, be patient..

The locks require a security command class for z-wave. which first of all costs money. well they have money so not the problem. second is time to implement it. As they have been working on a new z-wave architecture for the HC2. they have been waiting to implement it for this new version.

Now is the time for some people, to upgrade to the Alpha, and work close with Fibaro to get the template and implementation ready.

[Smartelite 0]

Ok I will be patient another year no problem

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

But meanwhile, what if we do the opposite? make the HC2 as a secondary controller to vera?

Is it possible?

[Guest shapa]

"So yeah, be patient.. "

+ 1 year to stabilize.

US locks are not supported until US-spec HC2/HCL will be available (it should be already, but I can't find any)

[Smartelite 0]

Hello guys

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

I have tried it once but now it is not happnening again

I am getting "time out error"

it is like both vera and fibaro are not communicating

Tried version 2.7 and 3.2 z-wave firmware

what do you think?