-
Notifications
You must be signed in to change notification settings - Fork 754
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
partybence
wants to merge
693
commits into
mileperhour:master
Choose a base branch
from
partybence:number_integer_format_option
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Number - integer format option #56
partybence
wants to merge
693
commits into
mileperhour:master
from
partybence:number_integer_format_option
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix missing color temp label
Periodically send update dps command
Add scan interval notes and updated screenshots for README.md and info.md
fix deprecated device_state_attributes
update to the new fan platform
Implementation of climate platform
Vacuum platform new
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>
Added workflow_dispatch
Code test changes and issue rospogrigio#1375, rospogrigio#1398
…number'; set v.5.1.0
…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…
…ration to 2024.1.0
Fix rospogrigio#1610 - Replaced SUPPORT_* with enums
* 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>
…low setup failures without crashing
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.