Brightness field is used in different ways

[alamers]

Describe The Bug: The documentation for the GET /v1.0/devices/{deviceId}/status mentions the field brightness twice, with different definitions. It looks like the motion sensor and contact sensor report a different type than the color bulb.

To Reproduce:

See documentation

Expected behavior:

Probably one of the brightness fields should be called differently. The way it is described now makes it very hard to integrate with this API from strongly typed languages such as Java (I am working on an OpenHAB implementation), as there are two types defined for the same field name.

Device Model: Motion sensor/Contact sensor/Light bulb.

[yjeanrenaud]

well spotted!

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

[nasa9084]

can we re-open this issue?

[nasa9084]

@donavanbecker

[nasa9084]

not close

[waku1123]

Im also having trouble with the same problem while developing in golang...

can we rename MotionSenser property like "brightness" to "dimness"???

[nasa9084]

@waku1123 btw, I wrote switchbot client for golang, which supports current brightness issue, use this if you want: https://github.com/nasa9084/go-switchbot

[waku1123]

@nasa9084 cool!!! This is exactly what I am looking for!

[yjeanrenaud]

no updates here, though?