mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #1138] [Bug Report] Smart plug connected via Home Assistant went offline (Tuya auth expired... yeah, #818
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#818
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @maziggy on GitHub (Apr 26, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1138
Originally assigned to: @maziggy on GitHub.
Smart plug connected via Home Assistant went offline (Tuya auth expired... yeah, I know...).
Plug didn't come back after that was fixed (tried restarting the Docker container). Had to edit the switch to get it to see that it was online again.
Fairly minor at this stage though it has the potential to get annoying - and I imagine that eventually someone else will wind up with the same kind of problem.
Screenshot
Reporter Contact
Email: david@dswebhosting.net
System Information
Logs (sanitized): bambuddy.log
Submitted via BamBuddy Bug Report
@maziggy commented on GitHub (Apr 27, 2026):
First of all i strongly suggest to change your Docker netwrk mode to host - as per the docs.
I cannot see any errors in your logs.
Please upload a support package -> https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
@lunaticds commented on GitHub (Apr 27, 2026):
Heh, not completing a bug report still submitted a bug report (is that a bug in itself?);
I'd attempted to cancel it once I realised that it was trying to capture logs (unexpected but cool?). I didn't want to do that as I'd restarted to see if that got the connection back (it did).
Next time it happens I'll resubmit it before I do anything else.
I do clearly need to fix my timezone looking at that system info output.
Not changing the Docker network any time soon though; my needs are... complex..
Feel free to close it.
@maziggy commented on GitHub (Apr 28, 2026):
The bubble is exatly explaining what will happen.