Michel Kohanim Posted February 21, 2013 Author Posted February 21, 2013 Hi all, we'll try to have another release as soon as possible. Xathros, can you check the Program Summary tab and see the last runtime/finish time for this program? With kind regards, Michel Quote
TJF1960 Posted February 21, 2013 Posted February 21, 2013 Hi Xathros, I ran into this a few months back. If you manually query a device it will trigger a program then/else. But the nightly queries do not. Nor do device queries via a program. Tim Quote
Xathros Posted February 21, 2013 Posted February 21, 2013 Xathros, can you check the Program Summary tab and see the last runtime/finish time for this program? Yep. Last run/finish are same as the last time I queried the IOLinc sensor node. for the one I'm playing with. For the other door, it was time the door was closed this morning until I queried it just now. Hi Xathros, I ran into this a few months back. If you manually query a device it will trigger a program then/else. But the nightly queries do not. Nor do device queries via a program. Tim I think I've run into this before too and just never took the time to research exactly what was happening. So it's quite possible it's behaved this way all along and I'm just now noticing. I don't have a 3am query set up so I can't say if that would trigger my notifications or not. Michel- Is this the intended behavior? Everything I've learned here so far would seem to indicate not. Shouldn't the status have to change to trigger that condition? -Xathros Quote
Michel Kohanim Posted February 21, 2013 Author Posted February 21, 2013 Hi Xathros, Thank you. No, this is not the intended behavior. BugID #56. With kind regards, Michel Quote
andyf0 Posted February 21, 2013 Posted February 21, 2013 Is there a sexier looking version of the Admin Console coming out soon? I just changed the way I bring it up and can now bring up what looks like a new display style with buttons rather than tabs. I can duplicate this fairly easily. The Programs button doesn't work but the others seem to. See below. Quote
johnnyt Posted February 22, 2013 Posted February 22, 2013 Hi Xathros, Thank you. No, this is not the intended behavior. BugID #56. With kind regards, Michel Been seeing this happening for a long time. Thought it was a "feature" and didn't like it but didn't post about it. I have a bunch of notification programs I use for troubleshooting io linc program behaviour (and iolinc h/w behaviour problems) in the absence of more sophisticated built in program logging. They end up taking up a lot of my inbox whenever I enable them because I query my 9 hvac related iolincs every time there's a change in heat, ac or fan call (triggered by sensor or the X10 I also programmed the io linc to send) and at regular intervals as a fail safe. (Unfortunately the sensor doesn't always tell isy it has changed state - or at least didn't always a while back when I set it up) Anyway, notifications get sent even though status didn't change. Until there's better built in program logging, these notification programs are actually something I'd like to be able to leave on to catch problems early but it just causes too many unneeded emails right now. Too bad I didn't post about this issue when I noticed it moons ago, but glad to see it's something that will be fixed. It is making me think I should check on why the sensor trigger isn't working sometimes even when comm is a healthy 3 hops / 2 left in case it's a bug too... although that's probably not an isy bug if it is one?... Sent from my iPod touch using Tapatalk Quote
TJF1960 Posted February 22, 2013 Posted February 22, 2013 johnnyt, This bug only occurs when you manually query a device not when the query is part of a program. Quote
Michel Kohanim Posted February 22, 2013 Author Posted February 22, 2013 Hi andyf0, We have not changed the UI at all except for the themes. Xathros, Tim, and johnnyt, I am so very sorry: when you do a query from Admin Console (force a query), ISY clears all previous states and then queries the devices. So, this is consistent with what you see: the programs will indeed get evaluated again (the state changes from NOTHING to something). On the other hand, queries done through programs do NOT clear the state. So, my question to johnnyt is whether or not - and as Tim suggested - you have this problem with programs and not just Query from Admin Console. Tim, thanks SO very much for the pointer. Xathros, I will have to close this ticket and again so very sorry for wrong information. With kind regards, Michel Quote
Xathros Posted February 22, 2013 Posted February 22, 2013 Xathros, I will have to close this ticket and again so very sorry for wrong information. No Problem and I have confirmed that when the IOLinc is queried via program the false trigger does NOT occur. -Xathros Quote
swnewman Posted February 23, 2013 Posted February 23, 2013 I just upgraded to 4.0.1 and I'm noticing something odd. Not sure if it is related, but now I have two dimmers that are blinking their LEDs with the Insteon traffic. These two devices are slaves on the same 4-way circuit, but any traffic on the network causes the blinking. Haven't noticed if there are others. Anybody know what's going on? Quote
LeeG Posted February 23, 2013 Posted February 23, 2013 swnewman What is the firmware level of the two SwitchLincs? Some devices have a feature that blinks the LED when it detects Insteon traffic. The ISY has no logic to control such a feature. Will do some research once I know the firmware level. Factory reset may eliminate but not sure about that. Quote
swnewman Posted February 23, 2013 Posted February 23, 2013 Lee, v.41 I did some research and also saw the recommendation to do a factory reset. I just thought it should be noted that this behavior began after the update. I have no other way of turning that setting on, since ISY doesn't give that option. I think maybe HouseLinc or SmartLinc does. The factory reset seems to have done the trick. Quote
LeeG Posted February 23, 2013 Posted February 23, 2013 swnewman Thanks for the information. I confirmed that my v.40 SwitchLinc has that feature so it would be expected on the v.41. Not sure how that option could have been set since the ISY has no function to manage these new options. Also confirmed the v.40 SwitchLinc has the ‘beep on button/paddle press' feature. A new KeypadLinc came up with the 'beep on button press' enabled after a very short (1/2 to 1 second) power outage. Have not wanted to do a factory reset to see if that would turn Off as that KPL is one I have a hard time communicating with using extended commands. None of my SwitchLincs in the test bed came up with 'blink LED on Insteon traffic' enabled from the short power outage so don't know if they are susceptible to the same type of very short power outage as the new KPL is. Quote
swnewman Posted February 23, 2013 Posted February 23, 2013 Lee, As far as I'm aware we haven't had any power blips. I did find another switch that was blinking and reset it to fix the problem. Just strange that these dimmers and switches have been installed and working for weeks and they just turned this 'feature' on after the update. If it had been more than a couple, it would have been quite the pain to turn it off on all of them. Thanks for your help. Michel, Is this an option that could be added for compatible devices in ISY? So we can at least easily turn it off if it happens? -Seth Edit: Just realized ISY has the ability to set this option on IOLincs, so it should be easy to add the capability to SwitchLincs. Quote
LeeG Posted February 23, 2013 Posted February 23, 2013 swnewman It is odd that it showed after the upgrade. Has a pretty obvious visual so it would seem hard to miss if it existed before. Without many reporting the same result it is not systemic. Have not found a way to recreate. I've restored SwitchLincs, deleted and readded SwitchLincs, cannot find anything that issues a command used to set the equivalent I/O Linc option. Of course moving to 4.0.1 here did not have that result on my SwitchLincs. The cat/subcat (device type) for the SwitchLinc and I/O Linc are very different so it does not seem likely the ISY would have confused a SwitchLinc with an I/O Linc. The cost to implement is the additional Admin Console code to manage all the various SwitchLinc, KeypadLinc, etc variants that now have these features. Plus the cost to regression test which is likely more than the cost to do the initial implementation. Button/paddle beep Blink LED on traffic Resume Bright and some others that do not come to mind are all candidates for future UI management. Quote
swnewman Posted February 23, 2013 Posted February 23, 2013 Yeah, I agree it is weird. But I seem to be a magnet for weird Insteon issues! I definitely would have noticed it before because the affected switches are in the family room where we spend most of our awake time. Who knows the actual cause...at least it was a simple fix! Quote
parkersmith Posted February 25, 2013 Posted February 25, 2013 Leak Sensor works properly. Glad to see the heartbeat is present. I see it is ON when there is a heartbeat. If the Leak Sensor has not sent out a heartbeat in a while, does the ISY change the status to OFF? Trying to determine how best to build a program to let me know when the heartbeat is absent. Also, on setting up a program, the STATUS options for the link sensor is "Responding", "100%" or "Off". Shouldn't is say On instead of 100%? Quote
LeeG Posted February 25, 2013 Posted February 25, 2013 The ISY does not change the Heartbeat to Off on its own. This Program will monitor the Heartbeat node. If Control 'Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours do something - turn On KPL button, send Notify, etc Else - No Actions - (To add one, press 'Action') It was a user suggestion to change On to 100%. Some users were interpreting On to mean any device state that was not Off when On really means 100% On. The change from On to 100% is a general change in the Admin Console, not specific to the Leak Sensor Quote
parkersmith Posted February 25, 2013 Posted February 25, 2013 The ISY does not change the Heartbeat to Off on its own. This Program will monitor the Heartbeat node. If Control 'Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours do something - turn On KPL button, send Notify, etc Else - No Actions - (To add one, press 'Action') It was a user suggestion to change On to 100%. Some users were interpreting On to mean any device state that was not Off when On really means 100% On. The change from On to 100% is a general change in the Admin Console, not specific to the Leak Sensor Thanks for the reply. So why or how would the heartbeat sensor get switched off? If the battery dies, removed or the unit is out of range, I would expect the Leak Sensor to not be able to send an On for the heartbeat. Quote
LeeG Posted February 25, 2013 Posted February 25, 2013 The Program is triggered each time a Heartbeat On (Leak Sensor Dry) or Heartbeat Off (Leak Sensor Wet) is received which should be every 24 hours. This will cause the Program to terminate the ‘Wait 25 Hours’ before it completes and executes the statements after the Wait. So long as the Leak Sensor continues to send Heartbeat messages every 24 hours the Program effectively does nothing but Wait. Should a heartbeat message fail to be received in 25 hours the Program Wait completes and does whatever it needs to do to signal a lack of heartbeat. Quote
parkersmith Posted February 25, 2013 Posted February 25, 2013 The Program is triggered each time a Heartbeat On (Leak Sensor Dry) or Heartbeat Off (Leak Sensor Wet) is received which should be every 24 hours. This will cause the Program to terminate the ‘Wait 25 Hours’ before it completes and executes the statements after the Wait. So long as the Leak Sensor continues to send Heartbeat messages every 24 hours the Program effectively does nothing but Wait. Should a heartbeat message fail to be received in 25 hours the Program Wait completes and does whatever it needs to do to signal a lack of heartbeat. Thanks. Are you sure Heartbeat On = (Leak Sensor Dry) or Heartbeat Off = (Leak Sensor Wet)? Heartbeat was supposed to be Group 4. I am confused by this as I thought the Heartbeat was a completely different signal than the wet/dry responses. I take it you own a leak sensor and have played around with it to make the suggested program work? Quote
LeeG Posted February 25, 2013 Posted February 25, 2013 Heartbeat is Group 4. The Group 4 Heartbeat message contains an On command when the Leak Sensor is Dry and an Off command when the Leak Sensor is Wet. The Heartbeat message is separate from the Leak Sensor Dry Group 1 On message or Leak Sensor Wet Group 2 On message. The Heartbeat message could occur many hours after the last Leak Sensor Dry or Leak Sensor Wet message. I do have a Leak Sensor. Firmware v.3E I do have a HeartBeat Program which is what I posted. I removed the functional statements after the Wait that perform Actions I want executed if the Heartbeat fails to arrive. Below is the event trace messages from a single Leak Sensor Set button tap. The test Heartbeat is generated approx 15 seconds after that last Set button tap. Leak Sensor is physically Dry Sun 02/24/2013 11:54:17 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.01 CB 11 01 LTONRR (01) Sun 02/24/2013 11:54:17 PM : [std-Group ] 21.7A.CC-->Group=1, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:17 PM : [ 21 7A CC 1] DON 1 Sun 02/24/2013 11:54:18 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.01 CB 11 01 LTONRR (01) Sun 02/24/2013 11:54:18 PM : [std-Group ] 21.7A.CC-->Group=1, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:18 PM : [iNST-DUP ] Previous message ignored. Sun 02/24/2013 11:54:20 PM : [iNST-SRX ] 02 50 21.7A.CC 11.01.01 CB 06 00 (00) Sun 02/24/2013 11:54:20 PM : [std-Group ] 21.7A.CC-->11.01.01, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:21 PM : [iNST-SRX ] 02 50 21.7A.CC 11.01.01 CB 06 00 (00) Sun 02/24/2013 11:54:21 PM : [std-Group ] 21.7A.CC-->11.01.01, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:21 PM : [iNST-DUP ] Previous message ignored. Sun 02/24/2013 11:54:34 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.04 CB 11 04 LTONRR (04) Sun 02/24/2013 11:54:34 PM : [std-Group ] 21.7A.CC-->Group=4, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:34 PM : [ 21 7A CC 4] DON 4 Sun 02/24/2013 11:54:34 PM : [ X10] A5 Sun 02/24/2013 11:54:34 PM : [X10-RSP ] 02 63 61 00 06 Sun 02/24/2013 11:54:34 PM : [ X10] A5/On (3) Sun 02/24/2013 11:54:35 PM : [X10-RSP ] 02 63 62 80 06 Sun 02/24/2013 11:54:36 PM : [X10-RX ] 02 52 AA 00 Sun 02/24/2013 11:54:36 PM : [ X10] D4 Sun 02/24/2013 11:54:37 PM : [iNST-SRX ] 02 50 21.7A.CC 11.01.04 CB 06 00 (00) Sun 02/24/2013 11:54:37 PM : [std-Group ] 21.7A.CC-->11.01.04, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:37 PM : [X10-RX ] 02 52 A3 80 Sun 02/24/2013 11:54:37 PM : [ X10] D4/Off (11) Sun 02/24/2013 11:54:38 PM : [iNST-SRX ] 02 50 21.7A.CC 11.01.04 CB 06 00 (00) Sun 02/24/2013 11:54:38 PM : [std-Group ] 21.7A.CC-->11.01.04, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:38 PM : [iNST-DUP ] Previous message ignored. Quote
parkersmith Posted February 25, 2013 Posted February 25, 2013 Heartbeat is Group 4. The Group 4 Heartbeat message contains an On command when the Leak Sensor is Dry and an Off command when the Leak Sensor is Wet. The Heartbeat message is separate from the Leak Sensor Dry Group 1 On message or Leak Sensor Wet Group 2 On message. The Heartbeat message could occur many hours after the last Leak Sensor Dry or Leak Sensor Wet message. I do have a Leak Sensor. Firmware v.3E I do have a HeartBeat Program which is what I posted. I removed the functional statements after the Wait that perform Actions I want executed if the Heartbeat fails to arrive. Below is the event trace messages from a single Leak Sensor Set button tap. The test Heartbeat is generated approx 15 seconds after that last Set button tap. Leak Sensor is physically Dry Sun 02/24/2013 11:54:17 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.01 CB 11 01 LTONRR (01) Sun 02/24/2013 11:54:17 PM : [std-Group ] 21.7A.CC-->Group=1, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:17 PM : [ 21 7A CC 1] DON 1 Sun 02/24/2013 11:54:18 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.01 CB 11 01 LTONRR (01) Sun 02/24/2013 11:54:18 PM : [std-Group ] 21.7A.CC-->Group=1, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:18 PM : [iNST-DUP ] Previous message ignored. Sun 02/24/2013 11:54:20 PM : [iNST-SRX ] 02 50 21.7A.CC 11.01.01 CB 06 00 (00) Sun 02/24/2013 11:54:20 PM : [std-Group ] 21.7A.CC-->11.01.01, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:21 PM : [iNST-SRX ] 02 50 21.7A.CC 11.01.01 CB 06 00 (00) Sun 02/24/2013 11:54:21 PM : [std-Group ] 21.7A.CC-->11.01.01, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:21 PM : [iNST-DUP ] Previous message ignored. Sun 02/24/2013 11:54:34 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.04 CB 11 04 LTONRR (04) Sun 02/24/2013 11:54:34 PM : [std-Group ] 21.7A.CC-->Group=4, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:34 PM : [ 21 7A CC 4] DON 4 Sun 02/24/2013 11:54:34 PM : [ X10] A5 Sun 02/24/2013 11:54:34 PM : [X10-RSP ] 02 63 61 00 06 Sun 02/24/2013 11:54:34 PM : [ X10] A5/On (3) Sun 02/24/2013 11:54:35 PM : [X10-RSP ] 02 63 62 80 06 Sun 02/24/2013 11:54:36 PM : [X10-RX ] 02 52 AA 00 Sun 02/24/2013 11:54:36 PM : [ X10] D4 Sun 02/24/2013 11:54:37 PM : [iNST-SRX ] 02 50 21.7A.CC 11.01.04 CB 06 00 (00) Sun 02/24/2013 11:54:37 PM : [std-Group ] 21.7A.CC-->11.01.04, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:37 PM : [X10-RX ] 02 52 A3 80 Sun 02/24/2013 11:54:37 PM : [ X10] D4/Off (11) Sun 02/24/2013 11:54:38 PM : [iNST-SRX ] 02 50 21.7A.CC 11.01.04 CB 06 00 (00) Sun 02/24/2013 11:54:38 PM : [std-Group ] 21.7A.CC-->11.01.04, Max Hops=3, Hops Left=2 Sun 02/24/2013 11:54:38 PM : [iNST-DUP ] Previous message ignored. Thanks for the detailed message. This make sense to me now. Quote
hmatos Posted February 26, 2013 Posted February 26, 2013 I'm not sure if this is where I'm suppose to post any ZWave issues, but here goes. I've also opened a support request. I've installed the Z-Wave module and it appears to work - the green light comes on. I start to add a Z Wave Device, but my device fails to add. I am attempting to add a Schlage BE469NX - which worked under Vera Lite UI5. Quote
LeeG Posted February 26, 2013 Posted February 26, 2013 hmatos There is a forum category dedicated to the ZWave Alpha viewforum.php?f=93 There is a limited number of devices currently support by the Alpha. Don’t know if the lock mentioned is covered. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.