-
Notifications
You must be signed in to change notification settings - Fork 290
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
"Config flow could not be loaded" / "bad marshal data" #2673
Comments
AMP is trying to import from the |
@danielbrunt57 Thanks for the reply, that makes sense but so far I've only used the Terminal & SSH add-on which doesn't have docker, so from some googling it looks like I need to go a level deeper. Are these the instructions I should follow? I'm running HA OS on a pi, if it matters. |
I'm using the Terminal & SSH add-on and I'm running Home Assistant OS on HA "Blue" ODROID N2+ and I have the |
The instructions you reference allow you to access the host via external SSH on port 22222 thus bypassing the need to run |
Same exact issue. I just did an upgrade to Alexapy (sudo pip install alexapy --upgrade), and restarted HA. Solved the issue, in case any others are running into this. |
IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug
After downloading from HACS and attempting to install the integration, the following error is shown:
To Reproduce
.storage
(pickle, config files), and restartExpected behavior
The setup config flow starts.
Screenshots
System details
const.py
or HA startup log): N/A (can't install) but observed with v4.13.7 and v4.13.8 from HACSpip show alexapy
in homeasssistant container or HA startup log): N/ADebug Logs (alexa_media & alexapy)
Please provide logs.
Note the logs above are without any AMP-specific logging added. If I add the
logger
config entry as per the link above, no errors are output at all since this is ERROR-level and comes from HA, not AMP. The FAQ should probably be updated to help users add logging for setup errors.Additional context
I don't know when this started, but AMP was previously working just fine and one day I noticed it stopped (my devices were unavailable). I deleted and attempted to reinstall the integration and this started. I've tried removing all traces of AMP including deleting from HACS and redownloading (with several reboots in between), but the error is the same. So either there is some kind of critical bug in AMP setup (unlikely since this has been going on for weeks and no one else has reported it) or there is some leftover file in my installation that I don't know about. The "bad marshal data" seems like a generic python issue that is usually resolved by clearing out
__pycache__
, but since I've tried deleting AMP and redownloading it I'm not really sure where else it could be storing these binaries.The UI error is the same as #2293, but the cause looks different so I'm creating a new issue.
The text was updated successfully, but these errors were encountered: