Home Assistant


#21

this is all you need currently, all other info is auto-detected …


#22

Dear Cereal,

Thank you for your answer.
However, in 0.77 it did not work, updating to 0.78 solved it.
So there was a bug :slight_smile:
Thanks again!


#23

0.82 will have velbus thermostat support

next up are the blinds, but this is a bit more tricky to implement as i don’t own these modules …


#24

so there was a bug in 0.77, need to check this out then


#25

cool so version 0.82 will have the thermostat function? Been waiting for ages for that :wink: thanks man


#26

hmm, they delayed it to 0.83 …

so the just release 0.82 does not have it


#27

dear I have tried several times to get the Home Assistant working, but I can not, I currently have version 0.85.0
I do the settings but at this moment I see in the log that a scan is done of the bus, but I do not see any Sensors / switch … appear in HA, my setting is currently:

velbus:
port: ‘/ dev / ttyACM0’

What do I have to do to get this working?

greetings Joram


#28

Hi

Just a thought, is your Velbus USB device definitely assigned /dev/ttyACM0 ?

For example, do you have anything else plugged in that might be assigned ttyACM0?

You could check if there is a symlink in /dev/serial/by-id/ that is named as the Vellerman / Velbus interface and points to the assigned ttyACM ?


#29

the connection between ha works but nothing appears in ha. I have to put more in the config file outside the usb connection


#30

I was under the impression that the latest version now automatically detects your Velbus modules.

So (with the risk of sounds very dull), as you absolutely sure that ttyACM0 is your Velbus adapter?

Or…

Do you need to trigger a scan?


#31

HA log : core-ssh:~# hassio homeassistant logs

2019-01-13 12:21:38 INFO (Thread-2) [velbus] Processing message b’\x0f\xfbg\x08\xbe"\x02+\x02I\x06A\xe8\x04’
2019-01-13 12:21:38 INFO (Thread-2) [velbus] New message: {“name”: “CounterStatusMessage”, “priority”: 251, “address”: 103, “rtr”: false, “pulses”: 800, “counter”: 36373065, “kwh”: 0, “delay”: 1601, “watt”: 0, “channel”: 3}
2019-01-13 12:21:39 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\x1e\x08\xed\xaa\x003\x00\x00\xc0\n<\x04’
2019-01-13 12:21:39 WARNING (Thread-2) [velbus] received unrecognized command 237
2019-01-13 12:21:40 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\xfe\x07\xa9\x02y\x11\xad\x00\x00\x0f\x04’
2019-01-13 12:21:40 WARNING (Thread-2) [velbus] received unrecognized command 169
2019-01-13 12:21:40 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\xfe\x08\xac\x02\x00 63.3X\x04’
2019-01-13 12:21:40 WARNING (Thread-2) [velbus] received unrecognized command 172
2019-01-13 12:21:40 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\xfe\x08\xac\x02\x05 mm/h\xac\x04’
2019-01-13 12:21:40 WARNING (Thread-2) [velbus] received unrecognized command 172
2019-01-13 12:21:40 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\xfe\x04\xac\x02\n\x00<\x04’
2019-01-13 12:21:40 WARNING (Thread-2) [velbus] received unrecognized command 172
2019-01-13 12:21:40 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\xfe\x08\xac\x04\x00 452e\x04’
2019-01-13 12:21:40 WARNING (Thread-2) [velbus] received unrecognized command 172
2019-01-13 12:21:40 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\xfe\x08\xac\x04\x055 lux\x8d\x04’
2019-01-13 12:21:40 WARNING (Thread-2) [velbus] received unrecognized command 172
2019-01-13 12:21:40 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\xfe\x04\xac\x04\n\x00:\x04’
2019-01-13 12:21:40 WARNING (Thread-2) [velbus] received unrecognized command 172
2019-01-13 12:21:40 INFO (Thread-2) [velbus] Processing message b’\x0f\xfbS\x08\xedA\x02\xa7\x00\x00\xc0\n\xfa\x04’
2019-01-13 12:21:40 WARNING (Thread-2) [velbus] received unrecognized command 237
2019-01-13 12:21:42 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\x0e\x08\xedA\x02\xb9\x00\x00\x00\n\xed\x04’
2019-01-13 12:21:42 WARNING (Thread-2) [velbus] received unrecognized command 237
2019-01-13 12:21:43 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\x16\x07\xe6\x12\xc0\x03\x1a\xe0\xc4\x04' 2019-01-13 12:21:43 INFO (Thread-2) [velbus] New message: {"name": "SensorTemperatureMessage", "priority": 251, "address": 22, "rtr": false, "cur": 9.375, "min": 1.6875, "max": 13.4375} 2019-01-13 12:21:43 INFO (Thread-2) [velbus] Processing message b'\x0f\xfbg\x03\xbd\x01\x00\xce\x04' 2019-01-13 12:21:43 INFO (Thread-2) [velbus] New message: {"name": "CounterStatusRequestMessage", "priority": 251, "address": 103, "rtr": false} 2019-01-13 12:21:43 INFO (Thread-2) [velbus] Processing message b'\x0f\xfbg\x08\xbe \x02O.\x06B\x82\x04’
2019-01-13 12:21:43 INFO (Thread-2) [velbus] New message: {“name”: “CounterStatusMessage”, “priority”: 251, “address”: 103, “rtr”: false, “pulses”: 800, “counter”: 38743648, “kwh”: 0, “delay”: 1602, “watt”: 0, “channel”: 1}
2019-01-13 12:21:44 INFO (Thread-2) [velbus] Processing message b’\x0f\xfbK\x08\xed\xc1\x03\xff\x10\x00\xc0\n\x19\x04’
2019-01-13 12:21:44 WARNING (Thread-2) [velbus] received unrecognized command 237
2019-01-13 12:21:44 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\x04\x08\xed\x02\x00\x1d\x04\x00\x00\n\xd0\x04’
2019-01-13 12:21:44 INFO (Thread-2) [velbus] New message: {“name”: “ModuleStatusPirMessage”, “priority”: 251, “address”: 4, “rtr”: false}
2019-01-13 12:21:45 INFO (Thread-2) [velbus] Processing message b’\x0f\xfbg\x03\xbd\x01\x00\xce\x04’
2019-01-13 12:21:45 INFO (Thread-2) [velbus] New message: {“name”: “CounterStatusRequestMessage”, “priority”: 251, “address”: 103, “rtr”: false}
2019-01-13 12:21:45 INFO (Thread-2) [velbus] Processing message b’\x0f\xfbg\x08\xbe \x02O.a\x06A\x82\x04’
2019-01-13 12:21:45 INFO (Thread-2) [velbus] New message: {“name”: “CounterStatusMessage”, “priority”: 251, “address”: 103, “rtr”: false, “pulses”: 800, “counter”: 38743649, “kwh”: 0, “delay”: 1601, “watt”: 0, “channel”: 1}
2019-01-13 12:21:46 INFO (Thread-2) [velbus] Processing message b’\x0f\xfb\x1a\x08\xbe \x00\x82\xba\xe0\x0e\xc5\x07\x04’
2019-01-13 12:21:46 INFO (Thread-2) [velbus] New message: {“name”: “CounterStatusMessage”, “priority”: 251, “address”: 26, “rtr”: false, “pulses”: 800, “counter”: 8567520, “kwh”: 0, “delay”: 3781, “watt”: 0, “channel”: 1}

Config file /config/configuration.yaml

homeassistant:

Name of the location where Home Assistant is running

name: Home

Location required to calculate the time the sun rises and sets

latitude: 0
longitude: 0

Impacts weather/sunrise data (altitude above sea level in meters)

elevation: 0

metric for Metric, imperial for Imperial

unit_system: metric

Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones

time_zone: UTC

Customization file

customize: !include customize.yaml

Show links to resources in log and frontend

introduction:

Enables the frontend

frontend:

Enables configuration UI

config:

Uncomment this if you are using SSL/TLS, running in Docker container, etc.

http:

base_url: example.duckdns.org:8123

Checks for available updates

Note: This component will send some information about your system to

the developers to assist with development of Home Assistant.

For more information, please see:

https://home-assistant.io/blog/2016/10/25/explaining-the-updater/

updater:

Optional, allows Home Assistant developers to focus on popular components.

include_used_components: true

Discover some devices automatically

discovery:

Allows you to issue voice commands from the frontend in enabled browsers

conversation:

Enables support for tracking state changes over time

history:

View all events in a logbook

logbook:

Enables a map showing the location of tracked devices

map:

Track the sun

sun:

Sensors

sensor:

Weather prediction

  • platform: yr

Text to speech

tts:

  • platform: google

Cloud

cloud:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

velbus:
port: ‘/dev/ttyACM0’

switch 1:
platform: velbus