Bridge found at incorrect address - no lights found

[tomkeldor]

[MacOS]

I’m facing problem in version 2.0.1 that probably somewhere is old config.json from version 1.x and it has old IP address of bridge. I tried to use force, host, ip options with setup but none worked. On Windows deleting configuration file helps because it allows you to run fresh dmx-hue setup and just click the bridge button and repeat the command to enter configuration process.

So the question is, where on MacOS this file is being created or should be created? I don’t remember the path from last year usage probably on different device and can’t find on current one.

[sinedied]

On Mac OS the config file is located in ~/Library/Preferences/dmx-hue-nodejs/

Running dmx-hue setup --force forces a new bridge search and configuration from scratch though.

[tomkeldor]

Thanks I will check this later when have access to MacOS. On a side note I still think the process of switching bridge between devices isn’t user friendly. At least it would be useful to have this mentioned in readme.

The solution I found now to be working, but within the same OS (in this case Windows) is to copy config.json so dmx-hue on new device use same bridge right away without setup thanks to the same user property hash and adjusted bridge address if necessary.

[tomkeldor]

@sinedied please look below on this example: Config file was at Macintosh HD/Library/Preferences/dmx-hue-nodejs (had to create myself). Also I have successfully found lights from Entertainment area API used by Soundswitch. So it’s really weird I got “No lights found” response after ensuring that configuration file has bridge IP confirmed through MAC address and IP using arp -a command from device connected to same WI-FI router the bridge is.

[sinedied]

If dmx-hue setup --force fails, that means it's unable to locate your bridge automatically. In that case you would need to use --ip to set it manually, along with the --force as you already have an existing config file.

I'm using https://www.npmjs.com/package/node-hue-api to communicate with Hue lights, so there's nothing I can do if your bridge or lights can't be found by this library.

[tomkeldor]

You might be right, at the end at the first place with Windows device it shows lights like a charm with existing configuration file as long as bridge IP is correct. At second location and where I tried to run it on MacOS Hue mobile app showed different address than it was in fact. Well, I hope that network setup is the problem and using another router should be fine.

[tomkeldor]

Reopening this because I really hate the user experience of this (very usefull) software and have no idea what I'm doing wrong. Tried on 2 Windows 10 OS and one Mac OS and the result is same as above. Also important thing is there were previous versions of dmx-hue installed on some but after trying to just reuse them with dmx-hue command it gave authorization error so the connection between the dmx-hue app with the saved clientId wasn't working anymore and you really need to have this pushing button on the bridge done to create this connection on each OS and device. I don't know what's under the hood of creating this authorization with bridge but each time I return to this it makes problem. How can it be changed to be more user-friendly?

[calino13]

Hello, I have the same problem with my Windows 10 machine. I used a new bridge which is up to date. I can use an old config-file an put in "C:\Users\CS\AppData\Roaming\dmx-hue-nodejs\Config", then I can at least find the bridge but I get an authorization error "Unauthorized user". So it doesn't help. When I use an older bridge which wasn't updated since at leasts 2021, it works. Does anyone have a solution for this? How to get connected with the up-to-date Hue bridge?