@sihui, That’s all right. Hope to get you back testing asap. You provide very valuable information and it’s easy for me to enhance the binding based on that.
Errors are captured and binding immediately set to offline rather than outputting warning lines to log. “Unparseable” lines is one thing to cause this. This could be handled differently but imho the binding is there to capture warnings and not to produce more of them. I think there’s two ways to resolve this. One is to not immediately put binding state to offline and stop reading but to direct these to warnin log and let the binding continue reading in the next loop. The second is to try to cover all different log outputs and handle them correctly. The latter is what I’m after.
@pauli_anttila, thise are some wise words and I agree. I have to admit that I havn’t thought it this way while developing and distributing this. I saw your posting in IoT Matketplace topic and I second all of your comments. I asked similar questions in here: Developing and distributing own bindings. Hoped to get some guidance how to handle these things in future.
And yes, source code can be found at github. github.com/gitMiguel Please have a look there. Help is always appreciated!
PS Happy independence day! Finns rule 