-
Notifications
You must be signed in to change notification settings - Fork 74
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
Add support for TemperHUM_V3.8 #34
Comments
From what I can see the following patch could already be enough for parsing:
We could alternatively also parse for the whole As well as adding the valid id list:
Adding those two makes temper.py work for me:
Can you advise which format you'd like for parsing the Firmware ID? Full string (TEMPerHUM_V3.8) or |
@urwen There are many PRs and issues open - would you be open for somebody else to take over the project? I can fork it, but I have seen that there is another stale fork at https://github.com/ccwienk/temper/ and I'd prefer avoiding to create another fork. |
@telmich thanks, I just ran into this new updated firmware this morning, and you patch seems to be working well. |
@telmich We're still taking PRs and issues over on ccwienk/temper. No guaranteed turnaround time, but we do get around to handling them. We also publish the PyPi package Edit: I started working with that repo after no response from original author here. Given that it has been a good long while, I'm going to actually start deviating where it makes sense to do so rather than keeping the difference to this repo minimal. I.e., rather than just accepting a device add here and there, I might make structural changes where it makes sense to do so. |
The latest shipment has an updated firmware:
This looks exactly the same as the previous white temperhum devices
The text was updated successfully, but these errors were encountered: