DDG
(Danny De Gaspari)
December 1, 2021, 6:09pm
206
Thanks for feedback.
What about implementing the dimspeed for dimmer channels in VMB4DC ? E.g. in automations set the dim value but also the dim speed.
brefra
(Brefra)
December 2, 2021, 9:11pm
207
@DDG , you should be able to use the “native” transition option of HA for this, like configured in screenshot below:-
DDG
(Danny De Gaspari)
December 3, 2021, 7:10am
208
Thanks for that. Did not know you could do it this way too.
BenoitP
December 3, 2021, 3:48pm
209
This morning the weather was cold and the VMBPIRO was indicating -1°c in Velbuslink and 127,31°c in HA !
Cereal2nd
(Maikel Punie)
December 3, 2021, 4:07pm
210
this is a bug in the velbusaio lib, the first bit is not used as the signbit
Bubli
(Kevin F)
December 15, 2021, 2:06pm
211
Hi Cereal2nd,
I just installed HomeAssistant 12.0; I’ve never had any issues but now I have two:
My blinds are always showing they are open, while they are closed. I can see in the history they first get the state closed, but once they are fully closed, they get a new state that says they are open again
My dimmable lights through Velbus (VMBDMI) are just showing as lights and not dimmable lights, since this new version.
Any ideas on this?
Thanks for your awesome work on this integration!
Kristof24
(Kristof Briers)
December 15, 2021, 3:14pm
212
I have the same problem! (Dimmers, Blinds, and temp status on glass modules)
I’m on version Home Assistant 2021.12.2 now…
I have al te latest Velbus firmware installed
Dimmer module info:
VMB4DC
by Velleman
Firmware: 25141-0.32.72
Blinds:
VMB2BLE
by Velleman
Firmware: 60622-0.25.53
Glass Button
VMBGP4
by Velleman
Firmware: 2674-1.25.23
lowagie
(thijs)
December 17, 2021, 4:59am
213
Hi all, new here on the forum and never ever had issues with Velbus in my HA over the past years. Looks that since the latest update, I have 2 issues with my setup, please help on what could be a next step to try to solve this.
In HA, all is up to date.
The climate entity doesn’t show the current temp any longer.
I no longer can dim my lights:
Thanks,
Thijs
Cereal2nd
(Maikel Punie)
December 17, 2021, 6:17am
214
For these problems.
I always need to know the exact moduletypes and firmware version.
Without this it’s impossible to
lowagie
(thijs)
December 17, 2021, 8:53am
215
Hi,
I’ll come back with more details
Before I do, one thing I’m thinking; I never updated/upgraded my velbus modules to newer/latest firmware.
I’ll try that first.
Thx for the input
Thijs
bvedomotic
(Bertrand)
December 18, 2021, 4:38pm
216
Hello,
The problem with the thermostat is on all glass panels of different types sinds last update, also all modules are dubbeled, one with the sensors and one without Anny sensors.
same problem with dimmers here after update of HA a few weeks ago
Cereal2nd
(Maikel Punie)
December 19, 2021, 6:00pm
218
someone is already running a pull-request to fix this
home-assistant:dev
← wlcrs:fix-velbus-dimmer
opened 01:53PM - 19 Dec 21 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate 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.
-->
Fix missing brightness setting for Velbus lights
## 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.
-->
- [ ] 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 #62169
- This PR is related to issue:
- Link to documentation pull request:
## 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.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] 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:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] 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
<!--
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
so once that one is merged, in the new version the dimmer problems should be solved.
Small note, i do not own dimmers, so i can’t test them …
and this is the PR for the current temp
home-assistant:dev
← Cereal2nd:velbusclimatefix
opened 06:10PM - 19 Dec 21 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.
-->
In one of the last udpates the current temperature was removed from the climate devices, this PR sets back the current_temperature property
## 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.
-->
- [ ] 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:
- Link to documentation pull request:
## 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.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] 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:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] 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
<!--
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
Cereal2nd
(Maikel Punie)
December 20, 2021, 5:30am
220
Both are merged so 2021.12.4 should have it solved.
For the blinds problem, is this a new problem? or did it also exist in previous releases?
lowagie
(thijs)
December 21, 2021, 11:11am
221
I can confirm, both fixed in 2021.12.4.
Thanks
bvedomotic
(Bertrand)
December 21, 2021, 7:39pm
222
Thanks,
Works great again.
But there are still double modules without entity’s, but that is not a problem for the functionality…
Cereal2nd
(Maikel Punie)
December 22, 2021, 7:47am
223
for the double modules i’m writing code to remove these.
it would be really helpfull if some people use the beta or rc channel in hass, this way we can catch problems like this before the actual release
lowagie
(thijs)
December 22, 2021, 8:01am
224
Same here. How can we fix this in the velbusaio lib? or what could be an easy workaround in HA?
Cereal2nd
(Maikel Punie)
December 22, 2021, 9:06am
225
This has to be fixed in hass via code
i’m trying to understand why this happend, i’m starting to think this happend during the migration from a string based ID to a deviceID object.
what i will probably do is add code to remove devices that do not have entities inside the velbus component.
Bubli
(Kevin F)
December 22, 2021, 9:47am
226
This is a new problem; I’ve never had this issue before and only have it since upgrading to version 2021.12.0.
I’m upgrading to 2021.12.4 now, so will check if I still have it. If so, I’ll provide info on the modules and firmware. I think I also still have Velbus firmware updates, so I’ll also update those if possible first to test.