Open DcR-NL opened 1 month ago
Hey there @eifinger, mind taking a look at this issue as it has been labeled with an integration (waze_travel_time
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
waze_travel_time documentation waze_travel_time source (message by IssueLinks)
How did you found out that the Waze integration was causing the issue? I am having the same error with SMTP (using SMTP2Go as mailhost), but i don't use the Waze integration.
By verifying my SMTP config to be functional in a fresh instance of the official container. Followed by duplicating my original container (copy data/config mount) and playing a little game of integration elimination until SMTP started working again.
When clicking the 'View known issues' link at the SMTP-component, i see that there are multiple issues since March. I think i will switch my remaining automations that were using mail, over to Pushover as that has been working flawlessly for me.
The problem
Whenever I enable Waze Travel Time, my SMTP integration stops working. Does it touch global certificates or SSL settings in any way?
Reproducible for me in this way:
52.366986222956314,4.89043329043077
, destination51.924500522056206,4.475371380080934
and regionEurope
;Failed to call service notify.mail_me. Unknown error
. See added logs.Solution:
What version of Home Assistant Core has the issue?
core-2024.5.5
What was the last working version of Home Assistant Core?
core-2024.5.4
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Waze Travel Time
Link to integration documentation on our website
https://www.home-assistant.io/integrations/waze_travel_time/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Result of step 5:
And when I try to reload the 'SMTP NOTIFY SERVICE' from the developer tools between step 5 and 6, I get:
Additional information
No response