ebaauw / homebridge-deconz

Homebridge plugin for deCONZ
Apache License 2.0
135 stars 6 forks source link

Two gateways with phoscon/deConz - How to "ui" into the second? #176

Closed bubffm closed 9 months ago

bubffm commented 9 months ago

Following situation after migrating from homebridge-hue to homebridge-deconz:

I have two gateways (raspberry's) with raspbee/deconz running. Only one of them has Homebridge / homebridge-deconz installed (same way as it was previously with homebridge-hue). Devices from both gateways are being properly exposed in homekit.

But: I can perfectly "-ui" into the gateway with the homebridge installed to change loglevels etc. but I dont seem to be able to access the other gateway (the one without homebridge).

Any way t oget around this? I dont really want to install homebridge on the second device.

Many thanks

ebaauw commented 9 months ago

ui get /gateways lists the gateways. Then use ui get /gateways/id/devices to list the devices for a given gateway.

bubffm commented 9 months ago

Many thanks. That gave me the accessories of the second gateway. I can update devices.

Now trying to put LogLevel 0 against the second gateway. Based on your example in dynamic config, I use ui-D put /gateways/ID/settings '{"logLevel": 0}

However this does not return nything.

ebaauw commented 9 months ago

The /settings is only needed when calling the API directly through curl or Postman. It’s just ui -D put /gateways/id’{"logLevel": 0}’.

bubffm commented 9 months ago

I tried that as well. this gets me stuck on that little "arrow" out of which I can only exit via CTRL+C 'ui -D put /gateways/id ’{"logLevel": 0}’. Response: '>'

Bildschirmfoto 2023-10-09 um 11 52 55

might a have missed a space between gateways and ID. But that gives me:

Bildschirmfoto 2023-10-09 um 11 57 47
ebaauw commented 9 months ago

Your single quotes don’t match. Make sure they’re not beautified.

bubffm commented 9 months ago

Oh, dear... Corrected that one, but different Error message now. Typed manually into terminal to avoid further beautifications.:

Bildschirmfoto 2023-10-09 um 12 09 07
ebaauw commented 9 months ago

You put a space in between the resource, causing ui to see the second part as the body. This is invalid, as JSON numbers don’t allow leading zeroes, so the parser expects a space or end of input at position 1, after the 0 at position 0.

bubffm commented 9 months ago

Here we go! Thank you very much!