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

Update quirks for H5051, H5103, H5179. #232

Merged
merged 1 commit into from
Jul 13, 2024
Merged

Update quirks for H5051, H5103, H5179. #232

merged 1 commit into from
Jul 13, 2024

Conversation

rhofour
Copy link
Contributor

@rhofour rhofour commented Jun 25, 2024

I believe this should fix #163, #188, and #206. It works locally for my H5179 devices.

I believe this should fix both wez#188 and wez#206. It works locally for my H5179 devices.
@rhofour
Copy link
Contributor Author

rhofour commented Jul 2, 2024

@wez Is there anything this is missing?

@cnewlandercvs
Copy link

@wez Is there anything this is missing?

Is this repo maintained anymore? Maybe just fork it and run with it until we learn otherwise. If this repo is indeed maintained we can switch back to it. Seems like this PR is addressing an issue three months old. And it's been over a week waiting for this PR to be merged.

@rhofour
Copy link
Contributor Author

rhofour commented Jul 2, 2024

It's definitely still maintained. wez replied in #206 and pointed me in exactly the right direction to fix this.

If you want to test this out yourself you're welcome to switch over to https://github.com/rhofour/govee2mqtt/tree/h5179-fix and try it out. It would probably help if other people confirmed this fixed things for them.

@wez
Copy link
Owner

wez commented Jul 3, 2024

@cnewlandercvs In case you are not aware, you are coming across as supremely entitled when you make a comment like that. What I expect from folks that comment on my projects is to "be excellent to each other", and to keep comments focused and productive. Your comment is neither of those things; it demonstrates a lack of awareness of the nature of the current issues, prior conversations, or how open source works, while coming across with an entitled and impatient tone. I'd encourage you to not respond to this statement or try to defend what you said. Please simply hear me and hold your peace; you needn't say any more, because it will not be a productive outcome for anyone.

@wez
Copy link
Owner

wez commented Jul 3, 2024

@rhofour I think this looks good, thank you! I haven't gotten around to merging it yet because I've had a lot of real life family health concerns recently, and I'll need to refresh my memory on how to correctly cut and push a release for HAOS. Merging is the easy bit!

@fhk1407
Copy link

fhk1407 commented Jul 5, 2024

It's definitely still maintained. wez replied in #206 and pointed me in exactly the right direction to fix this.

If you want to test this out yourself you're welcome to switch over to https://github.com/rhofour/govee2mqtt/tree/h5179-fix and try it out. It would probably help if other people confirmed this fixed things for them.

Could you explain how to go about applying the fix to the HAOS add-on?

@alegend2k
Copy link

It's definitely still maintained. wez replied in #206 and pointed me in exactly the right direction to fix this.
If you want to test this out yourself you're welcome to switch over to https://github.com/rhofour/govee2mqtt/tree/h5179-fix and try it out. It would probably help if other people confirmed this fixed things for them.

Could you explain how to go about applying the fix to the HAOS add-on?

I also dont know how to use this in HASS - an explanation would be nice.

@amresnick
Copy link

amresnick commented Jul 10, 2024

If you want to test this out yourself you're welcome to switch over to https://github.com/rhofour/govee2mqtt/tree/h5179-fix

and try it out. It would probably help if other people confirmed this fixed things for them.

Could you explain how to go about applying the fix to the HAOS add-on?

I would also be interested in this (until @wez has time to make the actual release).

@alegend2k
Copy link

If you want to test this out yourself you're welcome to switch over to https://github.com/rhofour/govee2mqtt/tree/h5179-fix

and try it out. It would probably help if other people confirmed this fixed things for them.

Could you explain how to go about applying the fix to the HAOS add-on?

I would also be interested in this (until @wez has time to make the actual release).

but i cant add it to hass addon repository - if I try to add https://github.com/rhofour/govee2mqtt/tree/h5179-fix
erorr pops up

Cmd('git') failed due to: exit code(128) cmdline: git clone -v --recursive --depth=1 --shallow-submodules -- https://github.com/rhofour/govee2mqtt/tree/h5179-fix /data/addons/git/c84125d4 stderr: 'Cloning into '/data/addons/git/c84125d4'... fatal: repository 'https://github.com/rhofour/govee2mqtt/tree/h5179-fix/' not found '

@wez wez merged commit 6d26288 into wez:main Jul 13, 2024
6 checks passed
@wez
Copy link
Owner

wez commented Jul 13, 2024

Thanks @rhofour!

@rhofour
Copy link
Contributor Author

rhofour commented Jul 14, 2024

Thanks for merging and releasing this! I can see that all my sensors are now working as expected.

@rhofour rhofour deleted the h5179-fix branch July 14, 2024 18:21
@amresnick amresnick mentioned this pull request Jul 14, 2024
@alegend2k
Copy link

Great it is working now !! One question though - is it possible to add an offset to the sensor value ?

@buschtoens
Copy link
Contributor

buschtoens commented Jul 15, 2024

@alegend2k AFAIK it's not directly possible in the addon itself, but you could use a template helper instead.

For instance, here's the template helper I've been using to convert the incorrect Fahrenheit readings to Celsius:

{% set t = states('sensor.govee_temperature') | float %}
{{ (t * 100 - 32) * (5/9) | round(1, default=0) }}

@fhk1407
Copy link

fhk1407 commented Jul 16, 2024

Thanks for merging and releasing this! I can see that all my sensors are now working as expected.

I'm still not being served an updated add-on... I would be grateful for an explanation on how to get it to work?

sampsyo added a commit to sampsyo/govee2mqtt that referenced this pull request Jul 20, 2024
Fixes wez#240. It appears that this sensor uses the same reporting style as
H5103, which were addressed in wez#232.
wez pushed a commit that referenced this pull request Jul 21, 2024
Fixes #240. It appears that this sensor uses the same reporting style as
H5103, which were addressed in #232.
@cgoudie
Copy link

cgoudie commented Jul 24, 2024

Looks like this would fix #247

@Marshall-Hallenbeck
Copy link

Hmm this was merged but it still seems like it's reporting wrong for me.

@amresnick
Copy link

amresnick commented Sep 2, 2024 via email

@Marshall-Hallenbeck
Copy link

Shouldn't adding the repo just use the newest code, or does it download the newest release instead?

@amresnick
Copy link

amresnick commented Sep 11, 2024 via email

@rhofour
Copy link
Contributor Author

rhofour commented Sep 11, 2024

Shouldn't adding the repo just use the newest code, or does it download the newest release instead?

I believe it only downloads the newest release, but there was a release on July 13th that included this: https://github.com/wez/govee2mqtt/releases/tag/2024.07.13-82ddc6e9

I have no idea why it seems some people aren't seeing it, but I was able to update through HA Add-Ons.

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.

H5179 - Temperature Readings are not valid.
9 participants