Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error message

See original GitHub issue

Hi! i am running Home assistant (0.105.5) on Docker on a NUC. When i start the room-assistant i get this [Nest] 6 - 02/21/2020, 10:14:08 PM [ClusterService] Command failed: dig +short @231.0.0.333 -p 5353 -4 localhost. +14461ms What is this error?

i also get these in the log when staring addon:

*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>```

Issue Analytics

State:
Created 4 years ago
Comments:15 (7 by maintainers)

Top GitHub Comments

1reaction

hwikenecommented, Feb 23, 2020

Sorry for all spam! found the sensor and it works perfect!!

0reactions

hwikenecommented, Feb 23, 2020

I get this message in my log:`(node:6) UnhandledPromiseRejectionWarning: Error: Entity with id bluetooth-classic-40-9c-28-03-01-cc already exists! at EntitiesService.add (/usr/lib/node_modules/room-assistant/dist/entities/entities.service.js:43:19) at BluetoothClassicService.createSensor (/usr/lib/node_modules/room-assistant/dist/integrations/bluetooth-classic/bluetooth-classic.service.js:187:45) at async BluetoothClassicService.handleNewRssi (/usr/lib/node_modules/room-assistant/dist/integrations/bluetooth-classic/bluetooth-classic.service.js:86:22) (node:6) 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(). (rejection id: 1) (node:6) [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

Top Results From Across the Web

Error Messages: Examples, Best Practices & Common Mistakes

Useful error messages can keep users on your site and increase conversions. See examples and learn the best practices.

Error message - Wikipedia

An error message is information displayed when an unforeseen problem occurs, usually on a computer or other device. On modern operating systems with ......

How to Write Good Error Messages - UX Planet

1. Be Clear And Not Ambiguous. Write error message in clear and simple language. User should be able to understand the problem while...

Best 10 Examples And Guidelines For Error Messages

Best 10 Examples And Guidelines For Error Messages · 1. Keep language clear and concise · 2. Keep user actions specific and logical...

Error Message Guidelines - Nielsen Norman Group

Established wisdom holds that good error messages are polite, precise, and constructive. The Web brings a few new guidelines: Make error messages clearly ......