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

Type Req / Hardware Join 1 & Range Test / Hardware Join 2 #26

Closed
jamesleesaunders opened this issue Apr 17, 2017 · 0 comments
Closed

Type Req / Hardware Join 1 & Range Test / Hardware Join 2 #26

jamesleesaunders opened this issue Apr 17, 2017 · 0 comments
Assignees
@jamesleesaunders
Labels
bug

Comments

@jamesleesaunders
Copy link
Owner

Investigate similarity or differences between:

  • Type Request & Hardware Join 1
  • Range Test RSSI Request & Hardware Join 2

Are they the same thing? Look at Desert Home notes again.
Look at commented out code in Device.py.
Look at messages dict in Base.py
Will a device actually join with type / RSSI request instead?

Fix broken range test reply code in Device.py
@jamesleesaunders jamesleesaunders self-assigned this Apr 17, 2017
jamesleesaunders added a commit that referenced this issue Apr 17, 2017
@jamesleesaunders
PEP formatting and notes for Issue #26.
d2c03b2
jamesleesaunders added a commit that referenced this issue Apr 18, 2017
@jamesleesaunders
Fix Issue #26 Type Req / Hardware Join 1 & Range Test / Hardware Join 2
7a2fe44
jamesleesaunders added a commit that referenced this issue Apr 19, 2017
@jamesleesaunders
Bump to v0.2.1
b406007 
* Fix Issue #19 Removed SQLite DB code - it was over complcating the class and would be superfuous if the developer wanted to use a different DB like MySQL.
* Fix Issue #26 Combining Type Req / Hardware Join 1 & Range Test / Hardware Join 2. 
* Partially addressed #5. Device.pl now has facility to send updates at regular intervals using Threads.
* Improvements to SmartPlug class.
* Improvements to Current Instantaneous Power and RSSI messages.
* Simpler terminology 'Power Demand' and 'Power Consumption'.
* Making more use of callback.
* Further PEP formatting.
@jamesleesaunders jamesleesaunders mentioned this issue Apr 19, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jamesleesaunders jamesleesaunders

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jamesleesaunders