You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My usage of this app is with my homebridge plugin homebridge-deebot.
It is standard practice with homebridge plugins to use the homebridge logging function to prefix entries with a timestamp and the plugin instance name. For example:
If any dependency uses console.log then the entry is added to the homebridge log but without the timestamp and plugin name - which can sometimes confuse users as to which plugin is causing the entries - normally only an issue when something is going wrong.
My ideal scenario would be the ability to pass a logging function to this repo in the EcovacsAPI class, for example
can you please give me an example of what debug information of the library currently appears in the log of your plugin when started in debug mode 🙂
Or are you planing to run the plugin in the development environment (NODE_ENV=dev)?
(I already started a conversation on Discord yesterday. We can continue there if you like)
The feature request
My usage of this app is with my homebridge plugin
homebridge-deebot
.It is standard practice with homebridge plugins to use the homebridge logging function to prefix entries with a timestamp and the plugin instance name. For example:
If any dependency uses
console.log
then the entry is added to the homebridge log but without the timestamp and plugin name - which can sometimes confuse users as to which plugin is causing the entries - normally only an issue when something is going wrong.My ideal scenario would be the ability to pass a logging function to this repo in the EcovacsAPI class, for example
so I can pass the homebridge logger function to the class and it be used in replacement of your repo's default logging function.
My use case would really be:
undefined
or an empty function() => {}
Happy to discuss this more on discord if preferred!
Thanks!
The text was updated successfully, but these errors were encountered: