Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Problem you have encountered:
Customer encountered problem with a pod not being able to authenticate/connect to MQTT.
What you expected to happen:
It should be able to connect as it happened locally.
Other information (workarounds you have tried, documentation consulted, etc):
- The issue of the error in the end was in the utcno from datetime in python messing up loginc on utc. More specifically datetime.datetime.utcnow().timestamp() does not return timestamp in UTC but in local time. The customer had to use custom made functions to do this properly.
- What he asked was to be able to display more verbose errors when something goes wrong with MQTT, instead of just that it fails vaguely (see the error message here [1]).
---
[1] - 'mqtt: The connection broke or was closed by the client.'