John
John
I saw also occasionally, but I'm unable to track it down to the cause. since a reload always worked for me, this doesn't seem to be a big issue after...
can't reproduce. does the message have an access level associated with it?
did you pass the URL arg to curl as posted above? as in this case the shell will run parts of it in background. you'd have to wrap the URL...
closed due to inactivity
could someone please go ahead and clearly determine whether it is related to ebusd update or csvs update? I'm pretty sure this has nothing to do with the ebusd version...
I've reverted https://github.com/john30/ebusd-configuration/issues/316 for the time being. looking at it more closely leaves quite some questions... please check if this eases the situation described here
does it work with netcat?? i.e. when using `echo "hex b5110101"|nc localhost 8888` instead
yes, I meant by using nc in the cronjob. you need to give an extra param to nc to not wait forever
in this case please check the ebus logging for anything unusual when the result is empty. maybe need to increase the log level
do you have writable messages at all? check with "ebusctl find -w"