| PM | Quote | Reply | Full Topic |
| Joined: | Wednesday Feb 18th, 2009 |
| Location: | United Kingdom |
| Posts: | 109 |
| Status: |
Offline
|
I am not quite sure how to categorise this, because to be honest I'm not quite sure what is going on.
Our topology is not very complex:
- comfort 2 main, outputs driving relay boards
- A remotely located RIO (connected via main panel) for controlling some lights and inputs from sensors in the drive and front of house
- A Slave module for outbuildings
- An IRIO (connected via the SEM) for controlling lights and inputs from sensors in the garden
For all things on control menu I have flags associated with them for the status to be shown on the app (IRIO requires flags to control it too, and I just did the menu the same way for the RIO, the differences are in the responses).
I am using timers in some responses to turn the lights on in sequence when a sensor is triggered. I have disabled these sensors by disconnecting them from RIO, so they shouldnt happen at present.
The problem (if it is one):
I notice the following when I use the comfort app (doesnt matter if its on iphone, samsung phone, or samsung tablet)
When I select Control, and then the specific section, the on/off status of the things controlled by the RIO initially say 'Wait', and after a number of seconds appear.
This doesnt happen for any of the other things. I am unclear why there would be a delay in getting status for some flags over others.
Second problem:
when I switch one of them on/off it seems to take ages to action sometimes. For example, if I switch on 1 output via the app for the first time today, it might happen straight away, or it might take a couple of minutes.
Its not simply the app not updating, as I can see the light doesnt come on until roughly the same time the app status updates.
When I use the control menu it uses different responses to turn the lights on/off in one go by setting/clearing the flag, turn the outputs on/off, and stop the timers.
Have I somehow created a dependancy on the timers ?
I have set a bunch of 'Do response after x seconds using timery' in the responses that sequence the lights. In the others they do 'stop timery' for all the timers used.
When I run a response (say to turn lights on), if I trigger another response does it get queued up on the stack, or done in parallel ?
Just wondering if I have one response waiting on a timer and another stops the timer...
Is there any way to see what response comfort is currently doing, or what is in its stack of responses ?
I also see this same behaviour if I monitor the output using comfigurator, and action responses from it.
Any thoughts ?
Cheers,
John.
p.s. slychiu, I uploaded the config file recently to put on my phone, so if you keep a record of these you have the file already
| Close Window |