Skip to content
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

enhancement request: trace flag for device_id #20

Closed
zxdavb opened this issue Sep 4, 2021 · 1 comment
Closed

enhancement request: trace flag for device_id #20

zxdavb opened this issue Sep 4, 2021 · 1 comment

Comments

@zxdavb
Copy link

zxdavb commented Sep 4, 2021

@ghoti57 it would be useful to be able to deterministically discover the evofw3 dongle's device_id.

My use case include scenarios where users have (or potentially have) more than one gateway, so that I can work out which is which without them having to tell my code that things are so.

I note it would also be useful to have this data even whilst having the device in a read-only mode, so sending a dummy packet is not preferred (and I can't be absolutely sure the packet I'm seeing wasn't from another dongle).

The obvious solution would be a traceflag, or to include this data in the !V response.

@ghoti57
Copy link
Owner

ghoti57 commented Dec 10, 2021

evofw3 0.7.1 includes a new command !I which reports local device class:id

I can't add it to !V because there's likely to be buffer overflow when working with branches

@ghoti57 ghoti57 closed this as completed Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants