-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Setup #7
Comments
Same issue here, setup fails |
Can you please update to the latest release (0.0.3) and report if it's still an issue? |
The setup appears to be working now after an update. Thanks!
…On Fri, Jun 28, 2024, 6:17 PM Harshit Sanghvi ***@***.***> wrote:
Can you please update to the latest release (0.0.3) and report if it's
still an issue?
—
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGYNAJHN3GUE5EEN34TCXB3ZJYDI5AVCNFSM6AAAAABIUO5OG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXHAYTIMJTGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Didn't work for me unfortunately. What can i do to help?
Failed setup, will retry: Error communicating with API: 401, message='Unauthorized', url=URL('https://api.monarchmoney.com/graphql')
2024-06-28 20:55:17.200 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'monarchmoney' at custom_components/monarchmoney/update_coordinator.py, line 36: self._api.load_session(filename=self._hass.config.path(SESSION_FILE)) (offender: /usr/local/lib/python3.12/site-packages/monarchmoney/monarchmoney.py, line 2499: with open(filename, "rb") as fh:), please create a bug report at https://github.com/sanghviharshit/ha-monarchmoney/issues
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
response = await handler(request)
File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
result = await handler(request, **request.match_info)
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 120, in post
await hass.config_entries.async_reload(entry_id)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1897, in async_reload
return await self.async_setup(entry_id, _lock=False)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1821, in async_setup
await entry.async_setup(self.hass)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/monarchmoney/__init__.py", line 18, in async_setup_entry
coordinator = MonarchCoordinator(hass, entry)
File "/config/custom_components/monarchmoney/update_coordinator.py", line 36, in __init__
self._api.load_session(filename=self._hass.config.path(SESSION_FILE))
2024-06-28 20:55:17.201 DEBUG (MainThread) [custom_components.monarchmoney.update_coordinator] Setting up coordinator
2024-06-28 20:55:17.201 DEBUG (MainThread) [custom_components.monarchmoney.update_coordinator] Getting first refresh
2024-06-28 20:55:17.539 DEBUG (MainThread) [custom_components.monarchmoney.update_coordinator] Finished fetching monarchmoney data in 0.339 seconds (success: False)
…On Fri, Jun 28, 2024, 18:34 Matt Blackmore ***@***.***> wrote:
The setup appears to be working now after an update. Thanks!
On Fri, Jun 28, 2024, 6:17 PM Harshit Sanghvi ***@***.***>
wrote:
> Can you please update to the latest release (0.0.3) and report if it's
> still an issue?
>
> —
> Reply to this email directly, view it on GitHub
> <
#7 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AGYNAJHN3GUE5EEN34TCXB3ZJYDI5AVCNFSM6AAAAABIUO5OG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXHAYTIMJTGI>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5QJQAIZU3FRRQR7L7G6N3ZJYFKDAVCNFSM6AAAAABIUO5OG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXHAZDIOJVGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Looks like authentication failure. Do you have 2FA enabled? |
I was able to get it working. Deleted the repo, scrubbed the file system
for any monarch files. Rebooted, redownloaded and logged in. Works fine
now!
Thanks!!
…On Sat, Jun 29, 2024 at 5:44 PM Harshit Sanghvi ***@***.***> wrote:
Looks like authentication failure. Do you have 2FA enabled?
—
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5QJQDFR7QDBNC3XVPMS2DZJ5IIHAVCNFSM6AAAAABIUO5OG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGM4DQNRWG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I have the same issue and error message. How did you scrub the file system for any monarch files? Is there a specific folder location I should be looking for? Appreciate any help. |
I had MM running for a few days. Unfortunately now the service isn't starting. I deleted and attempted to reconfigure the service and now it won't make any entities at all. Any Suggestions?
2024-06-01 14:33:09.688 DEBUG (MainThread) [custom_components.monarchmoney.update_coordinator] Setting up coordinator
2024-06-01 14:33:09.688 DEBUG (MainThread) [custom_components.monarchmoney.update_coordinator] Getting first refresh
2024-06-01 14:33:09.873 DEBUG (MainThread) [custom_components.monarchmoney.update_coordinator] Finished fetching monarchmoney data in 0.185 seconds (success: False)
The text was updated successfully, but these errors were encountered: