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.

Sign up for GitHub

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

Jump to bottom

device.ready not always a boolean as documented #21

Open
robertklep opened this issue Dec 18, 2022 · 1 comment
Open

device.ready not always a boolean as documented #21

robertklep opened this issue Dec 18, 2022 · 1 comment

Comments

@robertklep
Copy link

When a device is created, the device.update event is emitted multiple times.

The ready property of the device object that gets passed seems to be true or null, the latter not being a boolean as documented.
@jeroenwienk
Copy link

The update events are expected because during device init some properties are updated so an update event is broadcasted. Ready being null just means it hasnt been touched yet so either null or false can be treated as not ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@robertklep @jeroenwienk