-
Notifications
You must be signed in to change notification settings - Fork 526
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
Temperature off by a factor of 10 with some Entities #1907
Comments
You seem to have a variant of a supported device with different temperature scale, but there is no log or diagnostics attached to your report that would show which device config you are using. |
I will attach it. Not sure if I should be removing any info from it. There is no HA log mentioning this device at all. |
Do I need to add any more info? I do note the temp is showing correctly but the limits for the alarms are off by a factor of 10. thanks |
Are you trying the latest development version, or still on the last release? |
Latest release, which also has the issue that I have to reload all devices since they become unresponsive after reboot |
I think that is not even the latest release then, but the April release, before a series of hotfixes were attempted following the HA 2024.5 release which caused the above problem |
If you installed via HACS, then it should take care of prompting you when there is an update (but if you pressed "Ignore" at any stage, it may have stopped prompting). |
Nope never hit ignore. Installed through Settings> Devices and services> Add integrations > Tuya Local. Think first needed to add in hacs. Update: Ok just went to hacs again and clicked on add integration again and now the update shows up. So now I am all updated to 2024.5.2. The issue raised still remains. Thanks |
Sorry may I ask if there is any update? I am now using the latest version but am thinking you were wanting me to test a development version? Sorry how do you access it? |
I was wondering why mine wasn't showing. I had to again go to hacs for the update to show. Curious when was it released? BTW thank you so much for fixing this. |
Based on logs in make-all#1907, all values are scaled by 10, and ranges of original PR for temperatures seem to support that. Humidity is also scaled by 10 in the log, so adjusted some ranges to match. Assume both variants (with and without humidity) are the saame. Issue make-all#1907
A clear and concise description of what the bug is.
https://www.aliexpress.com/item/1005005372714992.html?spm=a2g0o.productlist.main.29.6be04f0fOEHZE4&algo_pvid=0c8a2f78-29f0-43b5-ba0b-7cb4a7a3162e&algo_exp_id=0c8a2f78-29f0-43b5-ba0b-7cb4a7a3162e-14&pdp_npi=4%40dis%21AUD%2178.84%2118.36%21%21%21371.02%2186.42%21%402101e5c517154395539983527e484c%2112000032789022863%21sea%21AU%210%21AB&curPageLogUid=HSDlkxo9sW1e&utparam-url=scene%3Asearch%7Cquery_from%3A
Ok so brought this device to monitor my Aquarium which works perfectly in tuya app. It also has temp and humidity high and low alarms to be setup. So I try to maintain the temp of the Aquarium around 30 deg C for tropical setup. In the tuya app I am able to set the temp high to 34 and low to 26 for alarms.
In HA I was able to get the current temp which is around 28.3 deg C fine but the limits have to setup in multiples of 10, so I need to somehow divide it by 10 else the alarms go off in the tuya app because setting it up as 26 and 34, sets it up in tuya as 2.6 and 3.4 etc. See pic
No bug report really because nothing is actually erroring out.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
I added this device with 3.4 in config as 3.3 did not work. Not sure if that is related at all.
If the bug involves a device, then please include device diagnostics from
Settings / Devices & Services / Tuya Local (your device) / "1 device"
Please check if there are messages from Tuya Local in the Home
Assistant log (Settings / System / Logs), and include those too.
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: