# New binding stops updating sensor values

**URL:** <https://community.openhab.org/t/new-binding-stops-updating-sensor-values/48074>\
**Category:** Bindings\
**Tags:** development\
**Created:** [July 19, 2018, 9:57pm UTC](https://community.openhab.org/t/new-binding-stops-updating-sensor-values/48074 "2018-07-19T21:57:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hans\_van\_den\_Bogert](https://community.openhab.org/letter_avatar_proxy/v4/letter/h/b5e925/32.png) [@Hans\_van\_den\_Bogert](https://community.openhab.org/u/Hans_van_den_Bogert)\
**Post date:** [July 19, 2018, 9:57pm UTC](https://community.openhab.org/t/new-binding-stops-updating-sensor-values/48074/1 "2018-07-19T21:57:39Z")

</div>

I have been banging my head for a while. I’ve created a new binding for Omnik Solar Inverters. It works fine most of the time. But after a couple of days (1+) it suddenly stops working. A simple restart openhab, or even of the binding is enough to get it working again.  
I’m clueless how to start debugging this without restarting the jvm first, and then the issue is of course gone. Am I misunderstanding how `scheduleWithFixedDelay` works?

So

- Could someone give a convenient way to debug current running process of an Openhab process living remotely in docker (yeah, I’m not making this easy..)
- If someone really has time to burn, here is the code: [openhab2-addons/addons/binding/org.openhab.binding.omnikinverter at omnikinverter · hansbogert/openhab2-addons · GitHub](https://github.com/hansbogert/openhab2-addons/tree/omnikinverter/addons/binding/org.openhab.binding.omnikinverter)

Much appreciated!

Hans

---

<div class="post-metadata">

**Author:** ![vbier](https://community.openhab.org/user_avatar/community.openhab.org/vbier/32/21467_2.png) [@vbier](https://community.openhab.org/u/vbier)\
**Post date:** [July 20, 2018, 5:17am UTC](https://community.openhab.org/t/new-binding-stops-updating-sensor-values/48074/2 "2018-07-20T05:17:17Z")

</div>

Looks like there is an exception thrown in your code. Wrap everthing in a catch try block, catch throwable and log something with error level to see if this is the case.
