Skip to content
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

ISSUE: UTF-8 not supported: Server does not support ENABLE #672

Closed
bschatzow opened this issue May 26, 2022 · 3 comments
Closed

ISSUE: UTF-8 not supported: Server does not support ENABLE #672

bschatzow opened this issue May 26, 2022 · 3 comments

Comments

@bschatzow
Copy link

Describe the bug
A clear and concise description of what the bug is.
Not sure if this is from the new Beta of HA or the new Beta of Mail and Packages.
Just started seeing this error in the logs
Environment (please complete the following information):

  • OS: [e.g. HassOS/Raspbian/CentOS]
    -HAOS 2020-6 Beta 1
  • Type of device: [e.g. RPi3/NUC/Synology]
    RPI4
  • Home Assistant version: [e.g. 0.105.5]
  • Hassio/Docker/Core?
  • Component version: [e.g. 0.1.2]

Logs
This error originated from a custom integration.

Logger: custom_components.mail_and_packages.helpers
Source: custom_components/mail_and_packages/helpers.py:544
Integration: Mail and Packages (documentation, issues)
First occurred: May 25, 2022, 7:46:40 PM (246 occurrences)
Last logged: 6:10:14 AM

UTF-8 not supported: Server does not support ENABLE

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
Please add emails in plain/text format if possible and applicable.

@bschatzow bschatzow added the pending Pending review label May 26, 2022
@firstof9
Copy link
Collaborator

Safe to ignore, it's just a warning.

@firstof9 firstof9 removed the pending Pending review label May 26, 2022
@firstof9
Copy link
Collaborator

Likely change it to a debug message next beta.

@firstof9
Copy link
Collaborator

This has been updated in 0.3.5-b1 to a debug message.

@firstof9 firstof9 pinned this issue May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants