You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: