Slow response from inputs / outputs

[pilfos]

Hello,

I've tested the ihcserver on a Raspberry 3 and the input / outputs are not refreshed immediately.

Some times I need to press during 1 sec a button so it can be "catched" by ihcserver.

Which is the minimum requirement for ihcserver to run smoothly?

Regards

[skumlos]

Are we talking through the web interface or directly in IHCServer?

[pilfos]

Both, from webinterface and I can see there is no output in the ihcserver log console if I quickly switch on / off a light

[skumlos]

I think this is inherent to the interface to the IHC controller. There's around 150ms between each command that allows IHCServer to retrieve data. It then has to decide what to do (update inputs or outputs), and when I wrote the code, I often ended up crashing the controller if I requested data too often. So when the controller "gives" IHCServer permission to "do something" IHCServer then sends a request, the controller responds, a quick press-and-release can easily be overlooked as the complete on-time might be in the 200ms area. I see the same issue with PIR sensors. When I first wrote the software I remember trying to optimize this, but it ended up locking up the IHC controller at some point, sometimes after a few minutes, sometimes hours, but it rarely lasted a day. This current implementation was stable, and good enough for my use, but I have not spent time on trying to improve it. You're welcome to try of course, that's the beauty of open source :)

[skumlos]

I just tried making some timing, and it is not uncommon that it takes up to 300ms (worst case above 400ms), from IHCServer waits to be "allowed" to request data, until the controller allows it.

[pilfos]

Which hardware are you using to run IHCServer?

I didn't want to state any problem with your code opening this issue but it was the opportunity to contact you. :)

Thanks for your answers.

[skumlos]

Using a Raspberry Pi 2B. No worries, it's always interesting to research :)