Add support for SecureOn password#38
Conversation
|
Thanks! This looks great! CI fails, because the GitHub actions were outdated. I fixed this in the main branch. You can resolve this by updating your branch. My only concern is that I don’t have the hardware to test this. The tests use mocks. They are great for catching regressions, but they don’t prove the functionality actually works. Did you test this by waking up an actual machine that uses SecureOn? |
|
Hi @remcohaszing EDIT: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #38 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 43 55 +12
Branches 14 23 +9
=========================================
+ Hits 43 55 +12 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Is there a stand alone version that I can use the test it with a real device?! |
|
Hi @erkr example: |
|
Since it’s also a standalone script with no dependencies, you could even just download and run https://github.com/mib1185/pywakeonlan/blob/add-secureon-password-support/wakeonlan/__init__.py directly if that’s easier for you. |
|
@erkr In which format is the password configured on the device? as a 6 character long string or as hex? |
|
I will give that a try on my PC |
as 6 hex characters (standard magical packet plus 6 bytes) |
|
so from a UX perspective it would be ok to ask the user entering the SecureOn password in a format like a mac address (eq. ff:ff:ff:ff:ff:ff or ffff.ffff.ffff or ffffffffffff)? |
|
I think it would be better to ask for the password as regular characters, so But this is my gut feeling. Do we have another tool that uses a similar way to format the tuple/password? From an API perspective it may even be better to support a tuple in addition to a slash-separated string. The string format would still be nice for the CLI interface. |
@remcohaszing Thanks, that was manageable for me :-) @mib1185 Initially I thought it was failing, but once I added the broadcast IP argument it worked ! logged: WoL: 192.168.178.211 wakes COBRA Nice job! |
No, that won't work as SecureOn allows for 6 arbitrary HEX values (Exactly the same format as the MAC) |
|
Thanks! I really appreciate both the PR and the feedback ❤️ |
This adds support for adding a SecureOn password to the magic packet. The password is provided after a
/as delimiter (so the mac and password are a tuble). The main intention is to add support for WoL with SecureOn password to Home Assistant.