loopj/home-assistant-vantage

Home Assistant integration for Vantage InFusion home automation controllers.

home-assistant-vantage's Issues

HA Core 2024.4 breaks the addon

System Health details

System Information

version	core-2024.4.0
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.2
os_name	Linux
os_version	6.1.73-haos-raspi
arch	aarch64
timezone	America/New_York
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4970
Installed Version	1.34.0
Stage	running
Available Repositories	1468
Downloaded Repositories	4

Home Assistant Cloud

logged_in	true
subscription_expiration	February 26, 2025 at 19:00
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	true
remote_server	us-east-1-0.ui.nabu.casa
certificate_status	ready
instance_id	239a2793dc35431885273f341225b65d
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 12.1
update_channel	stable
supervisor_version	supervisor-2024.03.1
agent_version	1.6.0
docker_version	24.0.7
disk_total	116.7 GB
disk_used	10.4 GB
healthy	true
supported	true
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	Terminal & SSH (9.10.0), File editor (5.8.0), Studio Code Server (5.15.0), Samba share (12.3.1)

Dashboards

dashboards	5
resources	0
views	18
mode	storage

Recorder

oldest_recorder_run	March 26, 2024 at 04:18
current_recorder_run	April 4, 2024 at 10:16
estimated_db_size	28.66 MiB
database_engine	sqlite
database_version	3.44.2

Checklist

• I have enabled debug logging for my installation
• I have filled out the issue template to the best of my ability
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue)
• This issue is not a duplicate of current issues

Describe the issue

As soon as Home Assistant is updated to the latest version (2024.4) the addon no longer loads, with errors in the notifications.

There is documented breaking changes on the HA dev blog which seems to fall in line with the errors. (https://www.home-assistant.io/blog/2024/04/03/release-20244/)

2024-04-04 10:16:01.075 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration vantage 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-04-04 10:16:01.079 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration vantage 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-04-04 10:16:33.759 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration 'vantage': Unable to import component: cannot import name 'Entity' from 'homeassistant.components.group' (/usr/src/homeassistant/homeassistant/components/group/__init__.py) File "/config/custom_components/vantage/__init__.py", line 30, in <module> File "/config/custom_components/vantage/entity.py", line 16, in <module> File "/config/custom_components/vantage/__init__.py", line 30, in <module> File "/config/custom_components/vantage/entity.py", line 16, in <module> 2024-04-04 10:16:37.353 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration vantage: cannot import name 'Entity' from 'homeassistant.components.group' (/usr/src/homeassistant/homeassistant/components/group/__init__.py) 2024-04-04 10:16:37.357 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration vantage: cannot import name 'Entity' from 'homeassistant.components.group' (/usr/src/homeassistant/homeassistant/components/group/__init__.py)

Reproduction steps

1. Update HA Core from the HA UI
2. Check notifications/addon status

...

Debug logs

2024-04-04 10:16:01.075 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration vantage 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-04-04 10:16:01.079 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration vantage 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-04-04 10:16:33.759 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration 'vantage': Unable to import component: cannot import name 'Entity' from 'homeassistant.components.group' (/usr/src/homeassistant/homeassistant/components/group/__init__.py)
File "/config/custom_components/vantage/__init__.py", line 30, in <module>
File "/config/custom_components/vantage/entity.py", line 16, in <module>
File "/config/custom_components/vantage/__init__.py", line 30, in <module>
File "/config/custom_components/vantage/entity.py", line 16, in <module>
2024-04-04 10:16:37.353 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration vantage: cannot import name 'Entity' from 'homeassistant.components.group' (/usr/src/homeassistant/homeassistant/components/group/__init__.py)
2024-04-04 10:16:37.357 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration vantage: cannot import name 'Entity' from 'homeassistant.components.group' (/usr/src/homeassistant/homeassistant/components/group/__init__.py)

Diagnostics dump

No response

Add state support for for shades/blinds

System Health details

System Information

version	core-2023.10.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.5
os_name	Linux
os_version	6.1.59
arch	x86_64
timezone	America/Chicago
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4934
Installed Version	1.33.0
Stage	running
Available Repositories	1331
Downloaded Repositories	50
HACS Data	ok

Home Assistant Cloud

logged_in	true
subscription_expiration	February 29, 2024 at 6:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	false
remote_server	us-east-1-1.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 11.1
update_channel	stable
supervisor_version	supervisor-2023.10.1
agent_version	1.6.0
docker_version	24.0.6
disk_total	116.7 GB
disk_used	45.3 GB
healthy	true
supported	true
board	generic-x86-64
supervisor_api	ok
version_api	ok
installed_addons	Studio Code Server (5.13.0), Mosquitto broker (6.3.1), Terminal & SSH (9.7.1), Glances (0.19.4), ESPHome (2023.10.4), chrony (2.6.2), Z-Wave JS (0.2.1), Network UPS Tools (0.12.2), Node-RED (15.0.0), EMQX (0.2.12), File editor (5.6.0), Home Assistant Google Drive Backup (0.111.1), openWakeWord (1.8.2), Piper (1.4.0), Whisper (1.0.0)

Dashboards

dashboards	6
resources	28
views	42
mode	storage

Recorder

oldest_recorder_run	October 23, 2023 at 2:31 AM
current_recorder_run	October 31, 2023 at 8:46 PM
estimated_db_size	2953.69 MiB
database_engine	sqlite
database_version	3.41.2

Checklist

• I have enabled debug logging for my installation
• I have filled out the issue template to the best of my ability
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue)
• This issue is not a duplicate of current issues

Describe the issue

Thank you very much for the support and time taken on this integration.

I have two QMotion QIS Shades/Blinds attached to my Vantage System. The integration brought them into Home assistant without issues and I have control of them but the state is always unknown.

Reproduction steps

Controlling the shades via Home assistant or Design Center the status in Home Assistant stays as unknown

Debug logs

2023-10-31 20:49:51.481 DEBUG (MainThread) [aiovantage.command_client.commands] Sending command: INVOKE 58 Blind.Close
2023-10-31 20:49:51.485 DEBUG (MainThread) [aiovantage.command_client.commands] Received response: R:INVOKE 58 0 Blind.Close
2023-10-31 20:49:51.531 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetBlindState 0 0 0 0 6591291
2023-10-31 20:49:52.341 DEBUG (MainThread) [aiovantage.command_client.commands] Sending command: INVOKE 58 Blind.Open
2023-10-31 20:49:52.351 DEBUG (MainThread) [aiovantage.command_client.commands] Received response: R:INVOKE 58 0 Blind.Open
2023-10-31 20:49:52.376 DEBUG (MainThread) [aiovantage.command_client.events] Received message: S:BLIND 58 100.000
2023-10-31 20:49:52.380 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetPosition 100000
2023-10-31 20:49:52.381 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetBlindState 1 0 100000 18894 6592146
2023-10-31 20:49:52.383 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetTravelTimes 0 18894 17351
2023-10-31 20:49:53.031 DEBUG (MainThread) [aiovantage.command_client.commands] Sending command: INVOKE 58 Blind.Stop
2023-10-31 20:49:53.036 DEBUG (MainThread) [aiovantage.command_client.commands] Received response: R:INVOKE 58 0 Blind.Stop
2023-10-31 20:49:53.073 DEBUG (MainThread) [aiovantage.command_client.events] Received message: S:BLIND 58 4.000
2023-10-31 20:49:53.075 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetPosition 4000
2023-10-31 20:49:53.076 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetBlindState 0 4000 4000 0 6592833
2023-10-31 20:49:53.615 DEBUG (MainThread) [aiovantage.command_client.commands] Sending command: INVOKE 58 Blind.Close
2023-10-31 20:49:53.620 DEBUG (MainThread) [aiovantage.command_client.commands] Received response: R:INVOKE 58 0 Blind.Close
2023-10-31 20:49:53.649 DEBUG (MainThread) [aiovantage.command_client.events] Received message: S:BLIND 58 0.000
2023-10-31 20:49:53.651 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetPosition 0
2023-10-31 20:49:53.652 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetBlindState 1 4000 0 653 6593419
2023-10-31 20:49:54.433 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 58 Blind.GetBlindState 0 0 0 0 6594192
2023-10-31 20:50:07.571 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 38 PowerSensor.GetPower 0
2023-10-31 20:50:07.573 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 66 PowerSensor.GetPower 0
2023-10-31 20:50:07.574 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 38 Sensor.GetLevel 0
2023-10-31 20:50:07.576 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 66 Sensor.GetLevel 0
2023-10-31 20:50:07.576 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 67 Sensor.GetLevel 0
2023-10-31 20:50:07.577 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 75 Sensor.GetLevel 0
2023-10-31 20:50:07.578 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 76 Sensor.GetLevel 0
2023-10-31 20:50:07.579 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 67 CurrentSensor.GetCurrent 0
2023-10-31 20:50:07.581 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 76 CurrentSensor.GetCurrent 0
2023-10-31 20:50:07.582 DEBUG (MainThread) [aiovantage.command_client.events] Received message: EL: 75 PowerSensor.GetPower 0
2023-10-31 20:50:08.228 DEBUG (MainThread) [aiovantage.command_client.events] Sending message: ECHO
2023-10-31 20:50:08.230 DEBUG (MainThread) [aiovantage.command_client.events] Received message: R:ECHO
2023-10-31 20:50:08.792 DEBUG (MainThread) [aiovantage.command_client.commands] Sending command: INVOKE 39 CurrentSensor.GetCurrent
2023-10-31 20:50:08.795 DEBUG (MainThread) [aiovantage.command_client.commands] Received response: R:INVOKE 39 0.000 CurrentSensor.GetCurrent
2023-10-31 20:50:08.796 DEBUG (MainThread) [aiovantage.command_client.commands] Sending command: INVOKE 67 CurrentSensor.GetCurrent
2023-10-31 20:50:08.798 DEBUG (MainThread) [aiovantage.command_client.commands] Received response: R:INVOKE 67 0.000 CurrentSensor.GetCurrent
2023-10-31 20:50:08.799 DEBUG (MainThread) [aiovantage.command_client.commands] Sending command: INVOKE 76 CurrentSensor.GetCurrent
2023-10-31 20:50:08.801 DEBUG (MainThread) [aiovantage.command_client.commands] Received response: R:INVOKE 76 0.000 CurrentSensor.GetCurrent

Diagnostics dump

No response

Generate Home Assistant events when a Vantage Task is started/stopped

Describe the problem

I'd like to be able to create automations in Home Assistant triggered by Vantage task state changes.

Describe the solution you'd like

Expose Vantage Task start/stop activity as events on the Home Assistant event bus.

Additional context

No response

Checklist

• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Expose Vantage Tasks to Home Assistant

• Allow running tasks by calling a custom service

Add support for PowerProfiles

Describe the problem

Loads have associated PowerProfile objects which describe, among other things, the maximum and minimum level of a load. Mostly we don't care about these profiles, since the Load.SetLevel interface normalizes levels for us.

One actually useful property of a PowerProfile is in determining if a load is dimmable or not.

Non-dimmable loads have a PowerProfile with Max == Min, and typical configurations will have a default PowerProfile called Relay which has PowerProfile.Max = 100 and PowerProfile.Min = 100.

We currently "guess" if a Load is dimmable, by checking if Load.LoadType ends with non-Dim. This is not bulletproof, since although these load types default to having the Relay power profile, a user could in theory select a Relay-like profile for any load.

Describe the solution you'd like

• We should expose PowerProfile objects via a new controller vantage.power_profiles
• We should remove the Load.is_dimmable property, which currently just guesses based on the load type
• We should instead add a PowerProfile.is_dimmable property, which returns True if PowerProfile.Max > PowerProfile.Min

Additional context

No response

Checklist

• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate of previous feature requests.

Generate Home Assistant events for Vantage Button presses

Linters and devcontainers

Hi, I just discovered your hass-vantage project when I noticed your PR for branding was approved in a few days while my PR for branding has been sitting a long time ;)

Anyway, I've been trying to use the gjbadros/hass-vantage component for a number of years, and it is only recently that the XML parsing was fixed (crashes with my project), so I got new interest.
I've spent the better part of the last week converting the project to something more modular and typed and GUI config, and then I discover you've done most already, thank you.

I am a sticker for linters, especially in non-typed languages, and I noticed some issues with your hass-vantage and aiovantage projects when using pylint and pycharm and black formatting (required by HA and HACS).

I also see you have not yet converted to a devcontainer for the component, which is something I've done, but my code is far from working.

I'd like to try your code out, I'd very much appreciate if you could 1) vscode/pylint/black/pycharm both your projects, there are some crashing bugs, and 2) add a devcontainer (I am happy to PR a devcontainer if you'd accept PR's)?

I can offer a very broken codebase but working devcontainer, github actions, requirements, linters, config's, etc., if you are interested in taking a look at my develop branch

Add sensible linting rules, add linting to GitHub Actions

Expose LightSensor and AnemoSensor as sensors in Home Assistant

LVRS8-DIN device not being reported

System Health details

System Information

version	core-2023.11.3
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.11.6
os_name	Linux
os_version	6.2.16-18-pve
arch	x86_64
timezone	America/Los_Angeles
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4942
Installed Version	1.33.0
Stage	running
Available Repositories	1411
Downloaded Repositories	8

Home Assistant Cloud

logged_in	true
subscription_expiration	January 31, 2024 at 4:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	false
remote_server	us-east-1-6.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Dashboards

dashboards	1
resources	2
views	21
mode	storage

Recorder

oldest_recorder_run	September 8, 2023 at 7:14 PM
current_recorder_run	November 29, 2023 at 9:26 PM
estimated_db_size	4123.86 MiB
database_engine	mysql
database_version	10.11.5

Checklist

• I have enabled debug logging for my installation
• I have filled out the issue template to the best of my ability
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue)
• This issue is not a duplicate of current issues

Describe the issue

I first noticed that none of the SDM12's were reporting any state, all current and power was 0.
Enabled debug logging from diagnostics page, and observed that periodic state reports reported all 0 values.
I observed that the recently added LVRS8-DIN module and associated loads were not listed in HA.
Restarted HA.

Observed that LVRS8-DIN low voltage relay station was not included in device report, but that the 8 switches were reported, and the parent was missing.

Parent 945 is missing:

<Object VID="947">
	<Load VID="947" Master="1" MTime="2023-11-15T05:47:40.079">
		<Name>Station Load 1</Name>
		<Model/>
		<Note/>
		<DName/>
		<ObjectTypeName>Load</ObjectTypeName>
		<Area>316</Area>
		<Location/>
		<Parent Position="1">945</Parent>
		<ContractorNumber>A6</ContractorNumber>
		<FixtureDefinition>0</FixtureDefinition>
		<LoadType>Low Voltage Relay</LoadType>
		<FixturePower>100</FixturePower>
		<FixtureQuantity>1</FixtureQuantity>
		<Power>0</Power>
		<PowerProfile>9</PowerProfile>
		<OverrideLevel>100</OverrideLevel>
		<DimmingConfig>Manual</DimmingConfig>
	</Load>
</Object>

May be unrelated, but I observed that the controller firmware was being reported as 0:

Some context:
I have been doing electrical panel maintenance over the past few weeks, and Vantage system has been off for a few minutes at a time.
I installed a low voltage relay stations, this is a DIN device, in order to add it to DC one has to add a DIN enclosure, then add the device to the enclosure.

P.s. for system health in issue template could use shortcut https://my.home-assistant.io/redirect/system_health/

Reproduction steps

1. Add LVRS8-DIN in DC
2. Look at HA and notice SDM12's are not reporting any values
3. Notice LVRS8-DIN is not reported.

Logs:
home-assistant.log

Debug logs

See debug log file, contents too big to fit here.

Diagnostics dump

home-assistant_vantage_2023-11-30T05-52-32.612Z.log

Error setting up entry Vantage InFusion for vantage - File "/config/custom_components/vantage/init.py", line 64

System Health details

System Information

version	core-2024.1.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.6
os_name	Linux
os_version	6.1.63-haos-raspi
arch	aarch64
timezone	America/Toronto
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4913
Installed Version	1.33.0
Stage	waiting
Available Repositories	1376
Downloaded Repositories	5
HACS Data	ok

Home Assistant Cloud

logged_in	true
subscription_expiration	February 12, 2024 at 7:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	true
remote_server	xxxxxxxx
certificate_status	ready
instance_id	xxxxxxx
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 11.4
update_channel	stable
supervisor_version	supervisor-2023.12.0
agent_version	1.6.0
docker_version	24.0.7
disk_total	57.3 GB
disk_used	6.0 GB
healthy	true
supported	true
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	Advanced SSH & Web Terminal (17.0.3), Mosquitto broker (6.4.0), File editor (5.7.0), Studio Code Server (5.15.0)

Dashboards

dashboards	3
resources	0
views	3
mode	yaml

Recorder

oldest_recorder_run	January 13, 2024 at 9:54 PM
current_recorder_run	January 13, 2024 at 8:49 PM
estimated_db_size	1.44 MiB
database_engine	sqlite
database_version	3.41.2

Checklist

• I have enabled debug logging for my installation
• I have filled out the issue template to the best of my ability
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue)
• This issue is not a duplicate of current issues

Describe the issue

After adding the IP in the Config Host, this is as far as it gets. It says "Failed Retry"

Reproduction steps

1. See above

...

Debug logs

Here is the debug log.

2024-01-13 20:45:51.527 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Vantage InFusion for vantage
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/vantage/__init__.py", line 64, in async_setup_entry
    await vantage.initialize()
  File "/usr/local/lib/python3.11/site-packages/aiovantage/__init__.py", line 272, in initialize
    await asyncio.gather(
  File "/usr/local/lib/python3.11/site-packages/aiovantage/controllers/base.py", line 160, in initialize
    await self.fetch_object_state(obj.id)
  File "/usr/local/lib/python3.11/site-packages/aiovantage/controllers/gmem.py", line 30, in fetch_object_state
    "value": await self.get_value(vid),
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiovantage/controllers/gmem.py", line 61, in get_value
    raw_value = response.args[1]
                ~~~~~~~~~~~~~^^^

Diagnostics dump

No response

Lights always power on at 100% but should power on at most recent load level

System Health details

System Information

version	core-2023.10.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.5
os_name	Linux
os_version	6.1.45
arch	x86_64
timezone	America/Los_Angeles
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	5000
Installed Version	1.33.0
Stage	running
Available Repositories	1382
Downloaded Repositories	1

Home Assistant Cloud

logged_in	true
subscription_expiration	June 10, 2024 at 5:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	true
remote_server	us-east-1-9.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 10.5
update_channel	stable
supervisor_version	supervisor-2023.10.1
agent_version	1.5.1
docker_version	23.0.6
disk_total	30.8 GB
disk_used	8.0 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Studio Code Server (5.13.0), Home Assistant Google Drive Backup (0.111.1), Advanced SSH & Web Terminal (15.1.0), Node-RED (14.4.0), Samba share (10.0.2), Mosquitto broker (6.2.1), WeatherFlow to MQTT (3.1.6)

Dashboards

dashboards	2
resources	0
views	1
mode	storage

Recorder

oldest_recorder_run	October 25, 2023 at 8:54 PM
current_recorder_run	October 26, 2023 at 3:31 PM
estimated_db_size	252.95 MiB
database_engine	sqlite
database_version	3.41.2

Checklist

• I have enabled debug logging for my installation
• I have filled out the issue template to the best of my ability
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue)
• This issue is not a duplicate of current issues

Describe the issue

Not sure if this is standard Home Assistant behavior or not but it is my view that when a dimmable light is powered on using the on/off power switch, it should power on at it's most recent load level. When this is done with a Philips Hue light, it is powered on at it's most recent load level. When lighting control is programmed in Vantage, the programmer usually specifies the load level. For interior loads, very seldom is it 100%. It just seems more user friendly to power it on at it's most recent level.

Reproduction steps

1. Go to the HA Dashboard UI and press the power toggle on a a dimmable load from Vantage.

...

Debug logs

I did not have the logger component active when I tested this.

Diagnostics dump

No response

Client does not reconnect after login failure

System Health details

System Information

version	core-2023.8.4
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.11.4
os_name	Linux
os_version	6.2.16-8-pve
arch	x86_64
timezone	America/Los_Angeles
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4971
Installed Version	1.32.1
Stage	running
Available Repositories	1336
Downloaded Repositories	3

Home Assistant Cloud

logged_in	true
subscription_expiration	January 31, 2024 at 4:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	false
google_enabled	false
remote_server	us-east-1-6.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Dashboards

dashboards	1
resources	0
views	20
mode	storage

Recorder

oldest_recorder_run	August 19, 2023 at 9:02 AM
current_recorder_run	August 25, 2023 at 2:03 AM
estimated_db_size	1010.11 MiB
database_engine	mysql
database_version	10.11.4

Checklist

• I have enabled debug logging for my installation
• I have filled out the issue template to the best of my ability
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue)
• This issue is not a duplicate of current issues

Describe the issue

Network client does not reconnect after a controller firmware update.
Log contains repeated aiovantage.errors.LoginRequiredError: "Requires Login" errors.

Reproduction steps

Update controller firmware:

1. Use DesignCenter v4.6 and update controller firmware from v4.5 to v4.6.
2. After controller update the password is reset to controller serial number.
3. Use DesignCenter and restore the password to the original value.
4. Observe that logs are full of aiovantage.errors.LoginRequiredError: "Requires Login" errors.

Reproduce as follows:

1. Use DC to change the password.
2. Drop the controller network connection.
3. Restore the controller network connection.
4. Use DC to restore the password.
5. Observe that logs are full of aiovantage.errors.LoginRequiredError: "Requires Login" errors.

Debug logs

2023-08-25 12:09:50.316 DEBUG (MainThread) [aiovantage.command_client.commands] Sending command: INVOKE 62 CurrentSensor.GetCurrentHW
2023-08-25 12:09:50.317 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.current_sensor_line_d_5 fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 699, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 938, in async_device_update
    await self.async_update()
  File "/config/custom_components/vantage/sensor.py", line 77, in async_update
    await self.client.omni_sensors.get_level(self.obj.id)
  File "/usr/local/lib/python3.11/site-packages/aiovantage/controllers/omni_sensors.py", line 61, in get_level
    response = await self.command_client.command("INVOKE", vid, method)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiovantage/command_client/commands.py", line 122, in command
    raw_response = await self.raw_request(request, connection=connection)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiovantage/command_client/commands.py", line 184, in raw_request
    raise self._parse_command_error(response_line)
aiovantage.errors.LoginRequiredError: "Requires Login"

Diagnostics dump

vantage.zip

Vantage IC-DIN-II Infusion Controller II init error

System Health details

System Information

version	core-2023.9.1
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.5
os_name	Linux
os_version	6.1.45
arch	x86_64
timezone	Europe/Rome
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4907
Installed Version	1.32.1
Stage	running
Available Repositories	1279
Downloaded Repositories	4

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 10.5
update_channel	stable
supervisor_version	supervisor-2023.08.3
agent_version	1.5.1
docker_version	23.0.6
disk_total	30.8 GB
disk_used	4.3 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Node-RED (14.4.5), Terminal & SSH (9.7.1), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.5.0), File editor (5.6.0)

Dashboards

dashboards	1
resources	0
views	4
mode	storage

Recorder

oldest_recorder_run	3 settembre 2023 alle ore 14:23
current_recorder_run	10 settembre 2023 alle ore 17:52
estimated_db_size	14.72 MiB
database_engine	sqlite
database_version	3.41.2

Sonoff

version	3.5.2 (2ad1cd7)
cloud_online	14 / 21
local_online	14 / 14

Checklist

• I have enabled debug logging for my installation
• I have filled out the issue template to the best of my ability
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue)
• This issue is not a duplicate of current issues

Describe the issue

Hi James, i'm trying your component with my Vantage IC-DIN-II
Infusion Controller II but i get this error? Have you any ideas?

Reproduction steps

1. Install component with Vantage IC-DIN-II firmware 3.9.1.11 and try to start

Debug logs

2023-09-10 17:12:53.153 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Vantage InFusion for vantage
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/vantage/__init__.py", line 57, in async_setup_entry
await vantage.initialize()
File "/usr/local/lib/python3.11/site-packages/aiovantage/__init__.py", line 268, in initialize
await asyncio.gather(
File "/usr/local/lib/python3.11/site-packages/aiovantage/controllers/base.py", line 139, in initialize
self._set_state(obj, await self.fetch_object_state(obj.id))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiovantage/controllers/temperature_sensors.py", line 27, in fetch_object_state
"value": await TemperatureInterface.get_value(self, vid),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiovantage/command_client/object_interfaces/temperature.py", line 22, in get_value
response = await self.invoke(vid, method)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiovantage/command_client/object_interfaces/base.py", line 34, in invoke
return await self.command_client.command("INVOKE", vid, method, *params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiovantage/command_client/commands.py", line 127, in command
raw_response = await self.raw_request(request, connection=connection)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiovantage/command_client/commands.py", line 189, in raw_request
raise self._parse_command_error(response_line)
aiovantage.errors.CommandError: "Not Implemented" (Error code 8)

Diagnostics dump

No response

[MDR8RW101] load type brought into HA as a Light but should be a Switch

System Health details

System Information

version	core-2023.10.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.5
os_name	Linux
os_version	6.1.45
arch	x86_64
timezone	America/Los_Angeles
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	5000
Installed Version	1.33.0
Stage	running
Available Repositories	1382
Downloaded Repositories	1

Home Assistant Cloud

logged_in	true
subscription_expiration	June 10, 2024 at 5:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	true
remote_server	us-east-1-9.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 10.5
update_channel	stable
supervisor_version	supervisor-2023.10.1
agent_version	1.5.1
docker_version	23.0.6
disk_total	30.8 GB
disk_used	8.0 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Studio Code Server (5.13.0), Home Assistant Google Drive Backup (0.111.1), Advanced SSH & Web Terminal (15.1.0), Node-RED (14.4.0), Samba share (10.0.2), Mosquitto broker (6.2.1), WeatherFlow to MQTT (3.1.6)

Dashboards

dashboards	2
resources	0
views	1
mode	storage

Recorder

oldest_recorder_run	October 25, 2023 at 8:54 PM
current_recorder_run	October 26, 2023 at 3:31 PM
estimated_db_size	252.95 MiB
database_engine	sqlite
database_version	3.41.2

Checklist

• I have enabled debug logging for my installation
• I have filled out the issue template to the best of my ability
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue)
• This issue is not a duplicate of current issues

Describe the issue

First, a big thank you for writing and sharing this integration! It works really well.

I am running an Infusion IC-24 Gen 1 controller with Design Center 3.9. I had several switched loads (relays) that were defined with a load type of [MDR8RW101] which must have been an option in an earlier version of Design Center because I can not figure out how set that load type in DC 3.9. The problem that I ran into was that the load was imported into HA as a light instead of a switch. The only reason I noticed this was because I also use the Homekit Bridge to bring my lights and switches into the Homekit ecosystem so that I can control them using Siri. I had a Ceiling Fan that had the load type set to [MDR8RW101] and when I asked Siri to turn the lights on, the ceiling fan went on. As a work around, I updated all of my loads that had load type set to [MDR8RW101] to High Voltage Relay. After reloading the Vantage program, I reloaded the custom component in HA and it obsolete the old version of the load and created a new load as a switch. Love that your component makes real time adjustments when the Vantage program changes.

I don't have an issue with this any more but just wanted to let you know, just in case you want to cover this edge case in your component.

mdr8rw101_issue.zip

Reproduction steps

1. Load the attached design center file on the vantage controller.
2. Add this integration to your HA instance.
3. Backyard Waterfall load in Backyard area will be brought into HA as a light. It is a relay load so should be brought in as a switch.
   ...

Debug logs

I didn't have the logger integration active when I did this.

Diagnostics dump

No response