Bridge will not start after upgrade 3.2.8

[ericlspencer]

My bridge service will not start after recent upgrade

hoobs@hoobs:/home/hoobs/.hoobs/etc $ grep : access.json "id": 1, "name": "xxx", "admin": true, "username": "xxx", "password": "xxxx", "salt": "xxxx"

"server": {
    "port": 80,
    "origin": "*",
    "autostart": 0,
    "home_setup_id": "X-HM://0023ISYWYHC6E",
    "polling_seconds": 5
"client": {
    "default_route": "status",
    "inactive_logoff": 30,
    "theme": "hoobs-light",
    "locale": "en",
    "temp_units": "fahrenheit",
    "country_code": "US",
    "postal_code": "65807"
"bridge": {
    "name": "HOOBS",
    "port": 51826,
    "pin": "031-45-154",
    "username": "3B:17:4D:01:25:C8"
"description": "",
"ports": {},
"plugins": [
"accessories": [
        "accessory": "Chamberlain",
        "plugin_map": {
            "plugin_name": "homebridge-chamberlain",
            "index": 0
        "name": "Garage Door",
        "username": "xxxxx",
        "password": "xxxxxx"
"platforms": [
        "platform": "orbit",
        "name": "orbit",
        "email": "xxxxx",
        "password": "xxxxxx",
        "plugin_map": {
            "plugin_name": "homebridge-platform-orbit"
"package_manager": "npm",
"system": "hoobs"

[askovi]

Please post your logs and follow the bug report template

[jmarshall2021]

I have the same issue. Before I checked here, I deleted all my plugins to see if a vanilla version would run, but no change:

{ "server": { "port": 8080, "origin": "*", "autostart": 0, "home_setup_id": "X-HM://0023ISYWYGD5L", "polling_seconds": 5 }, "client": { "default_route": "status", "inactive_logoff": 30, "theme": "hoobs-dark", "locale": "en", "temp_units": "fahrenheit", "country_code": "US", "postal_code": "91320" }, "bridge": { "name": "HOOBS", "port": 51826, "pin": "031-45-15X", "username": "5B:73:CA:EA:98:C8" }, "description": "", "ports": {}, "accessories": [], "platforms": [] }

[askovi]

@jmarshall2021 please post your logs

[9zero8]

I am having the same issue after updating. My logs are below:

10/21/2020, 7:09:40 PM HOOBS listening on port 8085. 10/21/2020, 7:09:42 PM assert.js:386 10/21/2020, 7:09:42 PM throw err; 10/21/2020, 7:09:42 PM ^ 10/21/2020, 7:09:42 PM AssertionError [ERR_ASSERTION]: Accessories must be created with a non-empty displayName. 10/21/2020, 7:09:42 PM at Bridge.Accessory [as constructor] (/usr/src/hoobs/node_modules/hap-nodejs/dist/lib/Accessory.js:1092:25) 10/21/2020, 7:09:42 PM at new Bridge (/usr/src/hoobs/node_modules/hap-nodejs/dist/lib/Bridge.js:26:28) 10/21/2020, 7:09:42 PM at new Server (/usr/src/hoobs/bridge/server.js:86:23) 10/21/2020, 7:09:42 PM at module.exports (/usr/src/hoobs/bridge/cli.js:47:20) 10/21/2020, 7:09:42 PM at Object. (/usr/src/hoobs/bin/hoobs:63:81) 10/21/2020, 7:09:42 PM at Module._compile (internal/modules/cjs/loader.js:1015:30) 10/21/2020, 7:09:42 PM at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10) 10/21/2020, 7:09:42 PM at Module.load (internal/modules/cjs/loader.js:879:32) 10/21/2020, 7:09:42 PM at Function.Module._load (internal/modules/cjs/loader.js:724:14) 10/21/2020, 7:09:42 PM at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) 10/21/2020, 7:09:42 PM at internal/main/run_main_module.js:17:47 { 10/21/2020, 7:09:42 PM generatedMessage: false, 10/21/2020, 7:09:42 PM code: 'ERR_ASSERTION', 10/21/2020, 7:09:42 PM actual: undefined, 10/21/2020, 7:09:42 PM expected: true, 10/21/2020, 7:09:42 PM operator: '==' 10/21/2020, 7:09:42 PM }

[rhuss2]

I am having exactly the same issue after updating:

10/21/2020, 7:41:25 PM HOOBS listening on port 8085. 10/21/2020, 7:41:26 PM assert.js:386 10/21/2020, 7:41:26 PM throw err; 10/21/2020, 7:41:26 PM ^ 10/21/2020, 7:41:26 PM AssertionError [ERR_ASSERTION]: Accessories must be created with a non-empty displayName. 10/21/2020, 7:41:26 PM at Bridge.Accessory [as constructor] (/usr/src/hoobs/node_modules/hap-nodejs/dist/lib/Accessory.js:1092:25) 10/21/2020, 7:41:26 PM at new Bridge (/usr/src/hoobs/node_modules/hap-nodejs/dist/lib/Bridge.js:26:28) 10/21/2020, 7:41:26 PM at new Server (/usr/src/hoobs/bridge/server.js:86:23) 10/21/2020, 7:41:26 PM at module.exports (/usr/src/hoobs/bridge/cli.js:47:20) 10/21/2020, 7:41:26 PM at Object. (/usr/src/hoobs/bin/hoobs:63:81) 10/21/2020, 7:41:26 PM at Module._compile (internal/modules/cjs/loader.js:1015:30) 10/21/2020, 7:41:26 PM at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10) 10/21/2020, 7:41:26 PM at Module.load (internal/modules/cjs/loader.js:879:32) 10/21/2020, 7:41:26 PM at Function.Module._load (internal/modules/cjs/loader.js:724:14) 10/21/2020, 7:41:26 PM at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) 10/21/2020, 7:41:26 PM at internal/main/run_main_module.js:17:47 { 10/21/2020, 7:41:26 PM generatedMessage: false, 10/21/2020, 7:41:26 PM code: 'ERR_ASSERTION', 10/21/2020, 7:41:26 PM actual: undefined, 10/21/2020, 7:41:26 PM expected: true, 10/21/2020, 7:41:26 PM operator: '==' 10/21/2020, 7:41:26 PM }

[pmppk]

Same issue, using the docker image.

[ericlspencer]

I deleted all my plugins and reinstalled them and it works

On Wed, Oct 21, 2020 at 4:33 PM jmarshall2021 notifications@github.com wrote:

I have the same issue. Before I checked here, I deleted all my plugins to see if a vanilla version would run, but no change:

{ "server": { "port": 8080, "origin": "*", "autostart": 0, "home_setup_id": "X-HM://0023ISYWYGD5L", "polling_seconds": 5 }, "client": { "default_route": "status", "inactive_logoff": 30, "theme": "hoobs-dark", "locale": "en", "temp_units": "fahrenheit", "country_code": "US", "postal_code": "91320" }, "bridge": { "name": "HOOBS", "port": 51826, "pin": "031-45-15X", "username": "5B:73:CA:EA:98:C8" }, "description": "", "ports": {}, "accessories": [], "platforms": [] }

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hoobs-org/HOOBS/issues/855#issuecomment-713889948, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALNH7GF27M6YVAAHMPHGV4DSL5HRNANCNFSM4S2HWIZA .

-- Sent from Gmail Mobile

[mkellsy]

It looks like our Docker Hub repo got corrupt somehow. I was able to rebuild and re-push a new image. However, we are abandoning the latest tag, so you must pull with the version like this.

docker pull hoobs/hoobs:3.2.8

[mkellsy]

We were using HB 1.2.3 by mistake. It was pulled. The HB version should be 1.1.6.

Related issue https://github.com/homebridge/homebridge/issues/2681

3.2.9 should fix your issues.

[rhuss2]

After updating docker image to 3.2.9, it still isn’t running, a new error:

10/22/2020, 5:57:22 AM HOOBS listening on port 8085. 10/22/2020, 5:57:23 AM No plugins installed. 10/22/2020, 5:57:23 AM AssertionError [ERR_ASSERTION]: The supplied username (undefined) is not valid (expected a format like 'XX:XX:XX:XX:XX:XX' with XX being a valid hexadecimal string). Note that, if you had this accessory already paired with the invalid username, you will need to repair the accessory and reconfigure your services in the Home app. Using an invalid username will lead to unexpected behaviour. at Function.AccessoryInfo.assertValidUsername (/usr/src/hoobs/node_modules/hap-nodejs/dist/lib/model/AccessoryInfo.js:198:26) at Function.AccessoryInfo.load (/usr/src/hoobs/node_modules/hap-nodejs/dist/lib/model/AccessoryInfo.js:164:23) at Bridge.Accessory._this.publish (/usr/src/hoobs/node_modules/hap-nodejs/dist/lib/Accessory.js:504:66) at Server.publishBridge (/usr/src/hoobs/bridge/server.js:193:21) at /usr/src/hoobs/bridge/server.js:162:53 at processTicksAndRejections (internal/process/task_queues.js:97:5) at async Server.start (/usr/src/hoobs/bridge/server.js:162:9)

[mkellsy]

Re-pull 3.2.9 there was an error pushing the layers.

[mkellsy]

I am closing this issue due to everyone except the op have reported that 3.2.9 is working for them.

To recap, to fix this either upgrade to 3.2.9 or re-pull the 3.2.9 image.