rhodges
(Randell)
May 6, 2022, 12:49am
223
I have a remotelinc and, if I command the scene to turn on/off it works. Make sure the remote has an action of “default”. The first image shows the things in the scene, and then the other images show when I click on the individual items in the scene.
I think that is what I did to get it to work properly.
FL- FanLinc Device
KP- KeyPad
RM- RemoteLinc
@shbatm Thanks for you awesome work on this integration. I am running ISY 994I 5.3.3. I have read only visibility of my Venstar Insteon Thermostat. I did some googling and found some old threads from 2019/2020. Are there any more current instructions on how to get 2 way thermostat support working with Homeassistant?
shbatm
(Shbatm)
June 25, 2022, 10:21am
225
Does the Venstar support 2-way setting from the ISY?
Can you post the XML output of http://your-isy-url/rest/nodes/ <<venstar addr>>
?
shbatm
(Shbatm)
June 27, 2022, 8:25pm
226
Venstar support should be fixed in an upcoming release:
home-assistant:dev
← shbatm:patch-3
opened 07:53PM - 27 Jun 22 UTC
## Proposed change
<!--
Describe the big picture of your changes here to com… municate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Bump pyisy to 3.0.7
https://github.com/automicus/PyISY/releases/tag/v3.0.7
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [x] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue: Partial resolution to https://github.com/home-assistant/core/issues/73972, Fixes community issue [here](https://community.home-assistant.io/t/venstar-2491t-insteon-v-93-thermostat-through-isy994-cant-set-temps-on-home-assistant/347919) and [here](https://community.home-assistant.io/t/calling-all-isy994-users/36205/225)
- Link to documentation pull request: N/A
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
shbatm
(Shbatm)
February 20, 2023, 9:28pm
227
PyISYoX Alpha Testing
Reviving an old chain – back with some more major updates to the ISY/IoX integration! If anyone is interested in testing, I have an alpha version for test a re-written pyisy / Home Assistant integration.
It can be added to Home Assistant using HACS and adding a Custom Repository: GitHub - shbatm/hacs-isy994: Custom Integration for ISY994 with Home Assistant (for use with HACS)
This includes a significant re-write of the underlying project to make it faster and more code conformant.
The goal of this version is to implement the following:
Standardization of code for different components
Use of modern Python (3.10+) coding styles and structures
Fully Typed module and Home Assistant integration
Conformant and consistent styles with Home Assistant (e.g. via mypy
, flake8
, ruff
, pylint
).
Dynamic loading of Node Definitions (names, types, translations) for Z-Wave**, Z-Matter**, and Node Servers
Home Assistant entity sorting and naming of Z-Wave and Node Server nodes based on Node Defs**.
** Work in progress - not yet available
Links:
Disclaimer
Consider this your official “Here Be Dragons” warning:
If you install the hacs v4.0.6 (pyisyox 1.0.0a2) you are accepting that there will be breaking changes . Unlike what I will have to do when this gets merged back for everyone–there are no deprecation warnings or grace periods. I’m making changes that need to be tested to try and get the new features and sorting for Z-Wave and Node Servers ready for prime time.
Entities will change names, will change device classes, and will change controls.
If you are using this on your main production system–you must back-up Home Assistant frequently, and be prepared to revert back to an old version, or uninstall the hacs version if something is not working for you. If you don’t know how to install a custom repo in HACS: testing this probably isn’t for you.