Can I get protocol errors to publish on MQTT topic?

[TimHaydnJones (Tim Jones)]

I have openhab 1.8 running on numerous rpi’s with z-wave binding and sensors.
Yesterday, I saw one of the motion sensors (Everspring SP103) go absolutely ape due to critically low battery - pushing out battery level 0 updates many times a second. Now, leaving aside the fact that it isn’t very bright for a sensor which is critically low on battery to waste power like this, it seemed to provoke an error with openhab. I have to say that I can’t prove that this was the trigger event but it seems a heck of a coincidence. Openhab started reporting protocol errors. I have a bespoke application running on the rpi which is subscribing to z-wave events via MQTT.

So, the question is: Is it possible for me to have subscribed to protocol error events so that my application could intervene and kill/restart openhab?

[sihui]

@TimHaydnJones

I have openhab 1.8 running

According to your log you are running version 1.7.0. which is VERY old.
Before trying to solve any problems I would update to the latest openHAB version.

[TimHaydnJones (Tim Jones)]

Ah, that’s a fair point - I lost track of which rpi was which. I have 1.8 running on other rpis. Will do so asap. Thanks

[sihui]

@TimHaydnJones

Is it possible for me to have subscribed to protocol error events

Maybe this

Skript to read openhab logs

Hi there, I created a small script which allows parsing of the openhab logfiles and then pushes the result back with the rest api. This way I can automatically check my logs for errors and then send those through the pushover binding. (I always forgot to check the logs regularly ) Maybe this is useful for anybody else. Check it out on github! Log output: 2016-06-30 10:30:01.324 [INFO ] [org.openhab.model.script.Exec ] - 2 of 208 lines matched in /opt/openhab/logs/openhab.log 201…

is something you could use.