lupinglade
Senior Member
The reason it takes longer to refresh in Haiku is because it displays a lot more info at any one time. However, there are many optimizations and some preferences and tips that can make Haiku a lot quicker.
First off, Haiku only loads what it needs -- that is depending on what tab you're on, what will be loaded on connect changes. For example, the Status tab loads Areas, Zones and Aux sensors as well as buttons because that is what it displays. Thus opening Haiku to the Status tab may be a little slower. See tips below.
Haiku uses cache to avoid loading names unless it's a fresh launch, the cache has been manually purged or the cache is older than 7 days. This is to keep Haiku's interface up to date with the controller and only takes a little longer to refresh initially, then the cache is good for another 7 days.
Now here are some details and tips:
- Controller firmware 3.9 seems to make the controller send data quicker resulting in a noticeable speed improvement in Haiku.
- Refreshes do take processing power so the fastest device is an iPad 2 or iPhone 4S. Devices like the iPhone 3GS are considerably slower.
- Ensure Quick Connect is on in Haiku's preferences, otherwise Haiku will refresh named on every connection.
- Turn off the Full Refresh option in Haiku's preferences. This option causes Haiku to preload Units and other data on connect even if you did not request it, speeding up overall usability and interface accuracy, but slowing down the initial connection process.
Haiku also has priorities assigned to certain tasks. So for example a command to turn a light on will be sent before a bunch of refresh commands even if those were queued first. So just because the spinner is going doesn't mean your command won't be sent until its done.
Lastly, Haiku refreshes objects in a somewhat random order so a list of lights may appear to refresh slower if you are only looking at a portion of the list because the refresh is not sequential. Also the Rooms view in the Control tab may seem slower but that's because each room consists of refreshing a number of units.
Personally I use an iPhone 4s with the prefs mentioned above and it is very quick. The other factor may be how big your system is. Are there very many units or zones? Our test system is fairly large. But I can imagine bigger systems do exist.
First off, Haiku only loads what it needs -- that is depending on what tab you're on, what will be loaded on connect changes. For example, the Status tab loads Areas, Zones and Aux sensors as well as buttons because that is what it displays. Thus opening Haiku to the Status tab may be a little slower. See tips below.
Haiku uses cache to avoid loading names unless it's a fresh launch, the cache has been manually purged or the cache is older than 7 days. This is to keep Haiku's interface up to date with the controller and only takes a little longer to refresh initially, then the cache is good for another 7 days.
Now here are some details and tips:
- Controller firmware 3.9 seems to make the controller send data quicker resulting in a noticeable speed improvement in Haiku.
- Refreshes do take processing power so the fastest device is an iPad 2 or iPhone 4S. Devices like the iPhone 3GS are considerably slower.
- Ensure Quick Connect is on in Haiku's preferences, otherwise Haiku will refresh named on every connection.
- Turn off the Full Refresh option in Haiku's preferences. This option causes Haiku to preload Units and other data on connect even if you did not request it, speeding up overall usability and interface accuracy, but slowing down the initial connection process.
Haiku also has priorities assigned to certain tasks. So for example a command to turn a light on will be sent before a bunch of refresh commands even if those were queued first. So just because the spinner is going doesn't mean your command won't be sent until its done.
Lastly, Haiku refreshes objects in a somewhat random order so a list of lights may appear to refresh slower if you are only looking at a portion of the list because the refresh is not sequential. Also the Rooms view in the Control tab may seem slower but that's because each room consists of refreshing a number of units.
Personally I use an iPhone 4s with the prefs mentioned above and it is very quick. The other factor may be how big your system is. Are there very many units or zones? Our test system is fairly large. But I can imagine bigger systems do exist.