forked from mileperhour/localtuya-homeassistant
-
Notifications
You must be signed in to change notification settings - Fork 565
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
Allow port reuse so that other integrations can read the same port #1481
Merged
rospogrigio
merged 2 commits into
rospogrigio:master
from
CodeFoodPixels:CodeFoodPixels-patch-1
Sep 12, 2023
Merged
Allow port reuse so that other integrations can read the same port #1481
rospogrigio
merged 2 commits into
rospogrigio:master
from
CodeFoodPixels:CodeFoodPixels-patch-1
Sep 12, 2023
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
rospogrigio
approved these changes
Sep 12, 2023
noahajac
pushed a commit
to noahajac/localtuya_comfortbilt
that referenced
this pull request
May 25, 2024
…ospogrigio#1481) Co-authored-by: rospogrigio <[email protected]>
noahajac
added a commit
to noahajac/localtuya_comfortbilt
that referenced
this pull request
May 25, 2024
* Fix for AttributeError: 'TuyaMessage' object has no attribute 'release' error * rospogrigio#711 Implemented m/p HVAC mode set * Introduced pytuya with support for 3.4 protocol * Introduced 3.4 protocol option in config flow * Fixed HEARTBEAT command * Added debugging * Fixed requested DPs for type_0d devices * Fixed negotiation and sequence numbers for protocol 3.4 * Fixed sequence numbering on status update * Fixed tox issues * Fixed tox issues * Updated README.md and info.md * Fixed tox issues * Fix for version not being set yet when calling _setup_dispatcher * Introduced the possibility to select which devices should have the pytuya debug enabled * Introduced device debugging option in README.md and info.md * Introduced pytuya with support for 3.4 protocol * Introduced 3.4 protocol option in config flow * Fixed HEARTBEAT command * Added debugging * Fixed requested DPs for type_0d devices * Fixed negotiation and sequence numbers for protocol 3.4 * Fixed sequence numbering on status update * Fixed tox issues * Fixed tox issues * Updated README.md and info.md * Fixed tox issues * Fix for version not being set yet when calling _setup_dispatcher * Introduced abort in config flow if all entities are deselected when editing a device * Introduced IT and PT translations * Update manifest.json for 5.0.0 * New tuyadebug.tgz now supporting protocol 3.4 * Update bug_report.md * Fix for unknown state of covers/shutters * New tuyadebug.tgz now including a tinytuya test * Force to int * Adjust input to avoid putting a string into an int * Adjust input to avoid putting a string into an int * Swap to int * Improved logging * Improved stability and Fix local_key update to not be thwarted by retries * Introduced update of local_key when editing a device * Improved logging * Tox fixes * Tox fixes * Tox fixes * Fix for not reconnecting after 'giving up' * Tox fixes * Tox fixes, reduced to 3.9 only * Add entities during 'Edit a device' * revert the default region * Fix depreciated async_get_registry * Add HACS validation * Remove extra key * Update manifest.json * Remove extra key * Update hacs.json * Add Hassfest validation * Alphabetize manifest.json Alphabetized manifest.json according to home assistant requirements. * Delete combined.yaml As described in KTibow/ha-blueprint, ha-blueprint is being retired and we should thereby switch over to hassfest and hacs validation. * Update tox.yaml Added workflow_dispatch * Update tox.ini * Reduced logging level for 'Command %d timed out waiting for sequence number'; set v.5.1.0 * Fixed tox errors * Updated manifest.json * Fix for socket.send() exceptions in the logs * Fixing pylint error * fix bug when climate entity is using default min/max temp and temp unit 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. * Allow calling localtuya.set_dp service by non-admin users * Fixed initialization with API but no internet. * Handle 3.4 protocol, fix CI (rospogrigio#1251) * Use refresh interval in version 3.4 * Scan interval convert to integer * Try to fix CI * Try to fix CI * Allow port reuse so that other integrations can read the same port (rospogrigio#1481) Co-authored-by: rospogrigio <[email protected]> * Fixing tox issues * Replaced SUPPORT_* with enums, set minimum HA version in HACS configuration to 2024.1.0 * Add support for more ac/fan modes (rospogrigio#1389) * 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 <[email protected]> * added dict get() instead of assuming keys exist; now handles config_flow setup failures without crashing * feat: add climate entity support for Comfortbilt stoves * refactor: change information for fork * feat: add support for alarm --------- Co-authored-by: sibowler <[email protected]> Co-authored-by: Daan Kemper <[email protected]> Co-authored-by: rospogrigio <[email protected]> Co-authored-by: rospogrigio <[email protected]> Co-authored-by: Daniel O'Connor <[email protected]> Co-authored-by: GaoJing <[email protected]> Co-authored-by: oven-lab <[email protected]> Co-authored-by: nu <[email protected]> Co-authored-by: Ovidiu Nitan <[email protected]> Co-authored-by: Neal Joslin <[email protected]> Co-authored-by: dulyts <[email protected]> Co-authored-by: Luke Bonaccorsi <[email protected]> Co-authored-by: Elad Bar <[email protected]> Co-authored-by: Simon Tegelid <[email protected]> Co-authored-by: Simon Tegelid <[email protected]> Co-authored-by: [email protected] <[email protected]>
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.
👋 I've recently taken over maintainership of the robovac integration and have added autodiscovery to keep the IP addresses up to date. Someone mentioned that they were having issues with both the robovac and localtuya integrations running at the same time, and I believe that adding this to both of our integrations should resolve the issue.