Hey and have had a quick poke around with this and it looks like there are some underlying issues with the reasonably old package and the base_url implementation. It was closed as stale with no resolution then. This was brought up 2 years ago on March 6, 2021. Result = self.fn(*self.args, **self.kwargs)įile '/usr/src/homeassistant/homeassistant/components/nzbget/config_flow.py', line 41, in _validate_inputįile '/usr/local/lib/python3.10/site-packages/pynzbgetapi/_init_.py', line 43, in _init_ĪttributeError: 'str' object has no attribute 'create_default_context' Integration: NZBGet (documentation, issues)įirst occurred: 3:31:15 AM (1 occurrences)įile '/usr/src/homeassistant/homeassistant/components/nzbget/config_flow.py', line 78, in async_step_userĪwait _add_executor_job(_validate_input, user_input)įile '/usr/local/lib/python3.10/concurrent/futures/thread.py', line 58, in run

Source: components/nzbget/config_flow.py:41 Example YAML snippet There's no YAML relevant to this integration.Īnything in the logs that might be useful for us? Logger: _flow NZBGet Link to integration documentation on our websiteĬan’t, as I can’t even finish the integration wizard. Home Assistant OS Integration causing the issue N/A What type of installation are you running? What version of Home Assistant Core has the issue?Ĭore-2022.7.3 What was the last working version of Home Assistant Core? I didn’t seem to have this issue with sonarr.

NZBGet is routed through nginx with a public LE certificate on a subdirectory (Not subdomain). When adding nzbget using the config flow an Unexpected error occurs.

Sonarr reverse proxy