Query doesn't work unless manually invoked

[MWareman]

 

 

I had this setup in Homeseer HS3.

HS3 has a section where Polling(Query I assume in ISY) can be set for each device.

I had it set to poll the device every 15 seconds.

This would allow me to turn on the fan in my office with the paddle and with 15 seconds the lights would come on.

 

As a FYI, can you not do on ISY what you did on HS3 and setup a program to query your devices, wait 15 seconds and then loop? It seems to me that ISY is behaving just as HS3 did for you.

[apostolakisl]

As a FYI, can you not do on ISY what you did on HS3 and setup a program to query your devices, wait 15 seconds and then loop? It seems to me that ISY is behaving just as HS3 did for you.

 

I missed that you had to have hs3 query every 15 seconds.  If indeed that is the case, then hs3 was not getting "on the fly" status updates either.  You you can query the same with ISY.  

 

Set the below program to "run then" at startup.  Create a scene with all the z-wave devices you want to query.  Or you can list them all out in the program individually.  I suggest starting by just querying the one device in question.

 

If

blank

Then

Repeat every 15 seconds

query 'the z wave switch in question'

Else

blank

 

Keep in mind that any program using the status of a z-wave device could be delayed by up to 15 seconds.

 

You will need to manually this program the first time (or reboot ISY).  To manually run it, right click it in the program tree and hit "run then".  

 

EDIT:  You just click "enable run at startup" from the right click menu in the program summary page.  When the "if" clause is blank, it will execute the "then" clause at startup.

[LeeG]

In case you decide to look at the ISY again and for the benefit of others considering using the ISY a few points.

 

What was missing from most of the forum discussion was needing Polling in HS.  This means that the wall switches do not send results of manual operation changes which is why Polling is required in HS.

 

ISY Program(s) can poll the ZWave devices just as HS does (example provided).

 

Neither "If Status" nor "If Control" generate device communication.   "If Status" checks the device state information already in the ISY and "If Control" looks at commands sent from the device due to changes at the device.

 

The combination of Polling done by an ISY Program(s) and "If Status" would have provided the HS equivalent.

 

Hopefully this will help others moving from HS. 

[andyf0]

FYI, all my Jasco/GE switches do provide an instant status when operated from the paddle, without polling. However, the switch has to be in direct contact with the ISY, not communicate via the mesh network and route through other devices.

 

I have a couple of switches that are borderline in range and the ISY sometimes get the status, other times not, although I have no problems querying or controlling those switches from the ISY. I'm working on that.

[Josshe]

apostolakisl,

 

You are absolutely a genius!!!

That fixed it!!!

I get to keep my ISY and the wonderful technical support and forum support!

Sorry for all the exclamation marks but i'm super stoked right now.

 

I knew what I was asking was not out off the realm of the ISY, I just did not know how to go about it.

 

I setup two devices for testing and they worked flawlessly!

 

Now I can leave the HomeSeer terrible tech support behind.

 

I have the ISY9941ZW/IR PRO, do you think that me making queries every 15 seconds for about 6 devices will over tax the cpu in the ISY?

 

HS3 had no problem with this type of operation as long as I kept it under 10 devices making such timed queries.

 

I've learned one major difference between the ISY os and the HS3 os.

HS3 continually executes/checks its programs after saving them and the ISY needs to be told to either run at startup or execute manually.

That is no problem at all, but very much needed information.

 

Thank all of you that replied to my plight and Steve at UDI... Awesome is all I can say.

I'm a UDI patron for a long time to come...

 

I was so very sad this morning as I took down the ISY and prepared it to be shipped back and was not looking forward to redo of the entire include/exclude process for the z-wave network.

Then I thought I'd check the forum just one last time and say goodbye.

I saw your post, tried it, and I'm a happy camper.

 

I'm thinking since I got the (1024) ISY that I should be okay with programming and scenes for 66 devices and once they get 5.0 deployed so that I may control my Gen5 siren and smart strip, I will be on cloud 9 if you will.

 

Now I can order the antenna kit!

 

Come on 5.0... I'm ready and waiting.

[apostolakisl]

Since a query requires a command and individual response from each device, I don't think ISY issues a scene query all at once.  It would seem by watching the task bar after initiating a query of a large scene, that it goes through one at a time so as to not overload the com.  I assume it will do the same with a z-wave scene.  You might create a scene with a bunch of z-wave devices and then issue a query command to it and see how it processes.  I am not sure how many devices you could include in a query scene that you repeat every 15 seconds before it overwhelms the system.  Some trial and error may be necessary.

[Josshe]

apostolakisl,

 

Thank you so very much for your spot on information!

I've sent the same question to Steve at UDI and am waiting for a reply.

 

I called UDI yesterday as I had a program to turn off all the lights during the day that would repeat every 10 minutes.

I light of the other issues (now resolved) I was having, I deleted the program and even rebooted the ISY.

 

To my chagrin, the program continued to executed but could not be found in the UI. 

 

I was instructed to reset the ISY to factory and restore my backup.

The rogue program went away but only 4 of my 66 z-wave devices restored even after doing a z-wave Synch and Heal.

So I guess i'll have to redo the missing devices again, but still not a deal breaker.

 

Now I want to add the antenna for extended range plus I like the way it looks on the ISY.

I there any benefit to increase the size capacity of the SD card from 2gig?

[Josshe]

In case you decide to look at the ISY again and for the benefit of others considering using the ISY a few points.

 

What was missing from most of the forum discussion was needing Polling in HS.  This means that the wall switches do not send results of manual operation changes which is why Polling is required in HS.

 

ISY Program(s) can poll the ZWave devices just as HS does (example provided).

 

Neither "If Status" nor "If Control" generate device communication.   "If Status" checks the device state information already in the ISY and "If Control" looks at commands sent from the device due to changes at the device.

 

The combination of Polling done by an ISY Program(s) and "If Status" would have provided the HS equivalent.

 

Hopefully this will help others moving from HS. 

 

Good point.

 

Also HS start testing the programs immediately after entry and continues to do so where the ISY in my case needed to be invoked at startup.

However the ISY has really neat way to manipulate the programs.

HS has voice control and programming which is cool but needs to be a bit more stable and offer better tech support..

 

Back on subject...

It'll take me an extra two program lines to do in ISY that I did in HS but the extra reliability and stability is worth the effort.

I do miss HS talking to me in the morning...

[apostolakisl]

ISY has a learning curve as it works a bit unconventional.  Not sure how HS works, but if programs started running at startup that you didn't want to run, this would be an issue.

 

There are 2 concepts to understand

 

1) Trigger

2) Evaluation

 

Any line in an "if" clause can be a trigger and all lines are evaluated after a trigger event. 

 

Control: is a trigger.  Requires the exact message to be a trigger.  ie Control switched on means that the device on paddle was pushed.  Makes no difference if it was already on or not.

Status is a trigger when the status changes in ISY's record.  

 

Both control and status get evaluated if something else triggers it.  Control will always evaluate false unless it was the trigger, for obvious reasons.

 

Time is a trigger when either the "from" or "to" times are met and is true at the from and false at the to.

Time evaluates to true if it is between those times and some other trigger runs the program

Time is x is a trigger at that time and is true.  Any other trigger will evaluate to false since it can't possibly be simultaneous to that exact time.

 

These are some of the basics.  All if conditions work on this same premise and you must understand it or your programs will not behave as you expect.

[Michel Kohanim]

Josshe,

 

Ads LeeG suggested, if the status does not change then the program is not evaluated.

 

Do you actually want a program to run regardless of status change? If so, can you please give an example?

 

With kind regards,

Michel