Skip to content
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

Hass 2021.6 not loading vbus #6

Open
thwandi opened this issue Apr 25, 2021 · 8 comments
Open

Hass 2021.6 not loading vbus #6

thwandi opened this issue Apr 25, 2021 · 8 comments

Comments

@thwandi
Copy link

thwandi commented Apr 25, 2021

Hey,

i have tried to setup the Vbus custom component in my Hass but it keeps mentioning the Following. Im not getting any data out of the vbus, the entities are just showing "Unknown" and nothing happens. I Connected the vbus using a USB to RS485 adapter. may that be the issue why i am not getting any data? Or is it regarding the last Hass Update?

Logger: homeassistant.loader Source: loader.py:786 First occurred: 25. April 2021, 22:30:25 (1 occurrences) Last logged: 25. April 2021, 22:30:25 No 'version' key in the manifest file for custom integration 'resolvbus'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'resolvbus'

@epenet
Copy link
Owner

epenet commented Apr 26, 2021

A few questions:

  • which version of Home Assistant are you using (2021.6 is not out yet I think)?
  • was it working before? or is it the first time you are trying?
  • what type of Resol/Vbus component are you trying to communicate with?

@thwandi
Copy link
Author

thwandi commented Apr 26, 2021

I'm using core-2021.4.5 and it is the first time i tried it. I have a Deltasol BS Controller and a USB-RS485 Converter on the Raspberry which is running the HA. Im thinking that the RS485 Adapter (it shows as USB to UART CP2102) is not the correct choice for getting the Vbus working.

@epenet
Copy link
Owner

epenet commented Apr 26, 2021

What did you put inside your YAML?

@epenet
Copy link
Owner

epenet commented Apr 26, 2021

Also - I think you are correct that VBUS is not the same as RS485.
They are similar but I don't think they are compatible.

@thwandi
Copy link
Author

thwandi commented Apr 26, 2021

How did you connect your vbus devices to Homeassistant? I dont wanna use their own converter stuff because its too expensive.

My yaml for the testing is as follows:

`- platform: resolvbus
name: MyResol
ttyPort: /dev/ttyUSB0
filterSource: 0x4720
filterDestination: 0x0010
filterCommand: 0x0100
attributes:
- name: temperature_sensor_1
offset: 4
size: 2
factor: 0.1
type: temperature
- name: temperature_sensor_2
offset: 6
size: 2
factor: 0.1
type: temperature
- name: temperature_sensor_3
offset: 8
size: 2
factor: 0.1
type: temperature
- name: pump_speed_relay_1
offset: 16
size: 1
- name: error_mask
offset: 68
size: 4
- name: operating_hours
offset: 28
size: 4

  • platform: template
    sensors:
    myresol_temperature1:
    value_template: '{{ state_attr("sensor.myresol" , "temperature_sensor_1") }}'
    friendly_name: "Collector"
    unit_of_measurement: '°C'
    myresol_temperature2:
    value_template: '{{ state_attr("sensor.myresol" , "temperature_sensor_2") }}'
    friendly_name: "Store"
    unit_of_measurement: '°C'
    myresol_temperature3:
    value_template: '{{ state_attr("sensor.myresol" , "temperature_sensor_3") }}'
    friendly_name: "Return"
    unit_of_measurement: '°C'
    myresol_pump1:
    value_template: '{{ state_attr("sensor.myresol" , "pump_speed_relay_1") }}'
    friendly_name: "Pump"
    unit_of_measurement: '%'
    myresol1_hours1:
    value_template: '{{ state_attr("sensor.myresol" , "operating_hours") }}'
    friendly_name: "Operating Hours"
    unit_of_measurement: 'h'
    myresol1_error1:
    value_template: '{{ state_attr("sensor.myresol" , "error_mask") }}'
    friendly_name: "Error"
    unit_of_measurement: '' `

@epenet
Copy link
Owner

epenet commented Apr 26, 2021

I use this product (got it almost 10 years ago!): https://www.resol.de/fr/produktdetail/13

@thwandi
Copy link
Author

thwandi commented May 1, 2021

Hi,

so i now changed to a classical USB UART converter and a level shifter circuit. If i connect that to my Mac and Readout the Serial Stream it shows the Following:

aa1000204710000112651554452d032164004e02004b7f002c04014f000040feff64000000001b3f0800000038450800000032808044f78f00000000007f00000000007f00000000007f00000000c001bcffaa150020471000010a6802010000007c64004e02004b7f0071580d2a018400fafeff64004e02004b00000000007f010b000000730000000080ff

AA is the start, 0010 should be the destination address, 4720 should be the source address, so far so good. But if im connection that to my Rpi with Homeassistant OS it still says "unknown" for all my configured sensors. My Controller is a Deltasol BS HE, 4720 in the resol list is known as BS/2 HE.

But im still not able to see any data from the Controller in my Homeassistant. Could you help me? Is there a way to monitor if the Serial Stream is arriving in the HASS correctly?

Thanks!

@epenet
Copy link
Owner

epenet commented May 3, 2021

Last year I decided to upgrade my RPI for HA, and to keep the old one for owserver, teleinfo and resol communicating with HA over the network. I therefore no longer use this HA component and it's possible that it is no longer compatible with latest HA versions...

I think the first step is to ensure that you can read the RESOL data directly from the command line.
I have attached here a small python script which I use for checking values.
vitosolic-test.zip

On line 8, you should change the USB port.
On lines 29-32, you should change to b'\x10\x00\x20\x47'
Then on lines 142-174, you can change to use the correct sensors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants