I am trying to use hostnames, as a lot of the devices I am trying to track have mac address randomisation, which means I cannot use the MAC or set a static iP. I am using Pi-hole as DNS which means I can resolve local host names.
When I restart my homebridge, the correct state of my devices are shown, but as soon as one disconnects or connects I get the following error:
_(node:11510) UnhandledPromiseRejectionWarning: TypeError: e.getMessage is not a function
at PeopleProAccessory.pingFunction (/usr/local/lib/node_modules/homebridge-people-pro/src/accessory.js:251:75)
(node:11510) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11)
(node:11510) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code._
The occupancy (or motion) doesnt update after this.
I am trying to use hostnames, as a lot of the devices I am trying to track have mac address randomisation, which means I cannot use the MAC or set a static iP. I am using Pi-hole as DNS which means I can resolve local host names.
When I restart my homebridge, the correct state of my devices are shown, but as soon as one disconnects or connects I get the following error:
_(node:11510) UnhandledPromiseRejectionWarning: TypeError: e.getMessage is not a function at PeopleProAccessory.pingFunction (/usr/local/lib/node_modules/homebridge-people-pro/src/accessory.js:251:75) (node:11510) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11) (node:11510) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code._The occupancy (or motion) doesnt update after this.