MWareman

Found it! Don't worry about posting. Its here: viewtopic.php?p=116049#p116049 Thanks again.

Missed that.... And Tapatalk is apparently not up to finding it at the moment. Can you post a thread link? Let me also take the opportunity to thank you for the programs! I use them throughout my programs. Hopefully, they won't be necessary in 5.x though...

I think it was talked about at one point - but the presence of the workaround pushed it to a low priority - and there are plenty of more pressing changes IMO. I do agree, the programs are a pain to setup. Once going though they work very well.

It sounds like your admin console version does not match your ISY version. Have you clears the Java cache? http://wiki.universal-devices.com/index ... Java_Cache

Take a look at this: http://wiki.universal-devices.com/index ... _Variables Its what I use to do this. Michael.

Thanks! That will make things much better, and is something I'll be able to make great use of. I look forward to it! It will enable some powerful stuff in Tasker, that's for sure.

Here are my initial notes about controlling my garage door with a combination of ISY (via the REST interface and network resources), Tasker and AutoRemote. I know this does not format well - I have it in a word document that I'm working on - but wanted to get it posted for the more adventurous... I have also noted how I switch the ISY URL based on network - so I can avoid SSL delays when I'm on the internal network. I may have the order wrong - YMMV. Sometimes, I have to exit Tasker and re-open it for it to recognise certain things - especially 'Run Task' actions if I recently defined the task. Need: Tasker https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm ($2.99) AutoRemote https://play.google.com/store/apps/details?id=com.joaomgcd.autoremote ($3.99) Note personal URL: http://goo.gl/Q4Iitz (Case Sensitive) Visit the URL and note the API key: XXYYZZ PowerToggles https://play.google.com/store/apps/details?id=com.painless.pc (Free) This sits in the notification tray to allow easy triggering of Tasker tasks On ISY, create a program 'GarageDoor - Operate'. Disable it. Under 'Then' - add your program for your action. In my case - it calls an Elk function. It should probably call the IOLinc for most people... Save Changes, then view the 'Summary' tab. Note the ID of this program (0084 in my case) Create network resource (Get the API key from the goo.gl redirect above): AR - Door - Garage Door - Closed HTTPS GET autoremotejoaomgcd.appspot.com:443 /sendmessage?key=XXYYZZ&message=SETVAR ISYStateGarageDoor 0=:=VAR AR - Door - Garage Door - Open HTTPS GET autoremotejoaomgcd.appspot.com:443 /sendmessage?key=XXYYZZ&message=SETVAR ISYStateGarageDoor 1=:=VAR Test these – make sure AutoRemote shows the toasts on RX Create a program to run the ‘AR - Door - Garage Door – Open’ network resource when the door opens – and ‘AR - Door - Garage Door – Closed’ when the door closes. Test. Make sure the toasts from AutoRemote are coming up on your phone when the door opens and closes. Make sure that when you ‘RunThen’ the ‘GarageDoor - Operate' program the door operates. Create the following Tasker variables: %IsyUrlInternal URL for the ISY internal to home network (http://user:password@192.168.1.3) %IsyUrlExternal URL for the ISY external to home network (https://user:password@host.dyndns.org) %IsyUrl Blank, initially Create Tasker Scene Activate Garage Door Contains a ‘Are you Sure’ text box, ‘Activate Door’ button (btnYes), ‘Cancel’ button (btnCancel) and a test box for status (txtStatus). btnCancel / Tap Destroy Scene / ‘Activate Door’ btnYes / Tap Perform Task / ISY-RunThen %par1=0084 Destroy Scene / ‘Activate Door’ Create tasks: Home-Arrive 'Variables' 'Variable Set' '%IsyUrl' to 'IsyUrlInternal' Home-Leave 'Variables' 'Variable Set' '%IsyUrl' to 'IsyUrlExternal' ISY-RunThen 'Net' 'HTTP Get' / Server:Port = '%IsyUrl' / Path = '/rest/programs/%par1/runThen 'Trust Any Certificate' may be necessary if you are self signed. I strongly recommend you get and install a real SSL certificate that is trusted by your devices though. http://www.ssls.com/ has them for $4.99/year. AutoRemote-SetVar If %arpar1 ~ SETVAR Variable Set %%arpar2 to %arcomm End If LaunchScene-GarageDoor Show Scene 'Activate Garage Door' 'Activity, Full window' 'Continue Immediately' Scene – Set Element Text – txtStatus ‘Closed’ if %ISYStateGarageDoor=0 Scene – Set Element Text – txtStatus ‘Open’ if %ISYStateGarageDoor>0 Notify-GarageDoor-Opened Popup Title ‘Garage’ Text ‘Opened’ Timeout 5 Show Over Keyguard Notify-GarageDoor-Closed Popup Title ‘Garage’ Text ‘Closed’ Timeout 5 Show Over Keyguard Create Tasker Profiles: At-Home 'State' 'Net' 'Wifi Connected' Select the SSID and MACs for your home network Select 'Home-Arrive' for the entry task Select 'Home-Leave' for the exit task AutoRemote-Set-Var AutoRemote / Event Behaviour / Message filter 'SETVAR' Entry Task: AutoRemote-SetVar Notify-GarageDoor State Variable Value %ISYStateGarageDoor = 1 Entry: Notify-GarageDoor-Opened Exit: Notify-GarageDoor-closed Power Toggles Add Notification Icon Custom / Tasker Toggle / LaunchScene-GarageDoor Give it an icon… Using Use, Pull notification down. Click the power toggle icon. Tasker should launch the scene ‘Activate Garage Door’ – then read the variable %ISYStateGarageDoor to set the status text to either ‘Open’ or ‘Closed’ on the scene. If you click ‘Cancel’ – Tasker will destroy the scene. If you click ‘Activate Door’ – Tasker calls the task ‘ISY-RunThen’ with the parameter of the program ID. ‘ISY-RunThen’ runs the ISY program via the REST API. ISY notices that the door has opened – and calls the network resource letting Tasker know. Tasker receives the notice – and updates the status variable %ISYStateGarageDoor. Then it pops up a notification to let you know... I have a second power toggle initiated Tasker scene with about 20 toggle buttons on it - each with updated with the status of a device. Clicking the toggle calls the scene associated with the device. It all works fairly well - I get zwave lock status, can initate a 'Lock' or 'Unlock' event, see status of lights, turn scenes on and off etc..

I'll see if I can write up my garage door solution first. A single function widget I think will be an easy place to get the concept across - and it was my own starting point. After the first was working, I found myself spending hours of 'oh, and this.... And this....' Etc. Suddenly It is 2qm again...

I building my Android control of ISY around Tasker, AutoRemote (to allow ISY to adjust Tasker variables in response to device state changes), PowerToggles (to launch Tasker scenes) and Pushover (for ISY to User notifications). Its working great so far - using nothing more than the REST API. I use Tasker Scenes to present a UI. For instance, I have a 'Door' button on my notification pull down. If I click it, I get a scene show asking 'Sure you want to operate the door?' With a large 'No' and a small 'Yes' button. Pressing 'Yes' calls my ISY program to operate the door. Open and close events are sent by Pushover (to alert me) and AutoRemote to update a Tasker variable, and that variable is used to show door state in another scene - without having to poll. I provide a 'Refresh' button that calls an ISY program to cycle thru all the status programs, to re-push all status. Its great that state of devices gets pushed with AutoRemote to variables, so widgets show status immediately without have to do polling or subscriptions. The thing that will *really* supercharge this is variable substitution in network resources. That way instead of device state in Tasker being 'On' or 'Off', I'll be able to send the actual value. I'll be able to display thermostat settings etc etc. Just cannot do that now without hundreds of rules, or externalizing ISY->AutoRemote. Some day (hopefully), I'll write it up.... I was rather hoping for the network module / variable enhancements first.

Assuming you can find stuff that still works with the 3.x firmware that the ISY99i is capped at. Many newer devices won't work with the older firmware.

