search

chiefdeputy / Resol-EmSimulator

Docker Compose project to simulate an EM device for Resol V-Bus
MIT License
0 stars 0 forks source link

Please, help me to setup this addon. Thanks #2

Open hoppel118 opened 1 year ago

hoppel118 commented 1 year ago

Hi,

I am migrating my home automation software from FHEM to Home Assistant.

So far, so good. This is one of the last pieces of the puzzle. I am new to Home Assistant, but not new to Linux, even though I am not a developer. :)

My Setup:

I can read the vbus information with the respective FHEM integration. So the setup as such works. Now I just have to migrate it to Home Assistant.

I have done what is described here: https://github.com/chiefdeputy/Resol-EmSimulator/blob/master/README.md

First I tried the following configuration:

host: 10.11.13.24
password: vbus
sensors:
  - switch.to_publish_as_sensor1
  - light.to_publish_as_sensor2
  - input_boolean_to publish_as_sensor_3
  - input_number.to publish_as_sensor_4
  - sensor.to_publish_as_sensor_5
json_server: true

But I got the following Websock ERROR:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Resol VBus
 Addon to provide json VBus data and emulate Extension Modules for Resol Deltasol controllers.
-----------------------------------------------------------
 Add-on version: 0.0.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.4  (amd64 / qemux86-64)
 Home Assistant Core: 2022.12.9
 Home Assistant Supervisor: 2022.12.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
01-03 03:42 INFO VBusCon Connecting to VBus device at 10.11.13.24
01-03 03:42 INFO Websock Setup listener
01-03 03:42 INFO WServer Setup web app.
01-03 03:42 INFO WServer Listening to VBus.
01-03 03:42 INFO WServer Setup TCP web server on port 26514.
01-03 03:42 INFO DevSim  Connection manager started.
01-03 03:42 INFO Websock Connecting...
01-03 03:42 ERROR Websock Expected message:
{'id': 2, 'type': 'result', 'success': True}
But got:{'id': 2, 'type': 'result', 'success': False, 'error': {'code': 'invalid_format', 'message': "Entity input_boolean_to publish_as_sensor_3 is neither a valid entity ID nor a valid UUID for dictionary value @ data['entity_id']. Got None"}}
01-03 03:42 ERROR root Task exited unexpected:{<Task finished name='Task-4' coro=<HassWs.run() done, defined at /root/hass.py:18> exception=ValueError('Unexpected response from Supervisor while connecting.')>}

Then I noticed that the configuration example is not quite consistent in structure and adapted the sensors as follows:

host: 10.11.13.24
password: vbus
sensors:
  - switch.to_publish_as_sensor1
  - light.to_publish_as_sensor2
  - input_boolean.to_publish_as_sensor_3
  - input_number.to_publish_as_sensor_4
  - sensor.to_publish_as_sensor_5
json_server: true

The log now looks as follows (better?):

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Resol VBus
 Addon to provide json VBus data and emulate Extension Modules for Resol Deltasol controllers.
-----------------------------------------------------------
 Add-on version: 0.0.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.4  (amd64 / qemux86-64)
 Home Assistant Core: 2022.12.9
 Home Assistant Supervisor: 2022.12.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
01-03 03:53 INFO VBusCon Connecting to VBus device at 10.11.13.24
01-03 03:53 INFO Websock Setup listener
01-03 03:53 INFO WServer Setup web app.
01-03 03:53 INFO WServer Listening to VBus.
01-03 03:53 INFO WServer Setup TCP web server on port 26514.
01-03 03:53 INFO DevSim  Connection manager started.
01-03 03:53 INFO Websock Connecting...
01-03 03:53 INFO Websock Connection established, listening to state events...

Is this correct? If not, where is my issue? What should I do next, to get the data to Home Assistant.

Thanks and regards Hoppel

chiefdeputy commented 1 year ago

This Addon currently only works the other way around. It does not listen to VBus and publishes the entities to Home Assistant, It listen to Home Assistant entities and publish them as a virtual ExtensionModule on the VBus.

hoppel118 commented 1 year ago

OK, sorry, I don't want to waste your time. But I don't understand what that exactly means. As already said, I am new to home assistant and I don't think, that I can solve this with my present knowledge.

Perhaps it would be more promising if I try to install it as follows:

https://github.com/danielwippermann/resol-vbus/issues/32#issuecomment-1369601863

What do you think about it?

Thanks Hoppel