Robert Klep
Robert Klep
Did it eventually recover, though? Previously, once the connection was gone, any subsequent requests would fail (even if the Easy was back online again).
It happens when the connection gets lost somehow. I guess I'll have to do a bit more experimenting :(
I did some more digging, but I can't reproduce this. However, it's difficult to reproduce, because I think it's related to the connection between the Easy and the cloud server,...
Thanks, I've added another fix to try to squash this bug: ``` npm i robertklep/nefit-easy-core -g ```
Interesting! Let's have it run for a few days to see how it behaves, if that's okay with you.
That's strange: after logging "connection error", it should immediately log "trying to restart the connection", which it doesn't. It should also mark the connection as being offline and not send...
I've been running a test program for a few days now, running the latest code, and it seems to pick up broken connections correctly after the backend returns back from...
@CaptainFS are you running the Github-hosted version of `nefit-easy-core`? The published version (hosted by NPM) is still "broken".
@CaptainFS make sure that if you have installed `nefit-easy-http-server` globally (`npm install nefit-easy-http-server -g`), you need to install `nefit-easy-core` globally as well. Tip: NPM knows how to install packages from...
@CaptainFS with what error, specifically? I've been running the HTTP server for about a week now, using the new code, and it's still working fine.