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

Obtain device name and cloud byte from HELLO_RESPONSE #322

Merged
merged 1 commit into from Mar 24, 2020

Conversation

felipediel
Copy link
Collaborator

If the cloud byte is active on RM Mini 3 0x5f36 and RM4 devices the user will need to perform a procedure to disable the cloud. If we save this byte, the automation platforms will be able to inform the user that this procedure is necessary.

I will take the opportunity to suggest saving the device name. It comes in the same packet. This will improve user experience, as it will be easier to identify devices after a discovery.

Copy link
Collaborator Author

@felipediel felipediel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is something that you may want to check.

Comment on lines +69 to +70
return device(host, mac, devtype, name=name, cloud=cloud)
return device_class(host, mac, devtype, name=name, cloud=cloud)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed something that I don't completely understand here. Why were we using kwargs? Backwards compatibility? In that case, let me know and I will keep the previous syntax. Otherwise, I don't see why not use args.

Copy link
Collaborator

@Danielhiversen Danielhiversen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Danielhiversen Danielhiversen merged commit 446496c into mjg59:master Mar 24, 2020
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

Successfully merging this pull request may close these issues.

None yet

2 participants