Is it possible to run multiple ISY-994i’s with Home Assistant? The Home Assistant documentation doesn’t indicate the possibility of more than one ISY.
The use case is two buildings each with its own ISY-994i controller and Home Assistant bridging between them.
Bump on this as this would be useful.
I wonder what would happen if you just tried to enter two?
# Example configuration.yaml entry
isy994:
- host: ISY_ADDRESS
username: ISY_USERNAME
password: ISY_PASSWORD
- host: ISY_ADDRESS
username: ISY_USERNAME
password: ISY_PASSWORD
You may get more traction in the other thread in this section:
Not that it would help with this, but if you haven’t tried the version in HACS it is better than the official integration.
I am running the HACS integration. And I didn’t even think of just trying to add two entries… let me try that and see 
[EDIT] Nope… doesn’t work.
Each building could have its own HA server and you could expose your devices over SSL
Yes however that’s a duplication of HASS instance requirements which is double the maintenance and double the issues on upgrades/updates.
In another system I’m running I can have multiple instances of the ISY driver loaded and all devices visible and usable for events and in the UI. Seems it should be possible with HASS as well but probably not a typical use case which is why it’s not available. I’ve found this limitation with all of the other systems I’ve tried with ISY as well so it’s not a surprise.
Well the external building wouldn’t have much installed other than isy: And it’s not double the work. If you expose the entities you could leave the external HA alone.
In case you missed it:
@TimWing, @simplextech: When you have a chance, I have a beta version for you to test which (should) support multiple ISYs. In HACS, please install the v0.1.11-beta1 version; config changes are available in the changelog and README for that branch–short version is just use a list and repeat the config for each controller.
You may have to show beta versions if you don’t already have them enabled, use the menu in HACS to show them:
Hello shbatm, Thank you for this revision. I have tries this a couple ways but have run into some trouble.
I installed the beta…
I changed my configuration.yaml to have two “isy994” configs.
# Universal Devices ISY994 (House)
isy994:
host: http://192.168.0.3:80
username: !secret isy_house_username
password: !secret isy_house_password
# Universal Devices ISY994 (Shop)
isy994:
host: http://192.168.0.2:80
username: !secret isy_shop_username
password: !secret isy_shop_password
but this results in VSC error…
File ‘configuration.yaml’ could not be parsed, it was referenced from path ‘configuration.yaml’.This file will be ignored. Error(s): - YAMLSemanticError: Map keys must be unique; “isy994” is repeated (Line: 2)
and hassio errors…
2020-02-22 12:08:16 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/configuration.yaml contains duplicate key "isy994". Check lines 30 and 36.
2020-02-22 12:08:16 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for isy994 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-02-22 12:08:16 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-02-22 12:08:16 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for nexia which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-02-22 12:08:16 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-02-22 12:08:22 WARNING (MainThread) [custom_components.isy994] Bad ISY Request: http://192.168.0.2:80/rest/vars/definitions/1 404: retry #0
2020-02-22 12:08:23 WARNING (MainThread) [custom_components.isy994] Bad ISY Request: http://192.168.0.2:80/rest/vars/definitions/1 404: retry #1
2020-02-22 12:08:24 WARNING (MainThread) [custom_components.isy994] Bad ISY Request: http://192.168.0.2:80/rest/vars/definitions/1 404: retry #2
2020-02-22 12:08:26 WARNING (MainThread) [custom_components.isy994] Bad ISY Request: http://192.168.0.2:80/rest/vars/definitions/1 404: retry #3
2020-02-22 12:08:27 WARNING (MainThread) [custom_components.isy994] Bad ISY Request: http://192.168.0.2:80/rest/vars/definitions/1 404: retry #4
2020-02-22 12:08:28 WARNING (MainThread) [custom_components.isy994] Bad ISY Request: http://192.168.0.2:80/rest/vars/definitions/1 404: retry #5
2020-02-22 12:08:29 ERROR (MainThread) [custom_components.isy994] Bad ISY Request: http://192.168.0.2:80/rest/vars/definitions/1 404: Failed after 5 retries
2020-02-22 12:08:29 ERROR (MainThread) [custom_components.isy994] ISY Could not parse response, poorly formatted XML.: Variables
2020-02-22 12:08:30 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for kodi_recently_added which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2020-02-22 12:08:32 WARNING (MainThread) [homeassistant.setup] Setup of isy994 is taking over 10 seconds.
2020-02-22 12:08:33 ERROR (SyncWorker_5) [homeassistant.components.cisco_ios.device_tracker] pxssh failed on login
2020-02-22 12:08:33 ERROR (SyncWorker_5) [homeassistant.components.cisco_ios.device_tracker] Could not establish connection to host
2020-02-22 12:08:33 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform legacy
2020-02-22 12:08:34 ERROR (SyncWorker_19) [homeassistant.components.cisco_ios.device_tracker] pxssh failed on login
2020-02-22 12:08:34 ERROR (SyncWorker_19) [homeassistant.components.cisco_ios.device_tracker] Could not establish connection to host
2020-02-22 12:08:34 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform legacy
2020-02-22 12:08:43 ERROR (stream_worker) [libav.tcp] Connection to tcp://192.168.0.230:554?timeout=5000000 failed: Host is unreachable
2020-02-22 12:08:46 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform alexa_media is taking over 10 seconds.
2020-02-22 12:08:46 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform alexa_media is taking over 10 seconds.
So I tried only one isy994 config…
# Universal Devices ISY994 (House)
isy994:
host: http://192.168.0.3:80
username: !secret isy_house_username
password: !secret isy_house_password
# Universal Devices ISY994 (Shop)
host: http://192.168.0.2:80
username: !secret isy_shop_username
password: !secret isy_shop_password
but getting VSC error…
File ‘configuration.yaml’ could not be parsed, it was referenced from path ‘configuration.yaml’.This file will be ignored. Error(s): - YAMLSemanticError: Map keys must be unique; “host” is repeated (Line: 32) - YAMLSemanticError: Map keys must be unique; “username” is repeated (Line: 32) - YAMLSemanticError: Map keys must be unique; “password” is repeated (Line: 32)
with the same hassio errors…
Am I doing something wrong?
@TimWing it needs to be a list if you use multiple hosts.
# Universal Devices ISY994 (House)
isy994:
- host: http://192.168.0.3:80
username: !secret isy_house_username
password: !secret isy_house_password
# Universal Devices ISY994 (Shop)
- host: http://192.168.0.2:80
username: !secret isy_shop_username
password: !secret isy_shop_password
@shbatm That works! I will continue to fiddle and let you know if anything comes up. Thanks for your help!
I know this discussion is for the HACS version and I am using the Core Integration of UD ISY and there is nothing in the configuration.yaml file for isy994.
So where is the information kept?
I have not found a way to change the IP Address, Login or Password.
I want to migrate a room at a time from my ISY994 to ISY/Polisy so I will need to be able to have both working at the same time.
Do I need to disable/delete the current instance and then put the needed information in the configuration.yaml file?
Multiple ISYs are supported by the integration when setup from the UI. There is no YAML config needed any more, just add a second instance from the Integrations page.
When migration things from one instance to another, you can use the Reload Universal Devices ISY994 button on the Server Controls page or use the isy994.reload service, but since you are moving the same devices over, it may be better to restart HA to try and avoid duplicated entity_ids.