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

Deprecate V_ID? #1285

Open
flatsiedatsie opened this issue Apr 24, 2019 · 2 comments
Open

Deprecate V_ID? #1285

flatsiedatsie opened this issue Apr 24, 2019 · 2 comments

Comments

@flatsiedatsie
Copy link

I noticed the V_ID property.

V_ID 42 Optional unique sensor id (e.g. OneWire DS1820b ids) S_TEMP

Only the S_Temperature uses it, and it seems designed for a specific Dallas hardware type.

I wouldn't even know how to implement it in my plugin.

More importantly, if you wanted to have insight into the different sensors, wouldn't it make more sense to present each one as a unique child? Wouldn't that be more in line with how most MySensors things work?

Perhaps I misunderstand its value/use.

@flatsiedatsie
Copy link
Author

Those links haven't really changed my opinion.

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