z-wave.me

I don't have it running under gdb all the time. Is there a way I can do that and still run it as a background process?

Got a crash without my HTTPDevice plugin activated.
Now installed monit to auto restart z-wave-server if it crashes.

Any update on this issue?

@PoltoS - my apologies for taking so long to response to you request for examples. I've put together all the details I think you'll need in the attached. Of course I don't know if a different format of response is what's causing the crash - let me know if you have a debug version with extra logging ...

And died again - I've disable my HTTPDevice plugin as that's almost certainly causing the crashes. Shame about that - if you can fix this that's great, otherwise I'll have to consider checking alarm status in another process and then changing a device in z-wave.me process. Won't have time for the re...

If just crashed again, but last time it took a few days before crashing.
The request and response is running every minute - capturing the state of my alarm (home/away)

I attach the details of the crash that I've just caught on my system, with gdb running as suggested. I'm using version v2.3.6, build 28-09-2017 15:29:18. I've had a few crashes since moving to v2.3.6, for this one and the other crash where I've checked the log file, the last line was an http request...

That's very interesting. I've been having crashes too and I'm using a module based on HTTPDevice which includes dynamically generated URLs based on previous messages.

Upgrading to 2.3.6 did the trick. Thanks for the advice.

I don't have a public example. But here's some more information: - Wikipedia article on chunking in http 1.1. https://en.wikipedia.org/wiki/Chunked_transfer_encoding - Example using node js and http.request with chunking, search for chunk on https://nodejs.org/en/docs/guides/anatomy-of-an-http-trans...