Yes, I have an ISY99i. Currently, I only use Insteon products and new to this. I don't know how I woiuld program the Vivinit ZWave items. They also still talk to the security thing on the wall, but that is not activated with the alarm company. As far as I know, the ISY99i cannot be extended to do z-wave. You'll need to upgrade to a ISY994i and then add the z-wave module. That might get quite expensive for something you don't know will work afterwards though.

...assuming of course it is a dual band PLM. I believe that you can still buy single band ones, and they won't be able to work with wireless sensors without at least one other dual band device, like an access point.

I'm at a brick wall, until there is new Foscam firmware, when I will test again..

To run the dashboard, try this link if you are running 4.2.3: http://isy.universal-devices.com/994i/4 ... board.jnlp

Make sure you are using the Dashboard (correct version for your running code version) to manage certificates - not the admin console or the http interface.

Was the certificate on your lighttpd HTTPS server issued by a well known (paid) CA like Thawte or Verisign? If not, your probably running into a certificate trust issue. You can relax the SSL client settings in ISY Dashboard, but it would be better to have a SSL cert on your Lighttpd server that's trusted by ISY. Either that, or exempt your ISY from the SSL redirect....

You should be aware that trusting any certificate gives you a false sense of security. It leaves you just as potentiality vulnerable as if you have no certificate at all. Any intermediate provider can intercept your connection and recover you credentials without you knowing. Michael.

Glad I could help! Michael.

You may be running into a couple of things. First - SSL trust. Is it a trusted cert. If not - you'll need -k to ignore that - but it's not *that* secure to do that. Second - with curl you don't put the username and password on the URL. You specify the -u parameter. Try it from the shell on your Asterisk system first: curl -k -s -u user:pass https://test.dyndns.biz:1234/rest/vars/set/2/88/1 If this works, I included it in my dialplan like this: exten => s,n,system(curl -k -s -u user:pass https://test.dyndns.biz:1234/rest/vars/set/2/88/1) I'm not using the curl Asterisk command. Not sure why (it way a while ago!) Michael.

May be even simpler than that if this is true.. http://gizmodo.com/report-apples-home-a ... 1583413379

I do this with an earlier version of Asterisk, by incorporating calling curl into my dialplan IVR menus. Works well. I think the URL you mention is the other way around, having Asterisk provide a REST api for things like call placement, queue management etc.

You'll have an IP hat can talk to the ISY, but not your (new) router.

I'm sorry not sure what this means. I'm new at all this and knowledge is limited. I was able to do it for my ELK M1 but I'm nit sure what you are referring to. Hope you can break it down for me please I'll try. I don't know specifics on your addressing (other than what was posted above) - or the specific operating system in use (assuming windows - but exact procedure and terminology varies with edition). I'll try to keep it generic... Your PC is probably getting an IP address from your new DHCP service (running on your new router) that is giving it an IP address that cannot connect to your ISY (which has a static address on your old network). You need to (temporarily) change your PC away from DHCP and, instead, assign it a static IP address in the range of your old network. So, let's say your old router was 192.168.0.1 and you set ISY to 192.168.0.2 - you should (temporarily) change your PC from 'Automatic' to use something like 192.168.0.3 (just make sure it does not conflict). For the 'Subnet Mask' put '255.255.255.0'. Do not worry about the 'Default Gateway' or 'DNS servers' for the temporary step. Your PC will lose access to the Internet during this temporary step. Now - connect to the ISY with your browser on it's IP address and change it's IP from (in my example) 192.168.0.2 to 192.168.1.2 - and the 'Default Gateway' to '192.168.1.1' from '192.168.0.1'. You will likely need to change the DNS address as well. When you save, ISY will reboot and you wont be able to access it again. Please ensure you map the made-up addresses I gave here to your actual situation! Then - simply change your PC back to 'Obtain address automatically' again - and you should be up and running again on the new subnet.

In that case, simply add a hard address in your old IP range to your PC, access the ISY and change it to work for your new subnet range, finally removing the had address on your PC.

If ISY is DHCP, power cycle it (so it's forced to renew, and get a new IP from your new router) and look at the DHCP logs on your router to see the IP that was assigned.