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

Number - integer format option #56

Open
wants to merge 693 commits into
base: master
Choose a base branch
from

Conversation

partybence
Copy link

Some devices might not handle float values properly, as happened to me. Please consider adding an option as I've described below.
Added checkbox option that number values should be sent to device as int.
Note that mine really is just a basic, makeshift solution. Requires the user to know not to use float min-max-step values or else they'll be parsed to int when this option is ticked.
The translation is basic google translate, might not be proper.

tinglis1 and others added 30 commits December 22, 2021 23:05
Add scan interval notes and updated screenshots for README.md and info.md
fix deprecated device_state_attributes
Implementation of climate platform
There is a typo in target precision which prevents corrct handling of temperature
* Add link to _tinytuya_.
* Clarify steps in Home Assistant Configuration screens.
* Set `yaml` syntax on a code example.
Use the core utility rather than reimplementing it.

Signed-off-by: Peter A. Bigot <pab@pabigot.com>
oven-lab and others added 30 commits May 20, 2023 14:27
Added workflow_dispatch
…exceptions

Fix for socket.send() exceptions in the logs
…it is F

The default min/max temps are in C but when the climate entity is set up with F this will cause incorrect boundary check and an inability to change the temperature from the home assistant entity UI widget.
* Use refresh interval in version 3.4
* Scan interval convert to integer
* Try to fix CI
* Try to fix CI
…ospogrigio#1481)

Co-authored-by: rospogrigio <49229287+rospogrigio@users.noreply.github.com>
Allow calling localtuya.set_dp service by non-admin users
…temp-when-in-F-fix

fix bug when climate entity is using default min/max temp and temp un…
* Add support for more ac/fan modes

* Replace deprecated constants with enums

* Add support for ClimateEntityFeature.TURN_{ON,OFF}

* Fix swing log message

---------

Co-authored-by: Simon Tegelid <simon.tegelid@bitvis.io>
Based on https://developers.home-assistant.io/blog/2024/06/12/async_forward_entry_setups/
it is possible to replace it with `async_forward_entry_setups` instead,
which accepts multiple platforms and it should be more efficient.
My AC wouldn't take the temperature as float, added option to choose to set number value as int.
This is not the nicest job, it may need more handling regarding the possible min-max-step values, the translation is pure google translate, but does the trick.
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.