az1324

Why not just put a keyfob by your bed and disarm the alarm when you get up?

Thu 01/31/2013 01:51:54 AM : [iNST-SRX ] 02 50 21.22.23 00.00.02 C7 11 02 LTONRR (02) Thu 01/31/2013 01:51:54 AM : [std-Group ] 21.22.23-->Group=2, Max Hops=3, Hops Left=1 Thu 01/31/2013 01:51:54 AM : [ 21 22 23 2] DON 2 Thu 01/31/2013 01:51:54 AM : [ 21 22 23 2] ST 255 Thu 01/31/2013 01:51:55 AM : [iNST-SRX ] 02 50 21.22.23 00.00.02 C7 11 02 LTONRR (02) Thu 01/31/2013 01:51:55 AM : [std-Group ] 21.22.23-->Group=2, Max Hops=3, Hops Left=1 Thu 01/31/2013 01:51:55 AM : [iNST-DUP ] Previous message ignored. Thu 01/31/2013 01:51:56 AM : [iNST-SRX ] 02 50 21.22.23 11.00.02 C3 06 00 (00) Thu 01/31/2013 01:51:56 AM : [std-Group ] 21.22.23-->11.00.02, Max Hops=3, Hops Left=0 Thu 01/31/2013 01:51:57 AM : [iNST-SRX ] 02 50 21.22.23 11.00.02 C7 06 00 (00) Thu 01/31/2013 01:51:57 AM : [std-Group ] 21.22.23-->11.00.02, Max Hops=3, Hops Left=1 Thu 01/31/2013 01:51:57 AM : [iNST-DUP ] Previous message ignored. Thu 01/31/2013 01:52:10 AM : [iNST-SRX ] 02 50 21.22.23 00.00.04 C7 11 04 LTONRR (04) Thu 01/31/2013 01:52:10 AM : [std-Group ] 21.22.23-->Group=4, Max Hops=3, Hops Left=1 Thu 01/31/2013 01:52:10 AM : [ 21 22 23 4] DON 4 Thu 01/31/2013 01:52:11 AM : [iNST-SRX ] 02 50 21.22.23 00.00.04 C3 11 04 LTONRR (04) Thu 01/31/2013 01:52:11 AM : [std-Group ] 21.22.23-->Group=4, Max Hops=3, Hops Left=0 Thu 01/31/2013 01:52:11 AM : [iNST-DUP ] Previous message ignored. Thu 01/31/2013 01:52:11 AM : [iNST-SRX ] 02 50 21.22.23 11.00.04 C7 06 00 (00) Thu 01/31/2013 01:52:11 AM : [std-Group ] 21.22.23-->11.00.04, Max Hops=3, Hops Left=1 Thu 01/31/2013 01:52:12 AM : [iNST-SRX ] 02 50 21.22.23 11.00.04 C7 06 00 (00) Thu 01/31/2013 01:52:12 AM : [std-Group ] 21.22.23-->11.00.04, Max Hops=3, Hops Left=1 Thu 01/31/2013 01:52:12 AM : [iNST-DUP ] Previous message ignored. The dev doc must have a typo (x3) since if you note it specifies ALL the messages are broadcast when in fact they are ALL group broadcast (flag is set). But then there are no cleanup messages so they are kind of a hybrid I guess. Plus it makes sense to only send the heartbeat messages if someone has subscribed to them. As far as saving a link, don't know what to tell you.

As long as it is wet, it will send wet messages every 15 seconds. Wouldn't you rather it keep trying to notify you of a problem than conserve its battery? If your small leak dries but then turns into a big leak then it will start notifying you again (you've already been notified about the small leak). So I don't really see a problem here.

Yes low battery would probably not be that useful, but would not have taken much effort to do it anyway. The heartbeat is more useful in that RF signal path changes over time are also a problem and regular monitored communication helps prevent a situation where the sensor needs to notify of a leak and the RF signal can't get through. Using the heartbeat as the dead battery notification, worst case the sensor battery is dead for 24hours before you know about it.

Ok heartbeat came in at pretty much exactly 24hrs since the last heartbeat. This is even though there were other group 1&2 messages more recently than that. So spacing is 24hrs from last group 4 message. Why have you never seen them? You didn't write the group 4 link. If the leak sensor has no group 4 links in its database it is not going to send any group 4 messages. Which is fine since why would it waste its battery sending if nobody is listening? So a simple fix for you.

