MWareman

Belias, I want to add to the chorus of thanks. I had a very basic program running the mostly worked, but given the importance of this I wanted something more reliable. I now have my 2 sensors under your programs control, and took advantage of the Costco deal to get 4 more. Most of my potential leak locations will soon be monitored. Thanks again. Michael.

That's a great deal. Thanks!

My issue is I want dimmable, and 3700k-ish. I cannot seem to find that available. (Or rather 'my wife demands' would be more accurate..)

No - or at least not yet. Rumor is once the Z-Wave changes are stabilized that this is the next feature in the pipeline.

My first thought is to check that you have the timezone of the ISY set correctly. For instance, if it is set to Pacific time and you are in the Midwest, I would expect the variables to reset at 10pm local time. Second thing to check is any programs that issue an 'Irrigation Reset' command. That command will also reset the numbers. Michael.

Can't really answer the main question satisfactorily (assuming browser interface is in use, you cannot remember the password with that). However, MobiLinc ($$) allows you to store your credential so you don't have to enter it each to time. Awesome app as well...

Sorry to hear that Michel - that is never pleasant. I hope you reach 100% soon! Michael.

Sorry to revive an old thread - but just got my smoke bridge and 4 new First alert Onelink alarms (two with CO - two fire only). This is what I did. I linked each alarm to each other. The last one I linked to the smoke bridge. So far - so good. On ISY - using 4.0.4 with the 4.0.11 UI I tried adding the device by it's ID. I got 'Unknown engine'. I clicked 'Start Linking' and pressed the button on the smoke bridge until the double-beep. This time - it linked to the ISY fine (although I got a comm error for some reason). I right-clicked the main node - and 'Write updates to device'. This brought the smoke bridge online - so to speak. Now - I got 7 nodes: NODE-Smoke NODE-CO NODE-Test NODE-Unknown Message NODE-Clear NODE-Low Bat NODE-Malfunction (Other reports I've seen indicate 3... not sure why I have 7. The smoke bridge is reporting v43). I have not had time to experiment with all of the conditions and triggers here - plus the wife is (already) getting annoyed at the loud testing. Does anyone have any good details of: Can I trigger a 'fire' signal on a connected and monitored Elk M1? (I have the Elk module) This is only for when the house is unattended (alarm is in 'Armed Away' mode) so I don't have to rely on a neighbours to call in case there is smoke when we are not home. What is 'Clear' about? Should I setup a state variable for 'Smoke Detected' - has 'NODE-Smoke' going on turn the state to '1'. Then have a program to wait for 'NODE-Clear' to change the state to '0'? I have heard that 'Smoke' and 'CO' issues a 'Off' for a clear - but 'Test' does not. Just trying to figure out how they all interact without driving everyone nuts with many, many loud tests.. I notice there is no write up on the wiki. I'm happy to collect information and write something up. Thanks for any info you have! Michael.

Personally, after 2 replacements of the 2441TH, I gave up, got a Trane Z-Wave device that has functioned perfectly, via a Vera until ISY has Z-Wave. It has functioned perfectly ever since. Personally, Smarthomes attitude to this problem has caused me to always buy a Z-Wave device before an Insteon device if available. If someone from Smarthome wants to have me try a fourth device, I'm happy to try and report. It will restore my faith. Why is it its only the 2441TH that has difficulty, where no other stat has caused problems on my furnace.

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.