David D Posted February 28, 2009 Share Posted February 28, 2009 Like the heading says, am I supposed to have two "QueryAll" programs in "My Programs"? Both are set to run at 3:00:00am. Link to comment
Brian H Posted February 28, 2009 Share Posted February 28, 2009 No. I ran with none for a few months since I deleted it from what the factory shipped it with. I did add one manually. Link to comment
Michel Kohanim Posted March 1, 2009 Share Posted March 1, 2009 Hi David D, NO! You should have only one. Please remove the other one. With kind regards, Michel Like the heading says, am I supposed to have two "QueryAll" programs in "My Programs"? Both are set to run at 3:00:00am. Link to comment
aLf Posted March 1, 2009 Share Posted March 1, 2009 I have not had a querry for two years! Should I insert one? If so, what is the best code? aLf Link to comment
Michel Kohanim Posted March 1, 2009 Share Posted March 1, 2009 Hi aLf, it's not necessary if you do not use dim/brighten extensively. If you do, all you have to do is to: If Time is 3:00 AM Then Set Scene My Lighting Query With kind regards, I have not had a querry for two years! Should I insert one? If so, what is the best code? aLf Link to comment
bocaray Posted August 9, 2010 Share Posted August 9, 2010 Michel, Could you explain the 'QueryAll' and why it is even needed? It seems that some of my sensors are triggered when this runs at 3:00 AM and I can't determine why. Can it be eliminated? Link to comment
Michel Kohanim Posted August 9, 2010 Share Posted August 9, 2010 Hello bocaray, It's really not needed unless you have programs that depend on 100% accurate reporting of device status AND you do a lot of dim/bright commands. With kind regards, Michel Link to comment
Mark Sanctuary Posted August 9, 2010 Share Posted August 9, 2010 Michel,Could you explain the 'QueryAll' and why it is even needed? It seems that some of my sensors are triggered when this runs at 3:00 AM and I can't determine why. Can it be eliminated? Its a check of every device under your "My Lighting" which everything you have linked to the ISY. In most cases the ISY has things already synced but there is times that a status is not matching and this query corrects it. I like to leave mine as another insurance tool for reliability of my setup but as Michel says its not a required program. Link to comment
Mark Sanctuary Posted August 9, 2010 Share Posted August 9, 2010 I am not totally sure about why the sensors are being triggered when the query runs...another thing you can do if you don't want your sensors triggered is you can Query once an evening an all scene that would exclude the sensors. Link to comment
bocaray Posted August 10, 2010 Share Posted August 10, 2010 Thanks to all. I like the idea of a Query that excludes the sensors until I can figure out why they are triggering. Appreciate replies. Link to comment
rgn2000 Posted March 10, 2011 Share Posted March 10, 2011 Bringing up an old topic. I have just the beginning setup of my network with only a few devices so far. One of them happens to be the garage sensor. I have text notifications set up to send to me when it goes to ON or OFF. At 3:00am when it does my "query all" I get a text message saying it is ON (closed). That seems fine because it is actually ON (closed), but when I open the door for the first time after this I do not get a notification, but I do again when it goes back to ON. Then any subsequent OFF and ON's I get the notifications for both. It is no big deal, but was wondering what in the "query all" is causing that? Link to comment
Michel Kohanim Posted March 11, 2011 Share Posted March 11, 2011 Hello rgn2000, What type of sensors are these? If IOLinc and an older version, they did have a bug where the status of the sensor was sent as the status of the relay. If you are not getting any notifications on demand, then do see the status of the sensor change when you open/close the garage in the Admin Console? If not, then perhaps there's no link in the PLM. You might want to try Right Mouse Click on the device and then choose Restore Device. With kind regards, Michel Link to comment
rgn2000 Posted March 11, 2011 Share Posted March 11, 2011 Yes it is the I/O Link from smarthome... http://www.smarthome.com/74551/I-O-Linc ... Kit/p.aspx I am getting notifications with no issues. It is just when the "query all" happens once a day it interferes with it. Let me give you a real life example. Thursday night - 9:50pm - Open door - Receive Notification OFF Thursday night - 10:00pm - Close door - Receive Notification ON Friday morning - 3:00am - QUERY ALL - Receive Notification ON Friday morning - 7:00am - Open door - DO NOT Receive Notification for OFF Friday morning - 7:30am - Close door - Receive Notification ON Friday morning - 9:30am - Open door - Receive Notification OFF Friday morning - 9:45am - Close door - Receive Notification ON As you can see I am getting notifications all the time, except for the very first occurrence after the QUERY ALL. It is not a huge deal, but I guess it could lead to other issues that I am not sure about with other things so was just wondering why this would happen and/or if there is something I can change. Thanks Link to comment
Michel Kohanim Posted March 12, 2011 Share Posted March 12, 2011 Hello rgn2000, Thanks the issue is the IOLinc ... older versions reported the status of the sensor as the status of the relay and thus all the errors. Please do be kind to get it replaced. With kind regards, Michel Link to comment
rgn2000 Posted March 12, 2011 Share Posted March 12, 2011 I just got it like 2 or 3 weeks ago. This is not an old version. To me this has nothing to do with that. The sensor is reporting properly and NOT reporting the status of the relay. The status gets reported correctly, I just do not get the notification in that one example above, but the status does indeed change to OFF. Rob Link to comment
Michel Kohanim Posted March 13, 2011 Share Posted March 13, 2011 Hi Rob, I am not sure what to think ... There are basically two cases: 1. The program is NOT run ... you can test this by looking at the last runtime column in the Program Summary tab. You may want to issue a query on My Lighting to test 2. The program is run but the notification is NOT sent ... two cases: a. In Error Log, please check for SMTP errors (-5000x) b. The condition is not evaluated correctly ... check the Logs to see if the status is correct and it jives with your program With kind regards, Michel Link to comment
rgn2000 Posted March 13, 2011 Share Posted March 13, 2011 Hello rgn2000, Thanks the issue is the IOLinc ... older versions reported the status of the sensor as the status of the relay and thus all the errors. Please do be kind to get it replaced. With kind regards, Michel My bad on my previous posts. I was mixed up and actually I am getting a bad read at the 3:00am Query. I changed my table below... Thursday night - 9:50pm - Open door - Receive Notification OFF Thursday night - 10:00pm - Close door - Receive Notification ON Friday morning - 3:00am - QUERY ALL - Receive Notification OFF (WRONG) Friday morning - 7:00am - Open door - DO NOT Receive Notification for OFF Friday morning - 7:30am - Close door - Receive Notification ON Friday morning - 9:30am - Open door - Receive Notification OFF So I am indeed get wrong status updates upon query like you said, but this is a new unit. How can this be fixed? Thanks Link to comment
LeeG Posted March 13, 2011 Share Posted March 13, 2011 rgn2000 Do you have the IO Linc set for Trigger Reverse? If so that is the answer. Trigger Reverse does not reverse the Query results. Lee EDIT: the default operation of the IO Linc is to send an ON command when the Sensor turns On and an OFF command when the Sensor turns Off. Trigger Reverse reverses that. An OFF command is sent when the Sensor turns On and an ON command is sent when the Sensor turns Off. Trigger Reverse does not change the basic Sensor On/Off operation relative to the Sensor being connected to GND or not. Query is returning the true On/Off state of the Sensor, not the reversed ON/OFF commands. Link to comment
rgn2000 Posted March 14, 2011 Share Posted March 14, 2011 That must be the problem then although it does send and ON command when it is indeed ON. It is just when I query that causes the problem. I set it for Trigger Reverse because of the directions in the following link.... http://www.universal-devices.com/mwiki/ ... e_Door_Kit I want to eventually set up keypadLincs so that is why I set it up as such. I do not have any as of yet though. So then in order to do what the link above is saying, if you ever have to query you will always get a false read? Link to comment
LeeG Posted March 14, 2011 Share Posted March 14, 2011 rgn2000 With the Trigger Reverse set, when the Sensor physically turns ON the IO Linc sends an Off command. When the Sensor physically turns OFF, the IO Linc sends an On command. The Green LED near the IO Linc connections shows the physical ON/OFF state of the Sensor. It is not affected by the Trigger Reverse option. Trigger Reverse simply reverses the On/Off commands sent by the IO Linc. There is nothing wrong with the instructions and sample Program. It works as the original author wanted it to. That implementation did not anticipate a Query being part of day to day operation. One solution is to stop Querying the IO Linc. Another solution is below. If you used the Smarthome garage kit it came with a magnetic sensor that has both a NO and NC switch built in. Simply use the other wire (red instead of green or green instead of red) from what you are currently using and turn the Trigger Reverse Off. That will restore the IO Linc to default operation where the Query result will match the default ON/OFF state and On/Off command. Note that when changing the Trigger Reverse option and magnetic switch connection it is necessary to cycle the magnetic switch (open/close the garage door) to get the IO Linc in sync with the new setup. Lee Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.