If what you posted is the way it is currently processed then it should already support the heartbeat as it would either cause a DRY ON or WET ON event. Then simply ensuring one of those occurs every 24h would be fine for heartbeat detection and no additional nodes would be required. However I did not see any group 4 events in the event viewer when pushing the set button until I changed the device to remotelinc so maybe the group 4 link is not written?

When wet, it will send the group 2 on message every 15 seconds. I don't know if this continues forever as I didn't leave it running for very long. When going from wet to dry, it will send the group 1 on message once. When pushing the set button, it will send the group 1 or 2 message depending on state and then 15 seconds later will send the group 4 message. I will let you know what the behavior is when it is undisturbed for 24hrs+, but I expect the group 4 message will come in. I don't see why specifying that a leak sensor has a group 4 node would change the codebase. The way I'm doing these tests is just adding the leak sensor as a remotelinc 2 4 scene and it works fine to trigger my program below: If Time is Last Run Time for 'Leak Sensor Monitor' + 36 hours Or ( Control 'Leak Sensor - D' is not switched On And Control 'Leak Sensor - D' is not switched Off ) Then Send Notification to 'Me' content 'Program Details' Else - No Actions - (To add one, press 'Action') Obviously group 1 (A) doesn't turn off when group 2 ( turns on or vice versa but I don't think that is important since they will still trigger programs. I'll just keep running it as a remotelinc 2 until it is fully supported. This is how I did notifications: Leak Sensor Wet If Control 'Leak Sensor - B' is switched On Or Control 'Leak Sensor - D' is switched Off Then Send Notification to 'Me' content 'Program Details' Disable Program 'Leak Sensor Wet' Else - No Actions - (To add one, press 'Action') If Time is Last Run Time for 'Leak Sensor Wet' + 15 minutes Then Enable Program 'Leak Sensor Wet' Else - No Actions - (To add one, press 'Action')

How about add group 4 as another node "Heartbeat" and use the following program If ( Control 'Leak Sensor-Heartbeat' is not switched On And Control 'Leak Sensor-Heartbeat' is not switched Off ) Or Time is Last Run Time for 'Leak Sensor Monitor' + 36 hours Then Send Notification to 'Me' content 'Leak Sensor Error' Else - No Actions - (To add one, press 'Action')

Is there supposed to be a low battery node for these? Also, mine does send the dry notification automatically, no button push required. Wet node is on when the sensor is wet, dry node is on when the sensor is dry.

I mostly graph them in a spreadsheet program. I didn't look into what the differences in the type value are for the different models so it only matches on 5.3.145.0 right now.

I wanted to log the temperature readings from my Insteon thermostats so I made this program (Windows .NET). It logs the temperature every 1 minute for all thermostats to a csv file for easy graphing. Can't say for sure if it will work with all the Venstar models. http://www.sendspace.com/file/v4w4c0

I don't think there is any such temperature sensor device. You could use a cheap thermostat, temperature monitor/controller or "temp alert" device hooked up to an I/O Linc. Then you would know whether the temp is above/below the setpoint but not the exact value. This is unfortunately going to be more expensive and more inconvenient than just being able to pull the temperature reading from an Energy Display. But at least you would have local control of the setpoint in the basement. You could also use an EZIO 6I with the analog input and a thermistor but I don't know if this is supported by ISY and it's even more expensive. So I think the best bet is to beg for the Energy Display to be supported for temp readings.

I have an IP camera at my front door. I also have the doorbell connected to an Insteon EZIO input. So it would be nice to trigger the IP camera to display in the browser when I am at the computer and the doorbell rings. I made a small app for this but it could also be done with EventGhost which would allow multiple events and lots more options. This requires a network resource which will send a UDP packet to your PC's IP address with the text "trigger". The port is configurable. Then the PC will execute whatever action is in the Run box such as the web address of my IP camera which will open in the default browser. This is a Windows .NET application. http://www.mediafire.com/?lujzrz3yoay

Ah ok that works too with the C Escaped method. Good to know. The setup requires Asterisk with the manager interface enabled. Don't really want to get into all the Asterisk stuff as there are other forums for that. As far as the ISY side goes for ringing the phones, the TCP (C Escaped) command is: Action: login\r Username: asterisk\r Secret: password\r Events: off\r \r Action: Originate\r Channel: SIP/extension\r Context: doorbell\r Priority: 1\r Callerid: \r Timeout: 10000\r Async: 1\r \r Context doorbell is a simple dialplan that will just say "Door" if the phone is answered.

