Haiku HAI and the iPAD

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.
 
I am using an iPad2 and Iphone 4s. Still slow. I will ask where is the haiku preferences to turn off the "Full Refresh Option"? I also have version 3.9 Firmware but I do have a very large system. I have every room utilized and I don't know the total number it is a lot of zones for security. So please let me know.

Thanks,

Neil
 
Neil: the two settings are found in the Settings app on your device, scroll down to the Haiku section. With a large system turning off Full Refresh should make a huge difference.
 
I have been very pleased with Haiku and the frequency of updates, but on this issue I asked for it back in July on page 9, at least they listened to you ;)

I know. Its on the TODO ;-) It just wasn't a high priority as not many have asked for it. But now its enough to move it up on the list.
Thanks for this one! Any comment on a message chiming with sound upon login especially if shown with "no beep" hours before?

Unfortunately when we retrieve a message from the controller after it has already been sent, there is no indicator on whether it was sent with or without a beep. I'll see if it makes sense to make it not beep in such a situation regardless, but that may be a little inconsistent. Why not use the mute switch at night? ;)
 
I have been very pleased with Haiku and the frequency of updates, but on this issue I asked for it back in July on page 9, at least they listened to you ;)

I was speaking of the "responsiveness" of the app WRT my Omni. ;)



Going back and reading through this thread, I see at least 3 others (including yours) making the same request.
Maybe I just hit it lucky with the timing. :)
 
Lupinglade,
Thank you for your reponse.
What you are saying makes sense.
I hope you didn't take my input the wrong way.
Again, I am extremely satisfied with your product and, like everybody else, I appreciate your quick reponses and constant improvements.
 
Unfortunately when we retrieve a message from the controller after it has already been sent, there is no indicator on whether it was sent with or without a beep. I'll see if it makes sense to make it not beep in such a situation regardless, but that may be a little inconsistent. Why not use the mute switch at night? ;)

I figured there might not be any indication of the message beep after the fact. I would argue though that the logical behavior in this case would be to never play a sound after the fact regardless of beep flag. The beep should only occur when the message is initially displayed, not at any time later. If Haiku isn't logged in at the time then it missed the beep and should not try and recreate it. The way Haiku works now would be equivalent to a console with a proximity sensor and the console would not beep for a message until you walked up to it, which would not be desirable.

I do try and use the mute switch, but I miss it many times, as I am just picking up my phone to arm the system. This is not something I should have to think about, the message was sent hours ago, having it beep now makes no sense, on top of that I sent it with no beep originally!

I need to check but do you do this with entry/exit zone chimes? That is if you log into Haiku while the back door is open does it chime? This would be the same issue to me, the chime should only occur when the zone changes state, not later when Haiku reads it's state.
 
Networking newbie alert!

If I wan't to use Haiku (or anything really) offsite, how do I set it up?
I understand I'll probaly need a DynDNS account and static public IP address.
The IP address get's me to my modem and router, how do I associate the 192.168.xxx.xxx local IP addresses behind the router?

Is it as simple as the staic IP get's me to the house, and the port to the controller is the comms path?

If that is the case, do I put the static public IP address in in place of the local IP address in the setup?

(Trying to get this to work witht he Western Mountain RUC too and I'm confused.)

THX
 
@Desert_AIP: You need to first configure your router to forward port 4369 to your controller's local IP address (and also port 4369(.

Once you've done the above, as long as your Internet (WAN) IP is static, you don't need a DynDNS service (unless you want it). You can simply enter the Internet IP (you can find out what it is at this link: http://whatismyip.com/) and port 4369 in Haiku.

Otherwise if your Internet IP changes (dynamic), you will need to sign up with a DynDNS provider and install their app to keep updating the hostname to match your dynamic IP address.

So essentially, its just a matter of getting the router to forward port 4369 to the local IP address of the controller.
 
@Desert_AIP: You need to first configure your router to forward port 4369 to your controller's local IP address (and also port 4369(.

Once you've done the above, as long as your Internet (WAN) IP is static, you don't need a DynDNS service (unless you want it). You can simply enter the Internet IP (you can find out what it is at this link: http://whatismyip.com/) and port 4369 in Haiku.

Otherwise if your Internet IP changes (dynamic), you will need to sign up with a DynDNS provider and install their app to keep updating the hostname to match your dynamic IP address.

So essentially, its just a matter of getting the router to forward port 4369 to the local IP address of the controller.


Thanks lumpinglade!

That sounds almost simple enought that I should be able to figure it out. :)
 
Back
Top