Better debug for command exception - #60
Open
FrugalGuy wants to merge 2 commits into
Open
Conversation
add traceback to debug for command exception
Update __init__.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am noticing that my smart plug isn't working here, but works find in Home Assistant and in the Smart Life app.
The plug generates this pretty scant debug output:
With the updated code, you see this instead, which is somewhat better, I think, because you can see where the issue arose:
BTW, clearing the 3.3 protocol box eliminates the exception, but doesn't get the plug to work.
I notice that my plug is using 3.4 protocol, which looks like it's not supported, yet. I can't tell if the plug should work without the 3.3 box checked.
That's another issue, though. :-)