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

[Feature request]: Add a mandatory device_type field #19268

Closed
fede843 opened this issue Oct 12, 2023 · 3 comments
Closed

[Feature request]: Add a mandatory device_type field #19268

fede843 opened this issue Oct 12, 2023 · 3 comments
Labels
feature request Feature request stale Stale issues

Comments

@fede843
Copy link

fede843 commented Oct 12, 2023

Is your feature request related to a problem? Please describe

There is no reliable way to determine if a device is capable of routing traffic or not.
The common accepted rule in the community is that battery devices are end devices, which probably it is 100% accurate.
Then all wired devices without neutral are considered end devices, and the wired devices with neutra are routers. And this is not accurate. It fits most of cases, but not all.
I would really like to be able to commit myself to buy a product knowing exactly before hand if it can act as router or not.

Describe the solution you'd like

My proposal is to have a mandatory field device_type with 4 possible values: end device, router, coordinator and not available yet.
When a contributor adds a new device it is simple enough to populate the field accordingly. I does not require any extra effort really.
For the already existing devices not available yet should be used to kickoff. Then the community naturally can help with it. The completeness won't be happening in one day, but eventually it will grow.
I think it worth the shot.

Describe alternatives you've considered

Search in internet to see if someone claims the device is router or not.
There is no much else you can do really, besides the common accepted rule mentioned above.

Additional context

The original discussion: #19255
Another related request for blakadder database: blakadder/zigbee#1051

@fede843 fede843 added the feature request Feature request label Oct 12, 2023
@blakadder
Copy link
Contributor

There's a supports: field that can be filled with that information yet community isn't updating it

@fede843
Copy link
Author

fede843 commented Nov 13, 2023

Hi. What is the type field? What is it for?

Copy link
Contributor

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days

@github-actions github-actions bot added the stale Stale issues label May 12, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Feature request stale Stale issues
Projects
None yet
Development

No branches or pull requests

2 participants