MWareman

Michel, Just a suggestion, but could you consider renaming 'Enable Internet Access' to something like 'Try upnp port mapping' and 'Disable Internet Access' to something like 'Disable upnp' to better represent the function the option does. Another thought is to suppress the option altogether if the ISY does not receive upnp Nat device broadcasts. Maybe you will get fewer questions on this? Michael.

Nice! That's some great info. Thanks!

My thought is you should ping Starthome about that. ISY994 compatible maybe, but saying ISY is misleading in my opinion - for those that have the 99. Either way, its not UDI's issue - they have been very open about this. My $0.02. As LeeG said, all devices have an end of life. Either RMA it to Smarthome on their mis-description, or buy a 994i for support of the latest devices.

Awesome! Sounds like just the ticket. Thanks!

Just cycling back to this thread. Michel - is it possible to confirm if this functionality is included in the current work on variable enhancement? Thanks! Michael.

I just downloaded the class 1 root ca cert from cacert.org and emailed it to myself on the android device. When you open the attachment, it asked about installing the new root certificate. Once done, any certificate issued by cacert.org will be trusted. So, sign up and get a cert issued in response to a csr. It's free - and you'll end up with a more secure solution that using a self signed certificate. I posed fuller details of this in another thread - if I can find it i'll link it here. Michael. Edit: Here you go. http://forum.universal-devices.com/viewtopic.php?t=12074#p93012

Since Android 4.2-ish - I've had success calling the ISY REST interface directly from Tasker (adding a custom root certificate on Android was the blocker before). My creativity is now unleashed! And yes - autovoice adds a massive dose of coolness to the solution.

That's not how I understand the sense to work on this module, but I'm probably wrong. I don't have one yet. Does a change in the sense wire TOGGLE the output (the way I hope it works) - or does the output follow the state of the sense wire (and controlling via insteon essentially let's the two get out of sync with each other - necessitating the double switch)? If the latter, I guess I won't be buying any. Michael.

You are welcome! Any time I can (hopefully) help. I will add is that user administered certificate support is still very new to android - and many apps are still doing things the old way. As apps get updated, more and more will be able to take advantage of the new APIs and work with the new certificate stores. I do think that Tasker with ISY is a killer feature now that I can all the REST API over SSL. Adding autovoice and autolocation to Tasker - well lets just say I can now talk to my ISY and have it do stuff - based on where I am.

What version of Android? It matters, because all versions before 4.2 (I think) did not share the root cert store between processes - each client had to implement its own list - and there was no way to import your own root cents and have them be trusted. 4.2 and later provides the ability to import user supplied root certificates into the root store - and this is now used by (some) applications - mainly the browser, email and vpn clients. If your device is older than that, you cannot import new root certs into the OS without rooting your phone. Unfortunately, Tasker does not seem to be one of the applications that uses the new root store anyway, so it cannot seem to use any new roots you import.

On your machine, go into your nic properties, and add a second IP address on the old 192.168.0.x subnet. You'll then be able to access it. (Assuming you are running windows that is). Once changed, remove the secondary address from your machine.

Wow... No thanks. They should be giving the device away in return for that monthly fee along with a 2 year commitment. Sounds like they are going to keep the API private to keep everyone from avoiding paying their fee.

JimsEvilTwin, Just for completeness, have you seen this thread? viewtopic.php?t=12029

There are others, but Mobilinc is (in my opinion) by far the most polished product. Mobilinc Connect is entirely optional - you can do port forwarding and connect directly. Make sure to use SSL to protect the credentials. MobiLinc allows you to create home screen widgets that trigger devices, scenes or programs as well. Also consider adding Tasker for phone-end intelligence - Mobilinc integrates very well with it. For instance, if i'm at home, it's after 10pm, and my phone is powered from a charger - my overnight scene is triggered automatically - making sure my doors are locked, alarm is armed and the lights are out. If I leave the house, the geofence tells my ISY to start sending notifications. At home, the notifications are suppressed. It's very convenient.

Just for completeness - I set my ISY to do a notification via Pushover whenever a heartbeat is detected from one of these devices. It appears almost exactly every 23 hours and 50 minutes. It is only sent once - so (I would guess) could be missed. I think I will do my heartbeat alert as this: If Control 'Basement / Basement Sump - Heartbeat' is switched On Or Control 'Basement / Basement Sump - Heartbeat' is switched Off Then Wait 48 hours Resource 'Pushover - Sump Leak - Heartbeat Fail' Else - No Actions - (To add one, press 'Action') That way - a single missed heartbeat is tolerated - but two being missed will be reported (I should expect to get two within 47 hours 40 mins). Thanks again for all the guidance! Very much appreciated.

