oznu

> we cannot ask the developers to change thir plug-in names to make it easier for end users Plugin developers can set a "nice" display name: https://github.com/oznu/homebridge-config-ui-x/blob/master/package.json#L3

The child bridges and the main bridge use the same logging class and format the date using the built in `new Date().toLocaleString()` JavaScript method which decides how to format the...

> Maybe a LANGUAGE setting for the main bridge that isn't exported in the environment and therefor not passed on to the child bridges? Child bridges are spawned with [`child_process.fork`](https://nodejs.org/dist/latest-v16.x/docs/api/child_process.html#child_processforkmodulepath-args-options)...

I'd probably be more inclined to just replace `toLocaleString()` and use an ISO8601-like datetime format for the logs instead, eg: ``` [YYYY-MM-DD hh:mm:ss] ``` That way there is never ambiguity...

I updated my two of my arm-based test units (DS216j and DS120j) from `DSM 7.1-42661 Update 1` to `DSM 7.1-42661 Update 3` and could not replicate this issue. The package...

``` === npm audit security report === ┌──────────────────────────────────────────────────────────────────────────────┐ │ Manual Review │ │ Some vulnerabilities require your attention to resolve │ │ │ │ Visit https://go.npm.me/audit-guide for additional guidance │...

> sudo apt-get install inetutils-ping > apk add iputils --no-cache Both of these packages have been added to the base oznu/homebridge docker image.

Sure thing, at a glace the `devices` structure will be challenging as custom "keys" don't work with the automated form generation as per [this](https://github.com/oznu/homebridge-config-ui-x/wiki/Developers:-Plugin-Settings-GUI#user-defined-keys). ```json "devices": { "wifi": { "name":...

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2104282/comments/3 According to this the fix is in `6.8.0-60`.