-
Notifications
You must be signed in to change notification settings - Fork 5
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
Unhandled message 'm': 14 #12
Comments
On Wednesday, November 10, 2021 1:54:20 A.M. CST RaghavRao wrote:
I was playing around with this today and got
```
WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 0}
WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 5}
WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 1}
WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 2}
WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 0}
WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 2}
WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 1}
WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 0}
```
Any ideas?
The code is a work-in-progress, reverse-engineering by me and many others. So
not all of the message traffic is understood. If a message is not understood,
it is logged as you see, but then ignored. So if you can get what you need,
you can just ignore the log.
On the other hand, if this message is needed by you, we have to add code.
Can you see if these are triggered by certain events -- like a button push?
Regards,
-Steve
|
The code is unneeded but I'd be happy to help figure it out.
I had just plugged in the color sensor when I got these messages.
On Wed, Nov 10, 2021, 10:09 Steven M. Robbins ***@***.***>
wrote:
… On Wednesday, November 10, 2021 1:54:20 A.M. CST RaghavRao wrote:
> I was playing around with this today and got
>
> ```
> WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 0}
> WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 5}
> WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 1}
> WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 2}
> WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 0}
> WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 2}
> WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 1}
> WARNING:data.HubMonitor:unhandled message: {'m': 14, 'p': 0}
> ```
>
> Any ideas?
The code is a work-in-progress, reverse-engineering by me and many others.
So
not all of the message traffic is understood. If a message is not
understood,
it is logged as you see, but then ignored. So if you can get what you
need,
you can just ignore the log.
On the other hand, if this message is needed by you, we have to add code.
Can you see if these are triggered by certain events -- like a button
push?
Regards,
-Steve
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUBDUZCBP76ET2HJIIMNO3ULKDJNANCNFSM5HXGPYGQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was playing around with this today and got
Any ideas?
The text was updated successfully, but these errors were encountered: