Hunter Douglas PowerView Gen 3 integration

andrewfg · December 12, 2024, 5:52pm

The manufacturer provides a standard firmware that you can flash on it to make it function as a BLE network interface for Wireshark.

Then you can sniff the traffic while you pair the device with the PowerView app. And one of the first few transactions contains the 32 byte encryption key.

cloom · December 12, 2024, 6:19pm

So I will have to forget my device and re-pair them?

Is it the same key for all the device? Or 1 key per device?

I have ESPs (ESP32 and ESP8266) so I would prefer to use them if that’s feasible.

If you have special hardware, it seems I cannot use my integrated bluetooth (Lenovo X1 Gen9) to sniff traffic with Wireshark?

andrewfg · December 12, 2024, 6:48pm

Yes.

It is the same key for each user account.

@patman did that I think.

Probably it is regular Bluetooth rather than BLE…

patman · December 14, 2024, 5:32pm

JFYI: I did not yet have enough time to succeed on using ESP32. I sniffed via recording the BT traffic on my mobile using the PowerView app.

cloom · December 15, 2024, 2:57pm

I guess you need to have root access on your device? I only have 2 corporate phones I cannot use for this.

I’ll see if I can get time to have something to sniff BLE during the holidays. Confidence: 15%

ad1217 · December 28, 2024, 4:04am

You can also just grab the key out of the app data if you have root on an Android phone or an emulator. The emulator doesn’t even need to support bluetooth if you are logging in with an online account. I successfully extracted mine using Waydroid.

sqlite3 ~/.local/share/waydroid/data/data/com.hunterdouglas.powerview/databases/ExdadUesc0LMXnTCcTu4_7 'select home_key from homes;'

Not sure if the file name there is different for every user. On a real phone this would be at /data/data/com.hunterdouglas.powerview/databases/.

cloom · December 28, 2024, 7:29pm

Thank you so much @ad1217 ! I got my “key”.

I now need to setup an ESP as a bluetooth proxy as I don’t have any BLE adapter to plug into my NAS where I run HAOS in a VM.

Another week of holiday, that’s my #1 project

I will try the custom_component from @patman:

@patman do you plan to propose to integrate it in HA core at some point?

patman · December 28, 2024, 7:53pm

That is quite a far way to get there, but in general, why not. First I need to get a clean code to integrate it with HACS as default repository, when it’s stable I can look further. For the moment, I still need to figure out really basic things, e.g. how much I can reuse from the existing integration with the hub, to avoid double work.
Nevertheless, my shades work well and stable since months (but I only have one simple type …).

cloom · December 29, 2024, 6:18pm

Thanks. If I can be of any help, let me know.

So far I have:

Added a bluetooth proxy via an ESP device as I don’t have bluetooth on my NAS where HA runs into a VM
Added your custom component hdpv_ble
I can see my Duettes blinds:
I added one and I can see when I open or close it with the app (and I guess with the remote as well)

Question:

I have the bluetooth “encryption/home key” but I don’t know if I can use it to also control the blinds ? Where should I add it?

Let me know if you want me to test some stuff. I need to place the ESPHome Bluetooth proxy somewhere final, I have other duties for it but I can develop on another one if I need to test the stability of the system.

cloom · December 30, 2024, 10:50am

So I easily found where to add the key

github.com

patman15/hdpv_ble/blob/8b0bccee6ba6eb95e52a55d50102e8adb378984a/custom_components/hunterdouglas_powerview_ble/const.py#L23


      
          # )
          
          
          DOMAIN: Final[str] = "hunterdouglas_powerview_ble"
          LOGGER: Final = logging.getLogger(__package__)
          MFCT_ID: Final[int] = 2073
          TIMEOUT: Final[int] = 5
          
          # put the key here, needs to be 16 bytes long, e.g.
          # HOME_KEY: Final[bytes] = b"\x00\x01\x02\x03\x04\x05\x06\x07\x08\x09\x0a\x0b\x0c\x0d\x0e\x0f"
          HOME_KEY: Final[bytes] = b""
          
          
          # attributes (do not change)
          ATTR_RSSI: Final[str] = "rssi"

