you can't use nslookup to find the envisalink, its not a DNS name. If you have SAMBA on your MAC you can use "nmblookup".

This is from the envisalink FAQ

labuser@romulus:~$ nmblookup envisalink
querying envisalink on 127.255.255.255
querying envisalink on 192.168.0.255
192.168.0.102 envisalink<00>
labuser@romulus:~$

That command is not recognized so I guess I don't have SAMBA. I'm hitting road blocks left and right!

Chad

Well, maybe it is time for brute force. In a terminal window, try pinging your network's broadcast address. If you are using a net mask of 255.255.255.0, then the broadcast address is the first three octets of your network number, plus 255 like:
ping 192.168.0.255

You will see a repeating list of ip addresses as each device responds to the ping request. You should be able to eliminate most of the addresses like your router, your Mac, etc. Then, your envisalink is on one of the remaining addresses.

There is another possibility. I am not sure how your network is setup, but, it is also possible you somehow have NAT'd the network port the your envisalink is connected to. In that case, it will be on some other network. Check the NAT settings in your Airport to be sure. You probably won't want NAT on and should change the setting to Bridged.

Also, check the log on your airport, it may tell you something, like if it assigned a DHCP address to the envisalink .

Install the old Airport Utility and get to the DHCP page like you were expecting to. You can have both installed.

http://support.apple.com/downloads/#airport

Note to self, don't update to v6+.

Further - read this post about it, which is why you can't find it and using both, etc.

https://discussions.apple.com/thread/37 ... 0&tstart=0

Thanks for all the input. You guys are a fountain of knowledge. I ended up plugging the the 2DS into my Windstream router, and found the IP address. It is linked and I have logged onto envisalink's webpage and everything seems to be fine on that end. I still have no control over my security system through Indigo. I cannot Arm/Disarm the system. I'm not sure what to do next. Any suggestions?

Thanks

Also, I tried entering the IP address in the DSC plugin preferences. When debugging is enabled I get this, a new line every second:

DSC Alarm Debug getConfiguration start
DSC Alarm Debug STATE: Startup
DSC Alarm Debug getConfiguration start
DSC Alarm Debug STATE: Startup
DSC Alarm Debug getConfiguration start
DSC Alarm Debug STATE: Startup
DSC Alarm Debug getConfiguration start
DSC Alarm Debug STATE: Startup
DSC Alarm Debug getConfiguration start
DSC Alarm Debug STATE: Startup
DSC Alarm Debug getConfiguration start
DSC Alarm Debug STATE: Startup
DSC Alarm Debug getConfiguration start
DSC Alarm Debug STATE: Startup
DSC Alarm Debug getConfiguration start
DSC Alarm Debug STATE: Startup
DSC Alarm Debug getConfiguration

I was playing around tonight and tried to arm/disarm the security system from Eyez-On website but nothing happened. Do I need to reset/reboot the DSC panel? When I type in the IP address into my web browser, it connects but takes a long time to do so. I'm not sure what's going on but I can't get this thing to work. Any help would be greatly appreciated.

Eyes-On phone/email support is great - I've pinged them. Even before buying a 2DS. Don't hesitate to reach out to them.

Did you completely power down the panel to install it? (battery disconnected, etc. etc.) If you are seeing it correctly now @home on the browser, and you properly registered it with your account by entering the MAC address of the 2DS unit, you might need their help with their account services vs. something on your side.

You might want to focus on getting the 2DS working with your home browser and then their website/eyezon services before trying with Indigo. I got that all in place before even installing Indigo (new user).

Travis does have to make some adjustments to the plugin regarding the 2DS so that might be released while you sort out the 2DS issues specifically. Knowing that's all working properly and as expected will simplify maters for you when you deal with Indigo.

If you do get it all working and want to explore the plugin alarm 2DS connectivity, but wait for the next release for full implementation, turn OFF create variables in the config, and do this in the config to get rid of the debug issues you mentioned;
Switch the interface to IT-100, selecting a serial port, doesn't matter which one, it won't get used. Don't save yet, immediately switch back to 2DS interface, then save.

Then we need to give Travis time to get a chance in his busy schedule to release another version.. once he does, I'll be cranking out the bells & whistles @home with it too.

Cheers!

Thanks Fishy. My alarm guy installed the 2DS so I don't know if he powered down the panel or not. I will try that first. Then, if nothing happens, I will give Eyez-on a call. Thanks for the input!

No prob, good luck!

I followed the instructions, which includes a 100% power down probably for safety, and also for the 2DS to register as a keypad with the main board. Get it to work with a browser @home, then with eyezon service, and you'll be golden.

FYI Eyez-On is pushing out 2DS firmware updates today which unfortunately break the API / TDI for the plugin.

I had already sent Travis an email detailing things prior to the eyez-on post going up clearly stating they changed the login process for API/TDI without backwards compatibility which is unfortunate.

I know it's a new device, and I'm glad they are working on improving it so much which is fantastic. Just too bad it impacts our use of the plugin.

My update occurred around ~10:30 EST today based on a peer reset notice from Travis' fine plugin.

http://forum.eyez-on.com/FORUM/viewtopi ... d80f1d12be

Version 1.07 has been released and is now being pushed to all registered users. There are some nice goodies in this release that people have been waiting for, especially the network time updates. This is a first for DSC systems.

There are some changes to the open API (TPI) so if you use this or use a service that uses the open API, please take note. An update to the TPI document is expected shortly from the dev team.

Release Notes:

Additions
- Support for network time updates. Envisalinks will attempt to synchronise with server time and update itself when the panel has lost time completely. Your time zone is determined by your Eyez-On account time zone so make sure it is correct.
- All sockets are closed properly in case of a warm-start. This applies to the local webserver as well as the TPI
- TPI commands 5052 (password timeout), and 5053(login request) have been added. See documentation.
- TPI commnd 912 (Command Output Keypress) has been added. You will now receive a command indicating which Output Command (*71, *72, *73, or *74) was pressed. Useful to typing FOBs to devices.


Bug Fixes
- TPI command 511 has been fixed
- TPI status response pointer corruption has been fixed.

argh double post deleted...

They mentioned yesterday to the developers they'd be making this change. It's a good change. The API is still young, some improvements will break existing stuff. I'd rather they do that than hold back the API. It's a lot easier to do now than it will be in the future when there are many more users.

I'll have a fix out later today.

That's good, glad you think so.

Agreed, new product, them's the risks.. also think it is great as I mentioned they are workin' hard on making it better. I didn't mean to sound negative about the change, I just wanted to let people know who might be more actively using it that it's expected to break if their 2DS gets updated. I'm likely going to use them for monitoring too in the near future - switching from current after the contract's up. I've been impressed with their support and the service itself (along w the 2DS of course).

Thanks for updating it Travis!

Cheers.