Might be possible by downloading the source code;
then change the app id, @ line 2, in .homeycompose/app.json
into, like,
"io.home-assistant.community-2"
and then install it by CLI (search the forum ifor “how to cli”) as your second HAC app.
Then connect it with your 2nd HA instance
Currently not. The app holds the credentials and the connection and all devices are passes through this connection.
It’s mainly because the app “old” already had this settings before I took over.
Is it possible to install the app twice?
Only from CLI with a modified app.json (another app id) like Peter showed.
Thanks this works!!
Btw… modify the /.homecompose.app.json and not the /app.json. The second one is generated from homeycompose.
Hi! Since a couple of days ago my homey23 reports that the homeassistant app crashed when i looked at it today and did a mouse over the crashed sign it said “CPU limit reached”
Is it something wonkey with my homeassistant that is making this or it the homey?
Did a diag a0c2feaa-1653-4038-851a-51a15c94502e
A CPU limit crash is caused by a massive amount of entity update messages.
A common reason is a device (representing an HA entity) that is synced back to HA. This can cause an entity update that is synced back to Homey again.
You have the MQTT Hub app running, right?
Please check the MQTT Hub settings and deactivate all devices created with HA Community app.
Then restart the Hub and check if both apps keep running.
@RonnyW Found that i had some loops!
But even after removal of this loops and also disabling of all mqtt it keeps crashing even after a full reboot. I also tried to remove all the devices added in homey but even without them the app keeps crashing.
Is it my homeassistant that is spamming the homey plugin and how can i find out what device is doing that?
Entities and attributes.
Hello,
I need help with the below, I think it should work but I so can’t get it done on my own. The whole setup here is to integrate everything via HomeAssistant and not use the Homey Zigbee, which I no longer want to use.
An entity is now integrated via Zigbee from my HomeAssistant. The entity itself is available via the Homey Assistant community app in Homey. So far, so good.
Now this entity in Home Assistant also has attributes. See image below. Unfortunately, these attributes are not available in Homey. When I connect the entity directly to Homey via Zigbee, these attributes are available. An indication that they should therefore indeed also be available in Homey via Home assistant.
Who can explain to me in plain language IF and HOW I make the attributes below available in Homey? My eternal thanks will be yours!
The HomeAssistant Entity:
The attributes via HA developer tools
(Specifically interested in “load_power” and “voltage”):
The Entities as available in Homey today :
The entities as they are available in Homey via the Homey integration (Power and Energy):
It sounds as if something is creating a lot of entity changes or events in HA.
If the app keeps alive for a time , you can log all entity updates and check if there is an entity that’s causing this traffic.
Go ot repair view of any device (you will need at least one). Then activate extended logging:
Go back and refresh. Then there should be some entity updates or events.
Don’t forget to deactivate the extended logging.
If you can’t get into repair view in case the app crashes too fast, the please check the HA logs in developer tools:
If you want to lof entity changed, just listen to “state_changed” events:
I hope that helps.
Edit: You can also check the statistics in device repair function to get an overview about the amout of messages:
The 30sec amount can be a good indicator:
Im so gratefull @RonnyW
Big thank you for your support and also this lovely app!
I found the culprit it was the unifi integration in homeassistant that was connected to my UDM pro it was spamming the homeassistant with temperatur informations that then lead to the problem against homey app.
So now everything is working without any crashes!
@RonnyW , any idea why changing thermostat mode do not change anything (THEN action card) ? Am I setting it wrong ? (I must manage it via flows as it’s Water heater / not standard thermostat)
You have to use the device internal mode Select mode.
This way you get the modes from your device as an autocomplete list.
This card sends a service call to HA:
Service: water_heater.set_operation_mode
Parameter: operation_mode: mode
Hm, I don’t see this option for thermostat type of HAC device … or did I get you wrong ?
This will not work as this is not standard thermostat device.
Just to explain my use case - I can change the thermostat modes in the HA, that’s not a problem but I would like to get it reflected also by the Thermostat device from HAC in Homey using trigger I have…
I think you are mixing two HA domains.
Your flow card shows a water heater icon. So it seems you added your entity as water heater.
Can you please check if your HA “device” is using different entities/domains?
Where is the mode defined (I think water heater entity).
Where is the thermostat defined (climate domain?)
Can you please show the details of your entity/entities?
Another question: Did you add additional entities/attributes to your water hearer device (Thermostat mode)?
Maybe we don’t understand each other or maybe it’s getting too complex for me 
Let’s simplify, just to prevent possible misunderstanding - when I run :
The Homey device stays in this mode after running this action (…so it’s relaying on the real update from HA ?) :
That Homey device is climate.water_heater_thermostat and in HA I see following particular entity IDs
It’s under select.water_heater_mode (it’s ESP32 integration…)
Apologies Ronny, this is what you mean ? 
{
"climate.water_heater_thermostat": {
"entity_id": "climate.water_heater_thermostat",
"state": "off",
"attributes": {
"hvac_modes": [
"off",
"heat"
],
"min_temp": 40,
"max_temp": 80,
"target_temp_step": 1,
"current_temperature": 65,
"temperature": 65,
"hvac_action": "idle",
"friendly_name": "Water heater thermostat",
"supported_features": 385
},
"context": {
"id": "01HXXXSX9E6XSVWNSEATXYRZG5",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T01:47:44.952Z",
"last_updated": "2024-05-15T10:47:09.358Z"
},
"sensor.water_heater_temp1": {
"entity_id": "sensor.water_heater_temp1",
"state": "63.1",
"attributes": {
"unit_of_measurement": "°C",
"icon": "mdi:thermometer",
"friendly_name": "Water heater temp1"
},
"context": {
"id": "01HXXYDR0KEX2EYNYBJACS8ETC",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T10:57:59.315Z",
"last_updated": "2024-05-15T10:57:59.315Z",
"homey_capability": "measure_temperature.sensor.water_heater_temp1"
},
"sensor.water_heater_temp2": {
"entity_id": "sensor.water_heater_temp2",
"state": "65.1",
"attributes": {
"unit_of_measurement": "°C",
"icon": "mdi:thermometer",
"friendly_name": "Water heater temp2"
},
"context": {
"id": "01HXXXSX9D7YAFAG1ZMMAX0B7C",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T10:47:09.357Z",
"last_updated": "2024-05-15T10:47:09.357Z",
"homey_capability": "measure_temperature.sensor.water_heater_temp2"
},
"sensor.water_heater_energy": {
"entity_id": "sensor.water_heater_energy",
"state": "8555.669",
"attributes": {
"state_class": "total_increasing",
"unit_of_measurement": "kWh",
"device_class": "energy",
"icon": "mdi:flash",
"friendly_name": "Water heater energy"
},
"context": {
"id": "01HXXY6BNWB8Q4BKZ74VRSH2N3",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T10:53:57.308Z",
"last_updated": "2024-05-15T10:53:57.308Z",
"homey_capability": "meter_power.sensor.water_heater_energy"
},
"sensor.water_heater_state": {
"entity_id": "sensor.water_heater_state",
"state": "Connected",
"attributes": {
"friendly_name": "Water heater state"
},
"context": {
"id": "01HXWYY79W8JGTNDCTCR56QQGY",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T01:47:44.828Z",
"last_updated": "2024-05-15T01:47:44.828Z",
"homey_capability": "measure_generic.sensor.water_heater_state"
},
"sensor.water_heater_version": {
"entity_id": "sensor.water_heater_version",
"state": "fw:1.78, board: 431, S/N: 35813",
"attributes": {
"friendly_name": "Water heater version"
},
"context": {
"id": "01HXWYY7A7VNK66ZBVQGTB5HYS",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T01:47:44.839Z",
"last_updated": "2024-05-15T01:47:44.839Z",
"homey_capability": "measure_generic.sensor.water_heater_version"
},
"sensor.water_heater_name": {
"entity_id": "sensor.water_heater_name",
"state": "SmartBoiler\u0000\u0000\u0000\u0000\u0000",
"attributes": {
"friendly_name": "Water heater name"
},
"context": {
"id": "01HXWYY79XFVC90GA0QZV476SN",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T01:47:44.829Z",
"last_updated": "2024-05-15T01:47:44.829Z",
"homey_capability": "measure_generic.sensor.water_heater_name"
},
"binary_sensor.water_heater_hdo": {
"entity_id": "binary_sensor.water_heater_hdo",
"state": "off",
"attributes": {
"friendly_name": "Water heater HDO"
},
"context": {
"id": "01HXWYY7TCWR7PJQCW2Z9MQKDK",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T01:47:45.356Z",
"last_updated": "2024-05-15T01:47:45.356Z",
"homey_capability": "alarm_generic.binary_sensor.water_heater_hdo"
},
"binary_sensor.water_heater_heat": {
"entity_id": "binary_sensor.water_heater_heat",
"state": "off",
"attributes": {
"friendly_name": "Water heater heat"
},
"context": {
"id": "01HXXXSW932QYEAQ4K5JZ1GT0F",
"parent_id": null,
"user_id": null
},
"last_changed": "2024-05-15T10:47:08.323Z",
"last_updated": "2024-05-15T10:47:08.323Z",
"homey_capability": "alarm_generic.binary_sensor.water_heater_heat"
}
}
