after a long time, PR was reviewed and some modifications was need. Additionally, i build the binding against 2.4.0 snapshot. Download it here, please. Is it possible to get feedback, if it still work? Thanks
@novoplan: As far as i see, you are using old configuration style. It will not work with current binding version.
You can access analog block now via
Thing analog aInputs [ kind="AI" ]
Thing analog aOutputs [ kind="AQ" ]
Inputs/Outputs can be found then in Channels:
Please, take a look into documentation for more details. The warning in a log file simply says, that binding was unable to get new states from Logo and the reason why.
@wita01: VMWare can be a reason for your network issues, since communication runs via virtual network adapter and not physical one. May be this helps… That’s right, binding creates two reader threads: One thread to monitor data state changes and another to monitor RTC (Real Time Clock). The reason is simple: Logo updates RTC once a second. And i’ll have the value as accurate as possible, even data update thread is configured to fetch changes once a minute. Please, forget PaperUI, if you will monitor state changes properly. PaperUI simply fail to get changes. Sometimes it helps to reload browser page. Additionally, especially pulse things tends not to update properly, if modified via PaperUI. My test system ends sometimes in a kind of endless loop: Pulse switch goes pemanently ON/OFF. Restart openhab or Logo! will help only