Newbie questions

Plugins & Plugin Development openHAB MiOS Binding
#1

Hi,

I’m considering testing this but I’m wondering if there will be any significant delay in scene activations or other functions when OH handles them?
Are there any advantages using Vera as the Z-wave communicating device vs. a rasberry with a z-wave usb stick (or the z-wave.me daughter card) ? :slight_smile:

#2

Welcome to the fold! No you will not see almost ANY lag between the response you were getting with Vera vs OpenHAB. Many have actually said the Raz with adapter is actually worse. This was my number one fear when I got started, but it was snappy as ever. If anything, I almost feel like some things run faster now through OpenHAB than they did with Vera. Simply because it’s not Vera doing much processing other than simply sending a signal based on the command sent from OpenHAB. All the other intelligence you once had to program through Vera to automate, seemed to make the response a little slower I believe.

Keep in mind though that different devices and the ZWave network will also affect this. For the most part though, not I think you will be pleasantly surprised how quick and snappy it is.

#3

A few quick notes:

a) New openHAB rules, never executed since openHAB started, take longer
There’s a pseudo-compile step that occurs on the first time a rule is executed, and this drags out the execution time for the first invocation.

And by drag out, I mean it can be 2-30 seconds “extra” for that first-time execution just after you wrote/published it. More typically it’s ~2seconds

I’m going to see if there’s a way to force-compile (“warm up”) the openHAB Rules so we don’t have to pay the price on the first execution.

b) A Scene running no MiOS “sendCommand” calls takes about 20-40ms to execute.
I have a number of scenes that conditionally execute their MiOS code. When they’re not calling out to MiOS, these scenes do date-time tests (for Night), [Debug] logging and some limited timing/conditionals.

These take 20-40ms per call (timed from inside the routine), and are being used for stuff like turning lights on when motion is detected.

I have timing hooks permanently in each of my Rules.

c) Delay from MiOS publishing in the HTTP Stream is about 10ms
and often less… The one major exemption to this is the nightly Heal operation that MiOS does, where they have an egregious Bug that floods ANY UI-Simple/Control-Point/UI device connected to them at that time.

I don’t scene stuff often at that time, so I have no idea what impact it has, but it can’t be healthy to do that on such a resource-limited system (Vera3), and I’m sure it accounts for why there are often more than one restart/reboot at that time.

I still have some tuning work to do, mostly related to when a lot of Commands are send FROM the openHAB system TO to the MiOS System. That said, once my MiOS system is reduced to only performing Z-Wave operations it’s going to get serialized on Z-Wave communications anyhow.

NB: All timing data relative to my openHAB deployment on an Odroid C1 with 1G RAM and a PNY SD Card. Network connection between Vera3 and openHAB is Netgear switched Gigabit Ethernet (two switches between)

#4

Thanks guys, think I’ll have a go at this :slight_smile:

#5

[quote=“guessed, post:3, topic:186507”]A few quick notes:

a) New openHAB rules, never executed since openHAB started, take longer
There’s a pseudo-compile step that occurs on the first time a rule is executed, and this drags out the execution time for the first invocation.

And by drag out, I mean it can be 2-30 seconds “extra” for that first-time execution just after you wrote/published it. More typically it’s ~2seconds

I’m going to see if there’s a way to force-compile (“warm up”) the openHAB Rules so we don’t have to pay the price on the first execution.[/quote]

Thank you for that interesting explanation. I have noticed this “first time running delay” but have no idea what was the reason.
If you find something, let us know.