| PM | Quote | Reply | Full Topic |
| Joined: | Wednesday Feb 18th, 2009 |
| Location: | United Kingdom |
| Posts: | 109 |
| Status: |
Offline
|
I will email it again when I get home.
I have filled up all of the available control menus, so I guess that makes it extensive.
I did a bit more testing over the weekend.
The RIO entries definitely take longer to initially get their status, but the outputs which are simply on/off without using timers activate pretty much straight away (comfort panels outputs are straight away, IRIO and RIO non timed are a shade longer - long enough to notice but only because I was checking, certainly not a problem).
It seems it is only the one on/off entry in the control menu that has a long (or rather, variable) delay, and only when done from the app.
Activating the response from Comfigurator that the control menu item uses sees the output switch on/off straight away.
I am going to take the timers out of the responses for now and see if that fixes it. If it doesnt, god knows what is going on.
Another thought. Can I get a response to add an entry into the event list ?
I could use that to debug if / when the responses are triggered to some extent. At least I could see when or if the response gets actioned from the app.
Its real odd that having pressed the slider to turn on/off this item, I can switch other things on and off that happens straight away while this one still doesnt happen straight off.
This isnt a show stopper, just frustrating that we cant turn the drive lights on when we want for someone to walk down it. These same responses are used to turn them on at dusk and off at midnight, and appear to work just fine, as do the sequenced responses when a car is detected.
Cheers,
John.
Last edited on Monday Dec 18th, 2017 05:37 pm by John W
| Close Window |