Open ingoratsdorf opened 2 years ago
FYI, This PR may help on that https://github.com/rospogrigio/localtuya/pull/942
@deese , yes, that might work. But apparently still not even in fan. And needed everywhere with int's.
@deese , yes, that might work. But apparently still not even in fan. And needed everywhere with int's.
Ever find a solution to this? I've hit the same issue with an Arlec/DETA PIR sensor. Mode and load on/off works in HA for now and can set the sensitivity, time, and lux from the Tuya app, but it'd be nice to keep it all in HA.
PR #1265 is waiting for Merge since March 2023. It will fix this issue and possibly a dozen more. Any chance to see this in the next release? It is essential for many Wall Plug Thermostats ( including mine).
I have this issue also with a pool heater... Evything is working fine except the target temperature settings. It is well discovered as a number and displayed correctly but when I try to change it, it goes to the minimum of the range... So probably requesting an INT instead of a FLOAT... Thanks !
May be related to #https://github.com/rospogrigio/localtuya/issues/710 ?
The problem
Move a slider for a number entity to any number other than 0, comes back as set to 0 (zero)
Environment
Steps to reproduce
LocalTuya defined for a PIR sensor. It’s DPS config represents the following:
When I move the slider for DP103 to any number in Home Asiistant, it comes back as set to 0 (zero) Same for DP104 and DP105. Comes back as zero. If I call a service as below
The value is correctly set to what it is supposed to be.
Configuration
configuration.yaml
orconfig_flow
config_flow
Provide Home Assistant taceback/logs
Additional information
As noted above, when manually calling the setDP service, all is working. I noticed in the trace above that the number is sent as 4.0 (float) and comes back as 0 (int). Can it be that tuya (or this device) does not support floats (4.0) but expects just an integer (4)? Can localtuya use integer only to send?