I'm a new hubitat user and I've been putting together all of my home automations after migrating away from Wink. In the last couple of days, I've been adding my Hue lights and incorporating them into the hubitat ecosystem.
Last night, I was running a routine from Alexa and my hue lights flashed then went out. When I went to investigate in the Hubitat portal, I noticed that the Hue integration app had disappeared. This morning, I've been trying to recover and now I'm getting errors. In particular, when I add the Hue integration back, the integration appears to work and the bulbs show up in the bulb discovery process, but when I complete the process, the bulbs never show in the portal. If I look at the logs, I see the following error in the logs:
[app:258] 2020-04-25 10:39:48.294 am [error] java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI on line 566 (updated)
I also noticed that in my logs, its hows me several Hue Integration "rollups" for the logs. I've attached a screenshot of my logs which shows both this error and the duplicate "Hue Bridge" instances. All of the lights and the hub work fine when using the hue app, so the issue appears exclusive to Hubitat.
I've rebooted the Hubitat several times but nothing I've tried as worked. Any suggestions on how I can clear this up? Thanks!! logs|690x436
1 Like
Did you restart your hub at some point? If Hubitat detects a bad database at restart, it will restore from the last known good version. This is more likely to happen if you suddenly restart, e.g., by pulling power instead of going to Settings > Restart or as part of a regular firmware upgrade. Rarely, these can happen for no apparent reason at all. A soft reset and a restore of "good" database you happen to have may help with that (the hub keeps a few of its own, but downloading them locally is always a good idea too). I don't want to suggest anything too extreme, but that is one possibility.
Thank you for the response @bertabcd1234!
Now that I think about it, I was reorganizing the powerstrip in my media cabinet that power the Hubitat and I did not power the hub down first before I unplugged it... That was earlier in the day, long before I had issues, but the answer to your question is yes, I did power it down and have a hard restart.
Sadly, I haven't backed anything up yet since I'm still getting it all put together -- rookie mistake I suppose! But looking at it, there is a backup from yesterday. Let me try and restore that to see if it's any better than what I have. Thanks for the suggestion!
1 Like
Ok reporting back on this...
I did have a backup from yesterday where the Hue bridge was still functioning. I lost quite a bit of my configuration but it did allow me to recover the Hue portion which is what counts. Thanks for the suggestion @bertabcd1234 and now I know how valuable backups can be 
2 Likes
Glad you got that working! Hopefully it was just the sudden power loss that caused this (still rare but does happen). Some people put their hub on a UPS to avoid this (there are a few threads with recommendations), but in general, "polite" shutdowns or restarts can help avoid that otherwise--and having a local backup, as you've discovered, is always good as well! Some people have also automated that (also something I've read about here on a couple threads you can probably also find with some searching; I'm too lazy to do this and just download one occasionally). Do note that currently, local backups don't include Z-Wave device pairings and may have mixed behavior with Zigbee (depending on whether you restore it to the same hub or a different hub); therefore, these aren't 100% full backups, but are still good for LAN devices and automations (at least seeing what you have configured) regardless. They also don't include hub firmware, as noted on the backup page.
If you notice this continuing to happen and aren't sure why, you might have a bigger problem that would warrant the inclusion of official Support. Otherwise, hopefully that's all it was!
1 Like
