Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to fetch Miniserver PLC readings #337

Open
raintonr opened this issue Oct 5, 2022 · 2 comments
Open

Option to fetch Miniserver PLC readings #337

raintonr opened this issue Oct 5, 2022 · 2 comments

Comments

@raintonr
Copy link
Collaborator

raintonr commented Oct 5, 2022

There are a number of PLC type statistics available from the Miniserver, documented here (CPU, interrupts, LAN packets sent/received, etc, etc):

https://www.loxone.com/enen/kb/web-services/

While these are maybe not of interest to some, I think it would be useful to have at least an option to fetch these periodically. Once fetched they could be used in any way a user wishes. For example I would graph them in an InfluxDB/Grafana dashboard but also...

I have been thinking about this for a some time now, but yesterday a condition occurred as a result of my Miniserver config that caused a nasty feedback loop, which in turn was causing the Miniserver to run slowly and cause issues with our KNX bus. I quickly addressed this once I noticed, but...

If ioBroker was watching the PLC statistics imagine this could have been detected in a more timely manner by spotting a peak in CPU/interrupt or other activity and an alert been triggered so I could have investigated the issue sooner.

As a side issue, I notice that on re-booting the Miniserver an attempt to reconnect is tried many times during a reboot. Using http://miniserver/dev/sps/state to wait for the correct state before attempting a reconnect may be more efficient.

@raintonr
Copy link
Collaborator Author

raintonr commented Oct 6, 2022

It strikes me that ioBroker.parser could do this, but within that adapter one manually has to configure every statistic/reading they are interested in. Maybe if the parser adapter had some kind of template ability to add numerous objects for the same device type via some kind of configuration import (which in this case would be for a Loxone Miniserver) that avenue might be more appealing.

@raintonr
Copy link
Collaborator Author

raintonr commented Oct 8, 2022

So using ioBroker.parser as discussed (ioBroker/ioBroker.parser#75 (comment)) I created a little JS file that one runs to add all the necessary config for the parser adapter.

At first this overloaded my Miniserver every time it was polled so added a delay (see ioBroker/ioBroker.parser#77) which solved the problem.

Now working great 😄

Perhaps we could add a little 'wizard' thing to the Loxone adapter that prompts the user for host/user/pass/parser instance fields and then creates the necessary parser config?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant