liudger
(Willem-Jan)
November 9, 2022, 10:13am
105
Diagnostics is coming soon in an update. Need to be merged. This would help with trouble shoot. I guess you have also a newer firmware? it only supports v1
hylyah
November 9, 2022, 10:52am
106
Oh⊠I am in V2âŠ
There is a documentation to using BSB-LAn V2 with mqtt ?
GSzabados
(GĂĄbor Szabados)
November 9, 2022, 11:05am
107
Partially, look at my and others comments above.
I tried to figure out yesterday how to setup a MQTT select for HVAC_MODE
(as it was mentioned above), but I couldnât make it work. It received the mode from BSBLAN, but I couldnât set it with the select.
Update: I looked at those codes and actually you need the new MQTT sensor definition, those are the depreciated ones.
hylyah
November 10, 2022, 9:08am
108
Hello,
It work with REST sensor so it is good for me.
Now I am looking how to create a switch/REST to change value.
GSzabados
(GĂĄbor Szabados)
November 10, 2022, 7:09pm
109
Look at @tiger42 posts above like this one:
I do not use a climate card, but individual input fields instead. This is what it looks like:
[heating_circuits]
This is the corresponding lovelace config:
cards:
- entities:
- entity: sensor.bsb_lan_betriebsart
filter:
include:
- key: sensor.bsb_lan_betriebsart.desc
name: Status
heading_name: ' '
heading_state: ' '
type: 'custom:entity-attributes-card'
- entity: input_number.bsb_lan_komfortsollwert
namâŠ
GSzabados
(GĂĄbor Szabados)
November 13, 2022, 12:19am
110
Look here for examples, there are a lot.
opened 03:01PM - 12 Nov 22 UTC
closed 10:44AM - 13 Nov 22 UTC
**Before submitting a bug report, please make sure that you have checked [chapte⊠r 14](https://1coderookie.github.io/BSB-LPB-LAN_EN/chap14.html) of the manual** ("Problems and their Possible Causes"). Most problems that are reported to us can be solved by going through the solutions provided there.
**BSB-LAN Version**
3.0.1-20221101130752
**Architecture**
Arduino Due
**Bus system**
BSB
**Describe the bug**
Read MQTT data in Home Assistant, because integration from @liudger not working now, I tried add an easy sensor.
IP adress of broker, username and password is right.
Device ID and prefix is as default BSB-LAN
**To Reproduce**
Steps to reproduce the behavior:
1. Go to manual, chapter 8.11
2. Click on configuration.yaml and edit
3. paste
```
sensor:
- platform: mqtt
state_topic: "bsb-lan/8310"
name: BSB-LAN flow temperature
unit_of_measurement: °C
device_class: temperature
```
This is not valid configuration.
I tried a new format
```
mqtt:
sensor:
- name: "BSB-LAN flow temperature"
state_topic: "bsb-lan/8310"
unit_of_measurement: "°C"
device_class: temperature
```
5. See state of entity, is still unknown in both cfgs
**Logs**
LOG from MQTT Broker in HA:
`2022-11-12 15:52:18: New connection from 192.168.0.150:51415 on port 1883.`
State by BSB Lan
http://192.168.0.150/8310
8310.0 Diagnostics producer - Boiler temp actual value: 37.7 °C
**Additional context**
I am doing some bad, but I dont know what...
GSzabados
(GĂĄbor Szabados)
November 13, 2022, 12:23am
111
So actually v3.0 is out and you need to start with a fresh config and custom_defs.h from Fred for your language.
liudger
(Willem-Jan)
November 13, 2022, 8:19am
112
Yes I Just updated my device!!
I have to wait for the device specific file. This makes it a bit scary if with this integration we can monitor all sorts of devices. Maybe the manual setup mqtt and rest is the better option?
I will have a look if I can identify devices and find the right basic parameters.
GSzabados
(GĂĄbor Szabados)
November 13, 2022, 5:28pm
113
I have never used the integration as I am using v2.x. But the main question, what do you want to control or read from a heater. I think the above listed example sums up the most common values. But might be a query for some other parameters could work, and some way let the user to add more parameters to monitor?
hylyah
November 13, 2022, 9:04pm
114
Just try the new update but I have an issu.
It show me a wrong température : -7.2 instead of 19.
GSzabados
(GĂĄbor Szabados)
November 14, 2022, 12:41pm
115
There is a conversion issue, it thinks 19 is in Fahrenheit and converts it to -7.2 Celsius.
Liese
(Jörg)
November 15, 2022, 4:29pm
116
Hi,
it seems I do not get the ESP32 to send the data.
My HA instance says, the ESP is up and running via developer entity check
source_type: router
ip: 192.168.1.53
mac: 7C:9E:BD:61:4C:90
host_name: BSB-Heizung
last_time_reachable: 2022-11-15T16:26:34+00:00
connected_to: fritz.box
connection_type: WLAN
ssid: xxxxxx
icon: mdi:lan-connect
friendly_name: BSB-Heizung
But my mqtt sensor in configuration.yaml is still âunknownâ
mqtt:
sensor:
- name: "mqtt temp bsb"
state_topic: "BSB-LAN/8700"
unit_of_measurement: °C
device_class: temperature
Any idea whatâs wrong?
Maybe I am struggling again with YAML syntax?
Regards
Joerg
EDIT:
It seems - after some checks with MQTT explorer - that it should be
mqtt:
sensor:
- name: "mqtt temp bsb"
state_topic: "BSB-LAN/8700.00"
unit_of_measurement: °C
device_class: temperature
GSzabados
(GĂĄbor Szabados)
November 16, 2022, 2:55pm
117
@Liese , it was just discussed in this issue what I posted above.
Look here for examples, there are a lot.
liudger
(Willem-Jan)
November 17, 2022, 8:13pm
118
The current version doesnât support version 3.0 yet. I am working on this.
The wrong unit is because BSBLAN project changed the string they used to identify unit. The new version that is almost ready will fix this and support the latest master. There was a bug in latest release of the firmware so please upgrade to the latest master commit.
liudger
(Willem-Jan)
November 18, 2022, 7:43am
119
pull request is done! waiting for merge
home-assistant:dev
â liudger:add-support-for-firmware-v3
opened 08:41PM - 17 Nov 22 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.
-->
Add support for new firmware. This brings support for esp32 devices.
https://github.com/liudger/python-bsblan/releases/tag/v0.5.8
This pull request is dependent on
https://github.com/home-assistant/core/pull/80957
## 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
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] 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 #80817
- 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.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] 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.
- [x] Untested files have been added to `.coveragerc`.
<!--
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:
- [x] 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
1 Like
babajun
(Gerhard)
November 19, 2022, 9:26pm
120
Iâm still using the old BSB v 0.44
Since some days, after an HA update, the HAVC panel doesnât show the BSB integration anymore. Is this expected?
liudger
(Willem-Jan)
November 20, 2022, 1:27pm
121
If you could make an issue on GitHub. This could speed up the merge process. It should be fixed with the latest pull request that is waiting for a merge. Not sure why it broke as it didnât fail test the previous version. It could be that I pulled more info from bsblan and this is maybe not available on certain devices. The latest version only pulls the minimum and hopefully this will fix the issue.
Regards Willem-Jan
liudger
(Willem-Jan)
November 20, 2022, 3:01pm
123
You could also retry adding the integration. So first delete. In one of the updates it needed a fresh setup
babajun
(Gerhard)
November 20, 2022, 3:22pm
124
Tried that, but cannot add new adapter. I donÂŽt use user/PW, just a string. Adapter Webpage is working: