-
-
Save MoritzBuetzer/6441d4045f989ef57aed915250bb4020 to your computer and use it in GitHub Desktop.
- platform: rest | |
resource: http://[DEVICE_IP]/ai?command=getDeviceStatus | |
name: 'V-Zug CookTopInduktion V6000' | |
authentication: digest | |
username: !secret vzug.username | |
password: !secret vzug.password | |
json_attributes: | |
- DeviceName | |
- Serial | |
- Inactive | |
- Status | |
- Program | |
- ProgramEnd | |
- platform: template | |
sensors: | |
vzug_cooktopinduktion_devicename: | |
friendly_name: 'V-Zug CookTopInduktion V6000 DeviceName' | |
value_template: "{{ state_attr('sensor.v_zug_cooktopinduktion_v6000', 'DeviceName') }}" | |
vzug_cooktopinduktion_serial: | |
friendly_name: 'V-Zug CookTopInduktion V6000 Serial' | |
value_template: "{{ state_attr('sensor.v_zug_cooktopinduktion_v6000', 'Serial') }}" | |
vzug_cooktopinduktion_inactive: | |
friendly_name: 'V-Zug CookTopInduktion V6000 Inactive' | |
value_template: "{{ state_attr('sensor.v_zug_cooktopinduktion_v6000', 'Inactive') }}" | |
vzug_cooktopinduktion_status: | |
friendly_name: 'V-Zug CookTopInduktion V6000 Status' | |
value_template: "{{ state_attr('sensor.v_zug_cooktopinduktion_v6000', 'Status') }}" | |
vzug_cooktopinduktion_program: | |
friendly_name: 'V-Zug CookTopInduktion V6000 Program' | |
value_template: "{{ state_attr('sensor.v_zug_cooktopinduktion_v6000', 'Program') }}" | |
vzug_cooktopinduktion_end: | |
friendly_name: 'V-Zug CookTopInduktion V6000 End' | |
value_template: "{{ state_attr('sensor.v_zug_cooktopinduktion_v6000', 'ProgramEnd')['End'] }}" | |
vzug_cooktopinduktion_endtype: | |
friendly_name: 'V-Zug CookTopInduktion V6000 End' | |
value_template: "{{ state_attr('sensor.v_zug_cooktopinduktion_v6000', 'ProgramEnd')['EndType'] }}" |
I'm not sure if this is still useful to anyone, but if I've noticed that the web UI always calls http://<ip>/hh?command=getZHMode
right before calling http://<ip>/ai?command=getDeviceStatus
.
If I do the same, then the amount of 501.03
errors is significantly reduced.
@izacus How can I combine this "wakeup" call with the rest call?
hi
i use the following config to get the engergy statistics:
sensor:
- platform: rest
name: 'V-Zug AdoraWash V4000 Eco Info'
json_attributes_path: "$.energy"
json_attributes:
- total
- lastMonth
- lastYear
- average
- program
resource: http://192.168.2.xx/hh?command=getEcoInfo
template:
- sensor:
- name: "V-Zug AdoraWash Energy total"
device_class: energy
state_class: total_increasing
unit_of_measurement: kWh
state: >
{{ state_attr('sensor.v_zug_adorawash_v4000_eco_info', 'total')}}
- name: "V-Zug AdoraWash Energy total"
That works with my adora wash v4000, AdoraDish V4000, Combair and Combisteamer v6000
but v-zug will change their api in the future. they will publish the new api.
but v-zug will change their api in the future. they will publish the new api.
Hello @asowlnowl, is there a way to know more about this new API effort? Do you have a contact with v-zug?
Hello @asowlnowl, is there a way to know more about this new API effort? Do you have a contact with v-zug?
they told me last fall that they have no eta yet. i just asked per contact form on their website for the api documentation.
FYI, I finally bit the bullet and created a proper integration for Home Assistant that can be installed using HACS.
The integration can be found here: https://github.com/siku2/hass-vzug
I used a lot of information in this thread for reference, so thank you all for sharing.
Nice one! Can’t wait to try it out. 👍
Thank you for this - only had basic date before now a lot more is in the HACS integration. Great stuff!
@siku2 awesome!
Awsome, Thanks
I have a AdoraDish V2000 I get the error "Einrichtung fehlgeschlage, wird erneut versucht" I guess the interface is not compatible with the V4000....
@simondaehler, can you create a new issue or discussion over at the repository? I would like to figure out what the issue is so the V2000 series can be supported as well, I just need a few things from your side and I don't want to clog up this thread.
@siku2 I'm using your integration with an adorawash_v2000. I set it up with the very first version, so at least this one did work.
I have both adorawash2000 and adoradry2000 and it works with latest version 0.31. Thanks a lot
I also tried
rest:
resource: http://192.168.1.111/ai?command=getDeviceStatus
sensor:
name: v_zug_oven
json_attributes:
- DeviceName
- Serial
- Inactive
- Status
- Program
- ProgramEnd
template:
state: "{{ state_attr('sensor.v_zug_oven', 'DeviceName') }}"
state: "{{ state_attr('sensor.v_zug_oven', 'Inactive') }}"
state: "{{ state_attr('sensor.v_zug_oven', 'Status') }}"
state: "{{ state_attr('sensor.v_zug_oven', 'Program') }}"
state: "{{ state_attr('sensor.v_zug_oven', 'ProgramEnd') }}"