;D
-=| Brazil – SP – Sao Paulo city- [] |=-
After investigating Forums, Automation related websites, Wikis and all sorts of automation resources in the Internet I finally bought from Amazon my 1st Schlage Wireless Lever (FE599 Zwave capable) and also my 1st Vera 2 to integrate my actual InsteOn devices + my recently acquired DLINK IP camera.
I hope my story of dealing with VERA2 and SCHLAGE locks would help people that faced the problem in the past and gave up and also those who are going to buy and face problems trying to do the 1st step of the integration, doing the BINDING!
- At first I configured everything in my VERA2, starting with the update of the MIOS (UI4) to v.1.1.1245, Wi-Fi, device name… Everything using the Wiki startup/setup guides I could find… Also the Web GUI is somehow intuitive for those familiarized with Routers and other home networked stuff… :
- It took me time to finally make Vera 2 communicate properly with the DLINK IP Camera (DCS-942L) but the information was already in the Internet for another IP camera model DCS-932; (don’t forget to update the firmware to the latest version before…) the URL (/image/jpeg.cgi) + IP + user/pass to were the key!
- My second integration was VERA2 with the InsteOn devices that I have already configured using my 2413UH + HouseLinc 2 software. VERA2 communicated easily with the device and all pre-configured stuff I did were appearing in the VERA2 (sometimes the filter provided with the Houselinc2 bundle were necessary to be used with the laptop I was accessing the VERA2 as I noticed that it was interfering with the InsteOn communication)
- Last thing to configure… my new Wireless Door Lock (piece of cake right? terribly wrong! I almost gave up of the integration)
a. I tried every single procedure I could find over the weekend, and when I tried to bind my VERA2 with the Schlage (FE599) lock I got almost instantly the RED blinking sign of error ( I reseted the Lock so many times, turned off everything close to 900MHz band, put all the devices as close as 10 cm, used the SSH terminal (need to be configured but info is located in Wikis and Internet) to investigate the ZWave messages (need to filter messages “^24” using tail -f command), messed up with all the Zwave device options in the MIOS UI4 menu. Nothing worked.
b. So as last resort I tried to update the MIOS firmware to the v1.1.1338 Beta. Nothing worked again following all the procedures to BIND the Lock with the VERA2 I used previously. :-[
c. Fortunately I went to a friend’s apartment as he also has another model of the Schlage Lock, the BE369. I thought it was mine that was defective…as the VERA2 had all the messages saying that was trying to add the device… and I got no errors only timeouts…
d. I was browsing the MIOS directories (using SSH/Putty) looking for something related to Zwave and I saw the zwave_locale, plus I remembered about the Locale thing, related to US and EU Zwave bands… So even buying the equipment in the USA I discovered that my VERA2 was configured to Europe band… so I changed the configuration modifying the /etc/cmh/zwave_locale file using the unix "vi"command! I thought everything was finally going to work! Again… there was something else to figure out … because it was still not binding at all! Gosh…
e. I live in Brazil and it is expensive to buy this type of stuff here (if it is even possible at all!!)… For me travelling to US and buying these stuff gives me only one chance to make good use of the money… it was a question of honor or frustration for the months ahead… :o
f. So at this time I got started changing again the Zwave configuration and basically I used the 2.78 Z-wave version and no MIOS routing and when binding my FE599 Schlage lock it took about 2-3 seconds in ORANGE color (the Schlage lock was waiting something) and then the GREEN Color of SUCCESS. ;D ;D ;D ;D ;D ;D
g. To confirm that my friend reseted his BE369 Schlage lock and did the binding procedure using the default binding procedure using the high power configuration option. Then worked for his lock too! What a good surprise… It was going to be our last shot and Worked! ;D ;D ;D ;D
To make your life easier here is the ZIP version of this story: - Maybe you don’t need the 1.1.1338 MIOS firmware version, but I suggest to update your VERA2
- Check your /etc/cmh/zwave_locale to match your Schlage region, in this case change to US.
- Follow the ZWAVE configuration below to ensure it is going to work… I don’t want to change anything as it is working now… I noticed that my VERA2 ZWave “Role” changed… maybe the Role is related to the actual linked status…(I am still investigating what is really necessary to make it work)
- So below you will find my actual configurations for the Zwave devices [Options] tab
Role Suc SIS:YES PRI:YES
[ul][li]By default MiOS should automatically configure devices[/li][/ul]
[ ] Use Z-Wave version 3.20 instead of 2.78 IMPORTANT: Read this first
[ ] Use MiOS routing instead of Z-Wave (requires 4.5)
[ ] Limit neighbors to Z-Wave discovery (requries MiOS routing)
[ul][li]Poll nodes learn more[/li][/ul]
Number of seconds to wait to start polling [20]
Only poll a node if the Z-Wave network is idle at least [10] seconds.
Poll a node every [60] seconds.
Unless specified otherwise, poll each node at most once every [30] seconds.
Good topic to read : Topic: Vera2 locale setting causes devices unable to include
http://forum.micasaverde.com/index.php?topic=6652
Results:
Working together now: (MCV VERA 2, InsteOn 2413UH + Switches and Outlets, DLINK IP Camera, Schlage Locks) – models enumerated below:
FE599 : Wireless Keypad Lever => bought at Amazon
BE369 : Wireless Keypad Deadbolt => friend’s Lock bought at Ebay
DCS-942L: DLINK IP camera => bought at Staples
2413UH : Dual-Band USB PLM (InsteOn USB Interface with USB + HouseLinc 2) => bought at Amazon
Cheers from Brazil. ;D