Recently I've been playing around a little with Asterisk and it was pretty easy to control ISY over the phone using a voice touch tone menu in the dialplan and some wget commands to talk to the ISY REST interface. I also wanted to have ISY be able to control Asterisk so that the phone can be used as an alert interface. For example, when the doorbell rings, an Insteon contact closure input triggers an ISY program which calls a network resource. It is configured to connect to the asterisk manager TCP interface on port 5038 and send commands causing Asterisk to ring the phones for 10 seconds and display the caller id name "Doorbell". This is useful because it is hard to hear the doorbell in parts of the house (or yard/garage) but there are always cordless phones within earshot and they can be taken outside. Also the callerid log on the phones keeps track of when the doorbell rang. The one issue I had was that the Asterisk API requires CRLF line terminations. So I had to use the TCP binary mode and write a little program to convert the text to the required format of decimal numbers with semicolons. But everything works and when someone rings the doorbell the phone rings. Many other things are possible but I just wanted to share a simple and yet useful example.

Works now! Thanks. Makes a big difference.

Hey Michael. My system has been down for many months for various reasons and just got it up and running again the other day. I have a user agent for iphone browser in my firefox and I do not and have not ever gotten the meta tag in the source for the pages (now on firmware 2.6.. I guess this is a problem with user agent detection? I have however confirmed that if I add to the header of the html pages (no other changes) and serve to the phone from a test server that it zooms perfectly on the browser. Since more mobile browsers are starting to read viewport tags a better way to implement this is Please also note that internal quotes are necessary and not sure where the tag brackets are in your code, but regardless nothing shows up in the source. Seems like you would just want to include this in the header always because browsers that don't use the tag will ignore it and browsers that do will zoom properly using the device-width parameter. Thanks.

Thanks, it works. Is there a way to adjust the zoom. It zooms to much now. A simple viewport tag would fix the zooming issue and has been suggested for months.

Anyone can confirm this? No change in mobile safari page rendering and no sign of viewport in HTML code.

- Added viewport, format-detection meta tags to HTML Don't see them!

Excellent! Thanks for letting me know.

Yeah I know its planned but I just wanted to bring up the possibility of something easier to implement that could be pushed out as a stopgap solution before the full notifications 2.0 implementation.

An easier intermediate fix might be to send all the conditions in the if (of the program containing the notification command) that evaluate to true. Although I am not sure when I would need to be notified that a "schedule has been met" so its usefulness is in question. In that case if I had a program such as: If Status 'Double Garage Status' is Off Or Status 'Single Garage Status' is Off Or Control 'Doorbell' is switched On Then Send Notification to All Else - No Actions - (To add one, press 'Action') and even if both doors were off then I would get a notification that said "Status 'Double Garage Status' is Off; Status 'Single Garage Status' is Off" because both conditions evaluated to true and the text is already there and formatted to be readable unlike the way notifications are currently worded. Alternatively the option to send user defined text would also be a good intermediate fix even if there was no "templated" way to pull dynamic information out of the event. One could just have separate programs the way I attempted to do originally. As a side note, something else that I wish I was able to do is to be able to alias the status of the garage devices to 'Open' and 'Closed' in stead of 'On' and 'Off' which I'm sure would come in handy for other situations. I think it also might be nice to have automatic nightly builds available and a formal bug tracking system.

If Time is Last Run Time for 'Away' + 10 minutes Or Time is Last Run Time for 'Security Check' + 10 minutes Then Run Program 'Check Double Garage' (If) Run Program 'Check Single Garage' (If) Else - No Actions - (To add one, press 'Action') If Status 'Double Garage Status' is Off Then Send Notification to All Else - No Actions - (To add one, press 'Action') From these programs the notification I get is "Sched has changed to Met." instead of the Status. I thought by breaking it up into invidividual programs like this I would be able to get the status in the notification. Is there a way to get the correct notification?

Hmm interesting they will allow web apps to use multitouch in the future. Disclaimer: I by no means am a web design expert and I just threw that little example together so it might not be the ideal way to do it. There are a few design issues that must be taken into consideration before deciding how best to format the default html. For example will the page be meant to work with browsers that don't support javascript? Is the css meant to remain valid and functional in this case? But in the example above the id would be found by referencing the desired "address" element based on the clicked "button" element and extracting its innerhtml in javascript. Also if a skin wants to display the device address it can. Obviously this requires javascript and another decision would be how to assign the onclick behavior to the buttons. Dynamically on page load or just reference a default click handler function and pass self? If there's a good base html output available it should not be hard to implement user-selected skins by just uploading a folder with a css file, images, and a js file in it. Then in the admin console one could simply choose a skin name and the html would reference its css and js file in that location.