Please make sure you are using the dashboard - not the admin console. The URL I placed on the wiki is probably for the latest version of firmware. You posted that you have a 99i - so you cannot have the latest version (since 4.x won't work there). You will need to use a specific URL for the dashboard for your version. You didn't say what version you are running - but according to a document on UDIs site you can use http://isy.universal-devices.com/99i/3. ... board.jnlp - where 3.3.10 is the firmware version. Replace for whatever version you are currently running. You should be able to find the settings described in the wiki then to change the crypto settings for the SSL client to support pushovers server. Michael.

Awesome! Thanks Lee. That perfectly explains what is going on, and I can now put this into a program as you suggested. Do we wiki-ize the peculiar devices?

Sounds good! Thanks Lee and Michel for the info. Extremely helpful as always! I never really though of 'Control On OR Control Off' - but it does make sense for, in effect, 'any change'. I'm a little confused with Michel's affirmation of my initial thought of the heartbeat though. Does the heartbeat status only change if the heartbeat is missed for 24 hours (as I initially thought) - or does the heartbeat flip-flop on/off with each 'pulse' from the sensor? Or is it something else - like a change to Off followed by a change to On each 'ping'? If the status only changes if something bad has happened due to a missed heartbeat - I would not want the program on the ISY to have to wait another 25 hours before alerting. Hence my question. There appears to be a bit of a lack of documentation for this device out there.

Hi Michel, Just bought 2 leak sensors - sorry to post to this thread again but one question is unanswered, and I need to know the answer as I setup my program: In your scenario where the leak happened during an outage of the ISY - the status will not be known by the ISY. In this state - if the leak sensor triggers a leak again - will the ISY know right away (I suspect this is the case)? Or will it have to wait for the heartbeat before leaks will be detected? As secondary question I have - the 'heartbeat' node has a status 'On'. How would I utilize this? Does the ISY status change to 'Off' if the heartbeat is not received in 24 hours? Or do I have to trigger a program on 'Off' and wait 24 hours to see if it changes back to 'On' - and sent a notification if not? Thanks! Michael.

Because when your program turns off the hot water (then condition step 1), it no longer satisfies your run condition (hot water status becomes 'Off') - so the program aborts without ever getting to step 3. You need 2 programs. One with your action and no condition - your then clause in the conditional program would simply run the then clause of your second 'action' program. That way - the wait won't get aborted once the heater turns off at 1am. Michael.

Even if the ISP does block port 80 and port 443 you could just change the setting in the ISY to use a different port number. Is there another way how an ISP can block you from running a server? Sent from my SPH-D710 using Tapatalk 2 Yes - but it does not happen very often. Two possible ways in fact. They can block any TCP packet heading to your router with 'SYN' set and 'ACK' not set. It would stop your server from working no matter what port it was listening on (breaks the 3 way TCP handshake - only in one direction). The other way is if your ISP does not give you a real IP - and NATs you to the Internet. This is starting to happen more and more now that the IPv4 pool is nearing exhaustion.

Such as with a keypad button (which, I submit, is the most common of "clients"). Perhaps, someday, we can have a means to easily duplicate a configurable keypad function on a tablet, and use them in place of a keypadlinc. In my mind, we are not quite there yet. Ahh - I don't do that.

It matters to me, where I use scenes to control status displays, and prefer "ON" to indicate open. I almost exclusively use MobiLinc - and I can override 'On' to actually say 'Open' or 'Closed' as necessary. My irrigation does not actually say 'On' - rather 'Running' or 'Off' on each zone. I guess if you cannot arbitrarily rename the status on your chosen client it does matter thou.

Arguably not - at least entirely. If this were completely true, the result of the query would also be reversed. Changing the magnetic switch from NC to NO does both. I do agree with you though - it's not a bug. I think it was a design flaw that nobody noticed until there was critical mass of deployed devices, and which point the 'if we fix this we break everybody's implementation' became a valid argument. At the end of the day though, does it *really* matter if 'ON' = 'OPEN' or 'ON' = 'CLOSED' as long as it's always the same? Trigger reverse breakers this. Just disable it, and reverse the program logic. To me, that's the easiest solution.

Yes, it works with the 994 (that's what I use it with) and on cellular and external you need to do one of 2 things: 1) Configure your NAT router at home to port forward he SSL port to your ISY (only works if your ISP does not block you from running a 'server' at home, as some do) Or 2) Subscribe to MobiLinc Connect