Replies: 6 comments 10 replies
-
|
Lol, I thought everyone is done with this project so when I made changes I never thought about up-streaming them. Yes, they work, but with a lot of unnecessary changes. I've been running Climate/Leak and Contact V2 sensors for a while and they seem to be quite stable. The chime is newly added and I haven't figured out a good way of using it, but it should work. It looks like you are re-starting your interests in these, so maybe let me cleanup my change and make a cleaner pull request? |
Beta Was this translation helpful? Give feedback.
-
|
I’ve recently gotten back into some other GitHub projects, and realized I should dust this off and at least get new GHCR builds and any changes I possibly could. That made me realize I should replace the long dead batteries in all my sensors, blah blah blah… so yeah, some renewed interest. Would love a cleanish PR against the devel branch taking any good updates. Home Assistant still links to the project, so I know some people are still using it aside from us. :) |
Beta Was this translation helpful? Give feedback.
-
|
I bought some climate and leak sensors a while back but haven't gotten around to making them work. What is required to use the new sensors? I do have v2 motion and contact sensors though and those work just fine. |
Beta Was this translation helpful? Give feedback.
-
|
Decided to take another quick look at this. I found the firmware upgrade project from @AK5nowman. I know nothing about c# projects but I managed to get it built. I have no idea how to run it though. What argument should be passed as the device path? Not much of a windows user here! If full climate/leak/etc sensor support is desired though, then I'd actually like to try porting the upgrade app to python and including it in this repo instead. |
Beta Was this translation helpful? Give feedback.
-
|
I already made a python version while I looked into this. Currently it's
private but I can make the repo public if you'd like to give it a try.
…On Tue, Mar 4, 2025, 09:39 Nathan Bahr ***@***.***> wrote:
Decided to take another quick look at this. I found the firmware upgrade
project from @AK5nowman <https://github.com/AK5nowman>. I know nothing
about c# projects but I managed to get it built. I have no idea how to run
it though. What argument should be passed as the device path? Not much of a
windows user here!
If full climate/leak/etc sensor support is desired though, then I'd
actually like to try porting the upgrade app to python and including it in
this repo instead.
—
Reply to this email directly, view it on GitHub
<#75 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZNWD4J42XPD7ALNWDEL332SXQMTAVCNFSM6AAAAABYJZICG2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZZGE3TCMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Nice! I've got a second dongle just sitting in the drawer. So yeah, I can give it a try and see if it'll upgrade and work. |
Beta Was this translation helpful? Give feedback.
-
|
Oh! I’d love the Python version as well. I’m primarily on Linux for my stuff and that’s easier to use. Don’t mind adding it to this repo either (or just linking in readme), though definitely don’t want to automate the upgrade with the current risks and limitations. |
Beta Was this translation helpful? Give feedback.
-
|
ok, it's public now: https://github.com/HclX/WyzeSenseUpdater. I've verified this with more than 5 dongles and they all work. I do want to remind there are chances to brick so proceed with caution. |
Beta Was this translation helpful? Give feedback.
-
|
I finally got around to giving your updater a try. It worked beautifully! Thank you! Also on the topic of V2 sensors. I see your repo has updates for the new message formats. Do you have plans to open PR for that? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, flashing firmware erased all settings means your previously paired
sensors are gone. You need to re-pair it. And the new firmware works for
both v1 and v2 sensors.
I do plan to upstream my change, but it's too messy and I need cleanup but
haven't got a chance to look into it.
…On Fri, Mar 14, 2025, 15:25 Nathan Bahr ***@***.***> wrote:
I finally got around to giving your updater a try. It worked beautifully!
Thank you!
This was on my second dongle that I wasn't using and I have a couple
questions.
I would assume that the new firmware does not interfere with the older
sensors correct?
Also, do I need to re-pair all of the previous sensors after flashing?
I am debating whether or not to spin up a second W2M instance for the new
sensors, or if I should go ahead and flash my main dongle.
Also on the topic of V2 sensors. I see your repo has updates for the new
message formats. Do you have plans to open PR for that?
—
Reply to this email directly, view it on GitHub
<#75 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZNWD77BBFNCLVKQXAAOA32UNJODAVCNFSM6AAAAABYJZICG2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJQGYYTMMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
That's what I figured. I think for now I will just run a second instance. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I already started working on it, so you might not want to waste your
time:)
…On Sat, Mar 15, 2025, 15:19 Nathan Bahr ***@***.***> wrote:
That's what I figured. I think for now I will just run a second instance.
I might take a look at bringing in the changes from your fork if you don't
mind. I don't really plan on doing it right away but if I find time it'd be
nice to make use of these extra sensors.
—
Reply to this email directly, view it on GitHub
<#75 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZNWD4OXQ4EKWLURWEQWZL2USROTAVCNFSM6AAAAABYJZICG2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJRGI2TAMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Sounds good to me. Thanks! I look forward to giving it a try when it's ready. |
Beta Was this translation helpful? Give feedback.
-
|
hey, i got my first pull request created. I'd probably won't apply it directly to release branch, but this should enable everyone to work on top of it if they want. My tested scenarios are limited so would prefer more verifications. |
Beta Was this translation helpful? Give feedback.
-
|
@nabahr I think I accidentally opened two pull requests, they are identical so feel free to close the other one. |
Beta Was this translation helpful? Give feedback.
-
|
Merged into devel branch and container. I did notice we need to update the readme to remove the invert_state option. There was also a lint failure with the merge. If either of you have time to poke, in particular I'd like to make sure it works against a non-upgraded bridge, along with an HMS bridge. Be best to not break anyone already using it should they update. I'm going to be a little busy for the next couple weeks, but will try to poke at things as I can. So watch for any commits to devel before spending time on updates/fixes. Also hoping to figure out the keypad PR now and re-do that one to add support for those as well. |
Beta Was this translation helpful? Give feedback.
-
@HclX are the changes to support Climate, Leak, and Chime sensors in your fork working correctly? I see you completed those relatively recently, so am thinking you made more progress than the rest of us did back in 2021. I can't cleanly take those commits, and would basically just need to suck down the entire files, or do a line-by-line fix. Would love to get those in place though.
Beta Was this translation helpful? Give feedback.
All reactions