Marcus Wittig
Marcus Wittig
``` node: …/src/binding.cc:186: static void Pcap::cb_packets(uv_poll_t*, int, int): Assertion `status == 0’ failed. ``` I think, socket errors need to be properly handled similar to the cases reported earlier. See...
LTS support has been switched to v8 and as part of this npm v3 is shipped (peerDependencies are no longer supported). Regarding the use of npm v3 further testing is...
See https://forum.pimatic.org/topic/4724/1-wire-hall-sensor
Pimatic should provide protection against brute force login attacks. See also https://forum.pimatic.org/topic/2385/bruteforce-login-failed-protection
Starting point of the discussion: https://forum.pimatic.org/topic/1821/battery-type-for-variables-device Follow-up on Hangouts - with the idea of providing a template mechanism as part of pimatic M. Wittig Ja, stimmt. Ich habe das "custom"...
See also https://forum.pimatic.org/topic/2927/date-expression-in-variabledevice/6
Possibly make it configurable https://forum.pimatic.org/topic/978/change-the-average-value-from-5-to-1-min
Steps to repoduce: ``` curl -X GET --user "user:wrongPassword" https://hostnameOrIP/api/devices/someDeviceId ``` This will raise the following exception (**sent via response body**, no log message!!!): ``` TypeError: Cannot read property 'set'...
See also https://forum.pimatic.org/topic/945/pimatic-dewpoint-device-doesn-t-update/
To keep pimatic 0.9 inline with supported packages we should update to request-promise@4 - https://www.npmjs.com/package/request-promise#migration-from-v2-to-v3 - https://www.npmjs.com/package/request-promise#migration-from-v3-to-v4