username "like a MAC address" error, solution on readme doesn't work.
See original GitHub issueHey All,
Trying to set this up for the first time and am running into a problem. I’ve tried the solution listed in the readme but still nothing.
iOS device has gotten your Homebridge username (looks like a MAC address) “stuck” somehow, where it’s in the database but inactive. Fix: change your username in the “bridge” section of config.json to be some new value.
I’ve tried changing the username in the config.json file but still nothing.
`Mac-mini:~ dirk$ homebridge [5/19/2016, 8:56:39 PM] Loaded plugin: homebridge-lifx [5/19/2016, 8:56:39 PM] Registering accessory ‘homebridge-lifx-bulb.LIFxBulb’ [5/19/2016, 8:56:39 PM] Registering platform ‘homebridge-lifx.LIFx’ [5/19/2016, 8:56:39 PM] — [5/19/2016, 8:56:39 PM] Loaded plugin: homebridge-nest [5/19/2016, 8:56:39 PM] Registering platform ‘homebridge-nest.Nest’ [5/19/2016, 8:56:39 PM] — /usr/local/lib/node_modules/homebridge/lib/server.js:184 throw new Error('Not a valid username: ’ + username + ‘. Must be 6 pairs of colon-’ + ^
Error: Not a valid username: undefined. Must be 6 pairs of colon-separated hexadecimal chars (A-F 0-9), like a MAC address. at Server._loadConfig (/usr/local/lib/node_modules/homebridge/lib/server.js:184:13) at new Server (/usr/local/lib/node_modules/homebridge/lib/server.js:44:23) at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:26:16) at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22) at Module._compile (module.js:409:26) at Object.Module._extensions…js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Function.Module.runMain (module.js:441:10) at startup (node.js:139:18) at node.js:968:3 Mac-mini:~ dirk$ `
I also tried searching previous topics but nothing so far. Anyone have any advice?
Issue Analytics
- State:
- Created 7 years ago
- Comments:20
Top GitHub Comments
Config.json! What you usin? Mac, Windows, Linux or raspberry pi?
This issue has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this issue was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.