Closed TheOneOgre closed 5 months ago
Have you tested on a non dev install of HA? I am on the latest (non dev) and just did Configure with changing some options and no issue.
I know a long time ago users had to manually delete files left over from an uninstall. It wasn't this error but worth a shot. We've had the unique id warning for awhile but not with a stack like this.
Thanks for the quick response. I made sure all files were removed upon removing the integration, everything was deleted properly, the only remnants I found were in /.storage/.blueiris, which I deleted, that did not fix the issue.
Reverting back from dev to main branch allows the config flow to perform properly, so there seems to be something breaking in one of the latest dev releases.
Excellent! Can reopen if something crops up but will chalk it up to a dev bug.
Excellent! Can reopen if something crops up but will chalk it up to a dev bug.
So with that being said, should it be reopened if it stays an issue with the dev branch for x number of days/release? Or should it only be reopened if it persists into a stable release?
So I actually looked into that last night and meant to reopen this earlier. First off, I don't understand what all is going on in the setup code for this integration and have avoided touching it as I believe a lot of work is being done manually vs letting HA logic handle it. Will defer to @elad-bar on that.
@elad-bar I see your shinobi integration doesn't utilize a config_flow_manager file. Not sure the work involved but should this one move away from that? Thanks as always.
It is still the same issue with a current beta release. Thanks for your efforts :)
Core 2024.6.0b4
Some related info here: https://community.home-assistant.io/t/configflowhandler-and-optionsflowhandler-managing-the-same-parameter/365582/28
Gut feeling (as I mentioned above) is that things need reworked to let HA handle a lot of the config management logic. A band-aid could be adding unique_id to the ConfigEntry here: https://github.com/elad-bar/ha-blueiris/blob/master/custom_components/blueiris/managers/config_flow_manager.py#L238 But I am not positive yet if there is a valid 'unique_id' that would work and not mess things up. Even if it was a new guid each time. All of this (creating new ConfigEntry objects) may be why the integration is frequently deleting and recreating entities.
This is the part of this integration I've tried to wrap my head around but never have been able to :(
Hi, Just to chime in here with a "Mee too". I am in the process of moving from AgentDVR to BlueIRIS to see if the resource use is better (circa 20 camera's) I however came across this same error code when trying to integrate with HA.
Let me know if I can help test any fixes.
Thanks
Just adding some information here that may help others having the same issue.
In the file /root/config/custom_components/blueiris/managers/config_flow_manager.py
About line 238 there is a function definition that appears to be missing a now mandatory option. I manually added a line as shown below, and then restart HA. After that, the Blue Iris integration completed its install and looks like it is working.
async def _update_entry(self): try: entry = ConfigEntry( version=0, minor_version=0, domain="", title="", data=self._data, source="", uniquie_id="", ### This is the line I added options=self._options, )
I don't have the skills to pull this apart properly and work out exactly what should be on that line, but setting something, even just a blank value appears to have worked. I was also going to try setting it to a GUID of some sort, but as it worked with a blank value, I've left it at that on my system.
Hopefully I haven't caused a time-bomb in the depths of HA :). Any feedback welcome.
Thanks @AaronPower2035 - please see my comment two posts above yours lol
I played around last night trying to change the logic to what HA really wants now (get rid of a lot of the manual work) but so far no luck. It really is what is needed though. Best bet may be to scavenge some of @elad-bar 's logic from the shinobi integration.
In the meantime, I'll release a version with the band-aid here in a bit just to get it back in a usable state.
The release with the fix is out there. Thanks all for your patience and have a good weekend!
Will close this but create a new wishlist ticket.
Was having issues with the integration showing 500 error, tried reinstalling but am running into the same config flow error. Have tried completely deleting and re-installing from HACS to no avail. Below is the error shown in the system log.