Mhh okay. But I still see this not as a bug. There seems to be something wrong with your connectivity.
Do you have trouble caused by the error in the log?
New Plugin [pimatic-vvo]
Mhh okay. But I still see this not as a bug. There seems to be something wrong with your connectivity.
Do you have trouble caused by the error in the log?
What i see as an problem is not the connectionproblem as itself. In my opinion there should be a shorter and clearer error message in the pimatic frontend.
@dk00000 said in New Plugin [pimatic-vvo]:
In my opinion there should be a shorter and clearer error message in the pimatic frontend.
Does the error message show up in the frontend at all? Looking at the code I think it is only logged
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Yes, only in the log file. I could do it like in the TV plugin and show a message in the frontend if the vvo service isn’t reachable.
I dont look at the logfile. I just look to the messages via the small button in the right corner of the header at the GUI. But maybe its the same?!?
Yes, that are errors, logged to the log file.
i believe i discovered a new bug:
warn [pimatic]: Keeping pimatic alive, but could be in an undefined state, please restart pimatic as soon as possible!
12:33:11error [pimatic]: An uncaught exception occurred: SyntaxError: Unexpected token >
at Object.parse (native)
at Request._callback (/home/pi/pimatic-app/node_modules/pimatic-vvo/vvo.coffee:115:21)
at Request.self.callback (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:186:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:1163:10)
at emitOne (events.js:77:13)
at Request.emit (events.js:169:7)
at IncomingMessage.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-vvo/node_modules/request/request.js:1085:12)
at IncomingMessage.g (events.js:260:16)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:923:12)
at nextTickCallbackWith2Args (node.js:511:9)
at process._tickCallback (node.js:425:17)
This is most probably a bug in pimatic or in a module, please report it!
version 0.0.6 released 2018-02-07
version 0.0.7 released 2018-02-14