I added it the way it is requested and restarted HA.

I now see the controls but they fail with:

Failed to perform the action cover/stop_cover. Device did not send confirmation.

I have gathered the logs and opened a bug:

github.com/patman15/hdpv_ble

Cannot control Duette (6) via ESPHome bluetooth proxy

opened 10:49AM - 30 Dec 24 UTC

cloom

### Checklist - [X] I have enabled debug logging for my installation. - [X] I h…ave filled out the issue template to the best of my ability. - [X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue). - [X] This issue is not a duplicate issue of any [previous issue](https://github.com/patman15/hdpv_ble/issues?q=is%3Aissue+label%3A%22Bug%22+). ### Describe the issue Hello, I might not have done things in order (see reproduction steps) but I should have the proper HOME_KEY setup in the const.py file of the custom_component. I can see the status of the blinds I have added to the component: opening, closing, open, close, percentage of opening, battery level. I cannot control the blinds, I get the following error when I try to open, close, stop: ``` Failed to perform the action cover/stop_cover. Device did not send confirmation. ``` I have enabled the logs, restarted HA, tried to control a blind, waiting for the error and stopped the logs. Let me know if there is anything I can do to test. ### Reproduction steps 1. Configure blinds normally (with the app on the phone) 2. Add a remote (optional but in case this has an impact) 3. Install the hdpv_ble custom component 4. Reboot HA 5. Add blinds to the component and verify you can see the status of the blinds 6. Get the HOME_KEY using [Waydroid](https://waydro.id/) 7. Convert the HOME_KEY into the python byte format and add it to the [const.py file](https://github.com/patman15/hdpv_ble/blob/main/custom_components/hunterdouglas_powerview_ble/const.py#L23) 8. Restart HA 9. Test any command: open, close, stop. ### Debug logs ```text 2024-12-30 11:34:38.330 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hunterdouglas_powerview_ble which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-12-30 11:34:38.333 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-12-30 11:34:38.337 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-12-30 11:34:38.339 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-12-30 11:34:38.342 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dlight which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-12-30 11:34:55.417 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.cold_water_daily (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using native unit of measurement 'm3' which is not a valid unit for the device class ('water') it is using; expected one of ['m³', 'CCF', 'gal', 'ft³', 'L']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22 2024-12-30 11:34:55.434 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.hot_water_daily (<class 'homeassistant.components.utility_meter.sensor.UtilityMeterSensor'>) is using native unit of measurement 'm3' which is not a valid unit for the device class ('water') it is using; expected one of ['m³', 'CCF', 'gal', 'ft³', 'L']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+utility_meter%22 2024-12-30 11:34:55.947 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Setup of <ConfigEntry entry_id=01JG9SMNNAGXESNZCK1HXANKBR version=1 domain=hunterdouglas_powerview_ble title=DUT:DDB8 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=F9:4F:22:3F:6B:D5> 2024-12-30 11:34:55.948 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Initializing coordinator for DUT:DDB8 (F9:4F:22:3F:6B:D5) 2024-12-30 11:34:55.949 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:DDB8: querying device info 2024-12-30 11:34:55.949 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Connecting DUT:DDB8 2024-12-30 11:34:55.950 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Setup of <ConfigEntry entry_id=01JG9SY03783Q865PW4SK8TP9V version=1 domain=hunterdouglas_powerview_ble title=DUT:5CDB state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=E7:B3:D2:48:EA:AB> 2024-12-30 11:34:55.950 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Initializing coordinator for DUT:5CDB (E7:B3:D2:48:EA:AB) 2024-12-30 11:34:55.951 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB: querying device info 2024-12-30 11:34:55.951 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Connecting DUT:5CDB 2024-12-30 11:34:58.915 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for eink @ 192.168.86.21: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.86.21', port=6053))]: [Errno 113] Connect call failed ('192.168.86.21', 6053) (SocketAPIError) 2024-12-30 11:34:58.979 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for kitchen_worktop @ 192.168.86.86: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.86.86', port=6053))]: [Errno 113] Connect call failed ('192.168.86.86', 6053) (SocketAPIError) 2024-12-30 11:35:01.129 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] connect took 5s 2024-12-30 11:35:01.132 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying manufacturer(2a29) 2024-12-30 11:35:01.282 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying model(2a24) 2024-12-30 11:35:01.415 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying serial_nr(2a25) 2024-12-30 11:35:01.707 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying hw_rev(2a27) 2024-12-30 11:35:01.905 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] connect took 5s 2024-12-30 11:35:01.906 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying manufacturer(2a29) 2024-12-30 11:35:01.911 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying fw_rev(2a26) 2024-12-30 11:35:02.012 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying sw_rev(2a28) 2024-12-30 11:35:02.113 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying model(2a24) 2024-12-30 11:35:02.205 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Disconnecting device DUT:DDB8 2024-12-30 11:35:02.256 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying serial_nr(2a25) 2024-12-30 11:35:02.311 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Disconnected from F9:4F:22:3F:6B:D5 2024-12-30 11:35:02.312 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:DDB8 device data: {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': 'DDB8B563D3E19342', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:02.353 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:DDB8: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': 'DDB8B563D3E19342', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:02.355 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:DDB8: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': 'DDB8B563D3E19342', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:02.356 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:DDB8: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': 'DDB8B563D3E19342', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:02.361 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:DDB8: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': 'DDB8B563D3E19342', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:02.363 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:DDB8: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': 'DDB8B563D3E19342', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:02.365 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] BLE event BluetoothChange.ADVERTISEMENT: {2073: b'\xfb\xd7\x06\xa0\x0f\x00\x00\x00\xe2'} 2024-12-30 11:35:02.365 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] data sample {'rssi': -69, 'current_position': 100.0, 'position2': 0, 'position3': 0, 'tilt': 0, 'home_id': 55291, 'type_id': 6, 'is_opening': False, 'is_closing': False, 'battery_charging': False, 'battery_level': 100, 'resetMode': False, 'resetClock': True} 2024-12-30 11:35:02.510 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying hw_rev(2a27) 2024-12-30 11:35:02.720 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying fw_rev(2a26) 2024-12-30 11:35:02.833 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] querying sw_rev(2a28) 2024-12-30 11:35:03.034 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Disconnecting device DUT:5CDB 2024-12-30 11:35:03.134 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Disconnected from E7:B3:D2:48:EA:AB 2024-12-30 11:35:03.134 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB device data: {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': '5CDBDE760B8E1908', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:03.135 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': '5CDBDE760B8E1908', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:03.137 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': '5CDBDE760B8E1908', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:03.138 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': '5CDBDE760B8E1908', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:03.144 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': '5CDBDE760B8E1908', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:03.146 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB: device_info, {'manufacturer': 'Hunter Douglas', 'model': '6', 'serial_nr': '5CDBDE760B8E1908', 'hw_rev': '171104', 'fw_rev': '30', 'sw_rev': '418'} 2024-12-30 11:35:03.147 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] BLE event BluetoothChange.ADVERTISEMENT: {2073: b'\xfb\xd7\x06\x08\x06\x00\x00\x00\xe2'} 2024-12-30 11:35:03.148 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] data sample {'rssi': -74, 'current_position': 38.6, 'position2': 0, 'position3': 0, 'tilt': 0, 'home_id': 55291, 'type_id': 6, 'is_opening': False, 'is_closing': False, 'battery_charging': False, 'battery_level': 100, 'resetMode': False, 'resetClock': True} 2024-12-30 11:35:03.221 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({%- set p_debut_machine = states('input_number.washing_machine_power_at_start') | round(2) -%} {%- set p_fin_machine = states('sensor.washing_machine_energy') | round(2) -%} {%- set p_cycle_machine = p_fin_machine - p_debut_machine -%} {{ (p_cycle_machine) | round(2) }}) renders=2> Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1928, in forgiving_round value = round(float(value), precision) ~~~~~^^^^^^^ ValueError: could not convert string to float: 'unknown' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 631, in async_render render_result = _render_with_context(self.template, compiled, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2733, in _render_with_context return template.render(**kwargs) ~~~~~~~~~~~~~~~^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1304, in render self.environment.handle_exception() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 939, in handle_exception raise rewrite_traceback_stack(source=source) File "<template>", line 1, in top-level template code File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1933, in forgiving_round raise_no_default("round", value) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1909, in raise_no_default raise ValueError( ...<2 lines>... ) ValueError: Template error: round got invalid input 'unknown' when rendering template '{%- set p_debut_machine = states('input_number.washing_machine_power_at_start') | round(2) -%} {%- set p_fin_machine = states('sensor.washing_machine_energy') | round(2) -%} {%- set p_cycle_machine = p_fin_machine - p_debut_machine -%} {{ (p_cycle_machine) | round(2) }}' but no default was specified The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 748, in async_render_to_info render_info._result = self.async_render( # noqa: SLF001 ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ variables, strict=strict, log_fn=log_fn, **kwargs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 633, in async_render raise TemplateError(err) from err homeassistant.exceptions.TemplateError: ValueError: Template error: round got invalid input 'unknown' when rendering template '{%- set p_debut_machine = states('input_number.washing_machine_power_at_start') | round(2) -%} {%- set p_fin_machine = states('sensor.washing_machine_energy') | round(2) -%} {%- set p_cycle_machine = p_fin_machine - p_debut_machine -%} {{ (p_cycle_machine) | round(2) }}' but no default was specified 2024-12-30 11:35:03.235 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: round got invalid input 'unknown' when rendering template '{%- set p_debut_machine = states('input_number.washing_machine_power_at_start') | round(2) -%} {%- set p_fin_machine = states('sensor.washing_machine_energy') | round(2) -%} {%- set p_cycle_machine = p_fin_machine - p_debut_machine -%} {{ (p_cycle_machine) | round(2) }}' but no default was specified') while processing template 'Template<template=({%- set p_debut_machine = states('input_number.washing_machine_power_at_start') | round(2) -%} {%- set p_fin_machine = states('sensor.washing_machine_energy') | round(2) -%} {%- set p_cycle_machine = p_fin_machine - p_debut_machine -%} {{ (p_cycle_machine) | round(2) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.washing_machine_last_energy' 2024-12-30 11:35:03.241 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({%- set p_debut_dish = states('input_number.dishwasher_power_at_start') | round(2) -%} {%- set p_fin_dish = states('sensor.dishwasher_energy') | round(2) -%} {%- set p_cycle_dish = p_fin_dish - p_debut_dish -%} {{ (p_cycle_dish) | round(2) }}) renders=2> Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1928, in forgiving_round value = round(float(value), precision) ~~~~~^^^^^^^ ValueError: could not convert string to float: 'unknown' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 631, in async_render render_result = _render_with_context(self.template, compiled, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2733, in _render_with_context return template.render(**kwargs) ~~~~~~~~~~~~~~~^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1304, in render self.environment.handle_exception() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 939, in handle_exception raise rewrite_traceback_stack(source=source) File "<template>", line 1, in top-level template code File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1933, in forgiving_round raise_no_default("round", value) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1909, in raise_no_default raise ValueError( ...<2 lines>... ) ValueError: Template error: round got invalid input 'unknown' when rendering template '{%- set p_debut_dish = states('input_number.dishwasher_power_at_start') | round(2) -%} {%- set p_fin_dish = states('sensor.dishwasher_energy') | round(2) -%} {%- set p_cycle_dish = p_fin_dish - p_debut_dish -%} {{ (p_cycle_dish) | round(2) }}' but no default was specified The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 748, in async_render_to_info render_info._result = self.async_render( # noqa: SLF001 ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ variables, strict=strict, log_fn=log_fn, **kwargs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 633, in async_render raise TemplateError(err) from err homeassistant.exceptions.TemplateError: ValueError: Template error: round got invalid input 'unknown' when rendering template '{%- set p_debut_dish = states('input_number.dishwasher_power_at_start') | round(2) -%} {%- set p_fin_dish = states('sensor.dishwasher_energy') | round(2) -%} {%- set p_cycle_dish = p_fin_dish - p_debut_dish -%} {{ (p_cycle_dish) | round(2) }}' but no default was specified 2024-12-30 11:35:03.250 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: round got invalid input 'unknown' when rendering template '{%- set p_debut_dish = states('input_number.dishwasher_power_at_start') | round(2) -%} {%- set p_fin_dish = states('sensor.dishwasher_energy') | round(2) -%} {%- set p_cycle_dish = p_fin_dish - p_debut_dish -%} {{ (p_cycle_dish) | round(2) }}' but no default was specified') while processing template 'Template<template=({%- set p_debut_dish = states('input_number.dishwasher_power_at_start') | round(2) -%} {%- set p_fin_dish = states('sensor.dishwasher_energy') | round(2) -%} {%- set p_cycle_dish = p_fin_dish - p_debut_dish -%} {{ (p_cycle_dish) | round(2) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.dishwasher_last_energy' 2024-12-30 11:35:08.285 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] Conflict: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2024-12-30 11:35:14.104 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] Conflict: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2024-12-30 11:35:21.044 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] Conflict: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2024-12-30 11:35:26.734 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] Conflict: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2024-12-30 11:35:35.326 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] Conflict: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2024-12-30 11:35:48.200 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] Conflict: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2024-12-30 11:36:07.407 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] Conflict: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2024-12-30 11:36:28.656 ERROR (MainThread) [homeassistant.components.telegram_bot.polling] Conflict: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running 2024-12-30 11:36:33.410 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] close cover 2024-12-30 11:36:33.410 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB close 2024-12-30 11:36:33.410 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] DUT:5CDB setting position to 0 2024-12-30 11:36:33.411 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Connecting DUT:5CDB 2024-12-30 11:36:34.592 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] connect took 1s 2024-12-30 11:36:34.595 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] sending cmd: b'WD\xe9]\xe5FKa/\xe7\xae\xa0\xa8' 2024-12-30 11:36:34.600 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] waiting for response 2024-12-30 11:36:35.185 DEBUG (MainThread) [custom_components.hunterdouglas_powerview_ble] Disconnected from E7:B3:D2:48:EA:AB 2024-12-30 11:36:39.602 ERROR (MainThread) [custom_components.hunterdouglas_powerview_ble] Error: TimeoutError - Device did not send confirmation. 2024-12-30 11:36:39.603 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140030495755712] Unexpected exception Traceback (most recent call last): File "/usr/local/lib/python3.13/asyncio/tasks.py", line 507, in wait_for return await fut ^^^^^^^^^ File "/config/custom_components/hunterdouglas_powerview_ble/api.py", line 106, in _wait_event await self._data_event.wait() File "/usr/local/lib/python3.13/asyncio/locks.py", line 213, in wait await fut asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/config/custom_components/hunterdouglas_powerview_ble/api.py", line 157, in _cmd await asyncio.wait_for(self._wait_event(), timeout=TIMEOUT) File "/usr/local/lib/python3.13/asyncio/tasks.py", line 506, in wait_for async with timeouts.timeout(timeout): ~~~~~~~~~~~~~~~~^^^^^^^^^ File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__ raise TimeoutError from exc_val TimeoutError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<7 lines>... ) ^ File "/usr/src/homeassistant/homeassistant/core.py", line 2802, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2845, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ hass, entity, func, data, call.context ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call result = await task ^^^^^^^^^^ File "/config/custom_components/hunterdouglas_powerview_ble/cover.py", line 158, in async_close_cover await self._coord.api.close() File "/config/custom_components/hunterdouglas_powerview_ble/api.py", line 219, in close await self.set_position(CLOSED_POSITION, disconnect=False) File "/config/custom_components/hunterdouglas_powerview_ble/api.py", line 195, in set_position await self._cmd( ...<8 lines>... ) File "/config/custom_components/hunterdouglas_powerview_ble/api.py", line 160, in _cmd raise TimeoutError("Device did not send confirmation.") from ex TimeoutError: Device did not send confirmation. ```

Sorry for the noise in the logs, I have other small issues to fix but they are not impacting this issue

patman · December 30, 2024, 10:50am

You need to add it to the const.py file.

Let me know if you want me to test some stuff.

Thanks, will come back to this offer, at the moment, I just finished a fake shade that allows to gather the encryption key and run further tests. Further, I’m working on integrating new types and align with the core integration on, e.g. data types for code reuse.

hungarianhc · January 23, 2025, 7:31am

Wondering if someone can help me troubleshoot…

The integration with my gen3 system has been rock solid basically since it was released. Then this morning, I noticed my shades didn’t’ open on schedule. I didn’t think much of it, and I used the PowerView app. But then they didn’t close in the evening… Closed w/ PowerView.

I looked into Home Assistant, and I see the dreaded red exclamation point that says, “Failed setup, will retry: Connection error to PowerView Hub XXX.XXX.X.XXX: Timeout in communicating with the hub.

I’m not sure what it can be or what caused it. I rebooted the hub. I also made sure I could ping it from the host that Home Assistant is running. No problem. I have a different 3rd party integration with Hunter Douglas that is working as well. Any ideas? Thanks!

alindner · January 23, 2025, 1:28pm

I’ve had the same issue. Powered cycled the hub and it went back to normal. Mine lasted about a year before requiring a power cycle.

hungarianhc · January 23, 2025, 7:48pm

Yeah. I tried power cycling it, and no change. How would I go about troubleshooting this? I find it interesting that the PowerView app still works just fine.

I actually have two 3rd party integrations w/ Hunter Douglas. One is Brilliant Control (the wall switches), and the other is Home Assistant. The Brilliant Control integration is working just fine. So is the PowerView app. Thus, I believe the issue is on the Home Assistant side. How do I get the right detailed logs to troubleshoot this?

UPDATE: I deleted the integration, and I tried to start over from scratch. This did not work. When I try to manually add it back, it’s not connecting via IP address. Again, The Brilliant integration and the PowerView app still work.

UPDATE 2: No idea what the root issue was, but I just deleted all of my gateways and re-added them. Now my system is working well again… Go figure. Clearly not a Home Assistant issue!

coreywilner · March 5, 2025, 9:07pm

I hadn’t realized that the Gen 3 was added to the powerview integration, I have been using the HomeKit Device integration for the Gen 3 with reasonable success. I also have a Gen 2 unit working just fine with the powerview integration.

I added the Gen 3 to the powerview integration and it is added without error and a ton of entities are added for my 5 shades. However, ALL the entities are showing up as unavailable.

Do I have to delete the HomeKit Device information (and possibly reset my hub)? Is there a setting I need to check in my hub?

Let me know if I’m missing something.

TheBigBoss · May 20, 2025, 8:55pm

Any idea how to extract the key on IOS?

siteexperts · June 18, 2025, 3:59am

I am looking at the Powerview+ Gen 3 shades. These are shades that can be controlled directly (hardwired) in addition to via bluetooth. If I have a gen3 hub, does this integration communicate with the hub and then the shades using the wired connection or is it only over bluetooth. Hoping to keep everything hardwired for more robustness.

Thanks

andrewfg · June 18, 2025, 8:56am

The integration talks to the gateway via TCP and the gateway passes the command to the shades via Bluetooth low energy.

siteexperts · June 18, 2025, 3:37pm

So the direct communication via the hardwire using the powerview+ is limited only to the Hunter Douglas App?

Anyone know if the bond pro also work wirelessly? Bond Pro is listed as “officially” supported by Hunter Douglas.

nugget · June 18, 2025, 3:46pm

Your link doesn’t describe any direct communication via the hardwire. It says that control is still handled by the gateway, just like it is with BLE connected shades. I wouldn’t expect the Home Assistant integration to know or care how the gateway is communicating with the individual shades.

“PowerView Gateway: Constantly Connected - The PowerView Gateway works with the PowerView+ Gen 3 Smart Power Supply to communicate with your PowerView+ shades.”

I didn’t know the “Gen 3 Smart Power Supply” existed until you linked it above, so this is just my interpretation of the marketing text, not direct experience.