search

ebaauw / homebridge-deconz

Homebridge plugin for deCONZ
Apache License 2.0
134 stars 7 forks source link

Potentially stale api key #229

Closed lhari84 closed 2 months ago

lhari84 commented 2 months ago

Hi, I got an issue when preparing for HB 2.0: To avoid warning "invalid name charactristic", I've renamed all devices that contain invalid characters and re-exposed all of these devices by removing them from HB's cached devices list once. So far so good, but one device makes troubles, it's the Phoscon Gateway itself: I've renamed it (from "Phoscon-GW" to "Phoscon GW") on side of deCONZ, on side of Homekit and HB, but still warning in HB logs: image

I guess this is because in device properties, the old name still stucks here: image

So, if i do the trick of re-exposing by deleting this device from HB cache, it causes the following problem/warning and I have no idea to get rid of it: image The one charactaristics-warning goes, but this one comes. Have tried it several times with different order of actions, but always the same result. For now, I have restored the snapshot where everything works fine with latest HB stable, so I could give it another try if there is any solution. Thank you very much in advance.

ebaauw commented 2 months ago

See #22. If you un-expose the gateway (using ui) instead of deleting the cached accessory, Homebridge deCONZ will delete the old API key.

lhari84 commented 2 months ago

See #22. If you un-expose the gateway (using ui) instead of deleting the cached accessory, Homebridge deCONZ will delete the old API key.

Thank you so much, this solved my issue! Sorry for not checking closed issues, Just googled it and have not found anything this way.