# \[APP\]\[Pro\] Home Assistant - Community App **URL:** \ **Category:** Apps\ **Tags:** app, tools, homey-pro, home-assistant\ **Created:** [October 31, 2022, 8:25pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477 "2022-10-31T20:25:26Z")\ **Posts on this page:** 20\ **Page:** 60
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [November 2, 2024, 7:57am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1194 "2024-11-02T07:57:47Z")
New **test version 1.7.3** : - Just some small improvements for dynamic mode list. ---
**Author:** ![GRat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/grat/32/17928_2.png) [@GRat](https://community.homey.app/u/GRat)\ **Post date:** [November 13, 2024, 6:03am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1195 "2024-11-13T06:03:46Z")
Hi, wanted some advice on the best way to setup (if possible ) my Solar panels? The current Solar panels app in Homey is broken (seems like an API update issue) but works fully in Home Assistant. I’ve added it as a compound device but just shows as a device consuming power, rather than generating. So not showing on the outside of the Homey energy ring ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [November 13, 2024, 3:04pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1196 "2024-11-13T15:04:05Z")
Hi, 1st: You should think about removing the compound devices and replace it with custom devices. About energy in general: Homey only uses measure\_power capability for the EnergyDashboard. That means, a device can only have one power capability. All others can only be added as subcapability (like measure\_power.sub1) and aren’t used for EnergyDashboard. So let’s start 🙂 I also use the Fronius HA integration. There is also a Homey app, but importing HA data into custom devices is a lot more flexible. You will see why… I thought about all energy values I want to have… - solar production - grid usage - grid feed-in - house usage - battery charging - battery discharging So I added all as a custom device with custom icon. Then I added the corresponding HA entity in rerpair view as measure\_power capability. ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/b/9b24fa19e9975d77c9eb3a96e39a10850ef4c2eb.png) Now you can change the device settings. Select “solarpanel” as device class for your solar production device. ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/4/944ca4ce4ad503f06f69dfda5b9f3bac1922f9d3.png) Set house usage and grid usage as “cumulative” power usage. ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/8/78e132db894403240a45a6acd7eae7c29c56a629.png) Feed-in is also set as “cumulative” but also as “include in total”. This way it’s counted as power usage and substracted from production. ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/6/a61b43a8bf8c5440b0c9f6f7551f22e4661ff7de.png) Battery is a special one. The HA integration has a sensor which has positive value for battery discharging (usage) and negative for charging. I want to see battery charging as “usage” power in Homey because it should be substracted from production. Battery discharging “returns” this energy. It works like a solarpanel. So I defined this device also as “solarpanel” device class. Both devices should only get “their” battery power part (negative/posisitve). I use the converter for: Battery charging: Positive values are cleared (set to 0), negative values are used as negative (\*1 to convert HA string state into numeric Homey value). Solar panels have to report negative values (see developer docs for details). ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/2/a2009c7376ed9ea8187c5807e9f4f99c37d46d5a.png) Battery discharging: same, but for positive range: ![grafik](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/8/c82740d3bce61a086c00520025c3315fe282434e.png) Good luck. To try the result, I used the mobile app for EnergyDashboarb while changing the devices in WebApp. ---
**Author:** ![GRat](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/grat/32/17928_2.png) [@GRat](https://community.homey.app/u/GRat)\ **Post date:** [November 13, 2024, 3:07pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1197 "2024-11-13T15:07:59Z")
Oh Wow, brilliant. Thanks very much, I’ll work through and let you know how it goes. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [November 24, 2024, 11:16am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1198 "2024-11-24T11:16:35Z")
New **test version 1.8.0** : - Added new capabilities for “add entity” view - Changed entity state import logic to import string values into enum capabilities. ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [November 25, 2024, 10:13am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1199 "2024-11-25T10:13:37Z")
Hi Ronny, diag. id 9e0ce4e0-3076-4775-a0b5-8cfb93ed6cea I had to go back to stable version, because existing flows stop working as some states are not populated anymore. Not sure it’s intended or not… Example : measure\_generic.select.water\_heater\_mode is N/A after update ![capab](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/d/8de74f8c6424a9f4b6f3fc72207436cf6f6da48b.png) _Didn’t check more now, just was wondering why some existing flows stop working…_ ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [November 25, 2024, 10:27am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1200 "2024-11-25T10:27:29Z")
You are right. It seems the wrong flow parameter is filled now. Thanks for reporting. I had to change the type check for capabilities to support enum capabilities (modes). So exchanged one issue with another 😅 I made some further changes yesterday to read capability type from the capability. I will check the flows before publishing a new test version. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [November 25, 2024, 10:43am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1201 "2024-11-25T10:43:08Z")
New **test version 1.8.1** : - Changed capability type check. The type of target capability (updates from HA) is now read from capability definition instead of using capability id. @Sharkys FYI and to test (if you dare 😄). ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [November 25, 2024, 11:29am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1202 "2024-11-25T11:29:17Z")
Thanks for the speedy fix! So far, 1.8.1 works perfectly. 🥂 ---
**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\ **Post date:** [December 13, 2024, 4:31pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1203 "2024-12-13T16:31:58Z")
Hello @RonnyW , I have included a power meter (custom), with device class “sensor” , capabilities “measure\_power” and “meter\_power”. In the new energy-tab from Homey, this meter does not get recognized correctly. The Energy tab states that the power meter only have real-time measurement, that is not true. I have tried to add a new device with only one Entitie with capabilitie “meter\_power”, then it showed up, but never updated values. “meter\_power.imported” with the same Entitie did not get recognized. Do you have any clue what is going on? Attached screenshots: Developer tool- ![bilde](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/5/15e6c4656540bb342fdbb102643afc1c34004b9e.png) Device settings- ![1000003538](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/3/535f24f86f1d89b42102536e95d2d6bb07f0e932.jpeg) Energy-tab Homey app: ![1000003537](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/3/f3dfce56bcc2ea9782fa61f92812793fe18c8d99.jpeg) ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [December 13, 2024, 5:11pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1204 "2024-12-13T17:11:19Z")
It looks good. I’m not sure what’s wrong. What message is shown after adding the device? And main capabilities measure\_power and meter\_power should be right. Did you wait a time? I also recognized that changes need some time to show up in HomeyEnergy. ---
**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\ **Post date:** [December 13, 2024, 5:20pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1205 "2024-12-13T17:20:59Z")
What message are you thinking about? I already had the device included with Main capability “measure\_power” and “meter\_power”. With my experimental tries I waited at least one hour, because the kWh is only updated at the whole hour. I have sent you the details from the device in a private message. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [December 13, 2024, 6:37pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1206 "2024-12-13T18:37:35Z")
> [@Marius\_Stensrod](#): > > What message are you thinking about? I meant this: > What message are you thinking about? But it won’t show more then you wrote. So not relevant I think. ---
**Author:** ![Marius\_Stensrod](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marius_stensrod/32/56540_2.png) [@Marius\_Stensrod](https://community.homey.app/u/Marius_Stensrod)\ **Post date:** [December 13, 2024, 6:42pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1207 "2024-12-13T18:42:46Z")
It has to be a bug at Athom. I have given up to report issues as I am considered “just a user”, can you report it? If you consider it as a bug, like I do. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [December 13, 2024, 11:59pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1208 "2024-12-13T23:59:35Z")
Hope it’s OK to post here: ### Show gauges colored or grayed out, depending on sensor value With these very nice gauges (HACS store integration link [here](https://github.com/custom-cards/canvas-gauge-card)), I wanted gauges without (relevant) information to turn grey-ish, instead of hiding them completely. With the new “Sections” dashboard view-type, it’s very easy to hide elements on certain condition(s). > ![1000000148](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/5/55d7d33a32f645045cc13752cbc3101d64c0777e.jpeg) Now, from one of these 2 gauges: > ![1000000140](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/0/50ccfb64211af6913456089591dd1cbdaa1e2bf9.jpeg) I just duplicated the original gauge, changed the colors to grey-ish, and added it to the section. In edit mode, you’ll see “everything”, all 3 gauges, and the “Zon Output” gauge twice, in different colors: > ![1000000138](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/a/1a0ee5ae2e8110b69c3329c7da6d8ebc06273cba.jpeg) Now, whith the settings saved, and the dashboard back in ‘live’ view: When the value of that sensor is below 1, it shows the grey gauge instead of the colored gauge: > ![1000000136](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/9/7960cae7469fa98048a2e6e15a80de902922adc3.jpeg) To make both gauges switch, just add a “`visibility`” entry, along with these different conditions, (next to `condition` and `entity`): `above: 1` for the colored gauge; `below: 1` for the grey gauge; > ![1000000144](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/7/175fe6ce0fc82e49e25dd8c12f6c018caa9dc0c9.jpeg) Code for both gauges: > **colored gauge** > > ```auto > type: custom:canvas-gauge-card > entity: sensor.solar_total_output > name: null > card_height: 165 > shadow_height: 0% > font_size: 0.95em > font_color: "#000" > shadow_bottom: 10 > gauge: > type: radial-gauge > units: Watt > title: Zon output > width: 185 > height: 185 > borderShadowWidth: 3 > borderOuterWidth: 1.2 > borderMiddleWidth: 1 > borderInnerWidth: 0.2 > minValue: 0 > maxValue: 7000 > startAngle: 45 > ticksAngle: 270 > valueBox: true > majorTicks: > - "0" > - "750" > - "1500" > - "2250" > - "3000" > - "3750" > - "4250" > - "5000" > - "5750" > - "6500" > - "7000" > minorTicks: 3 > strokeTicks: true > highlights: > - from: 0 > to: 1500 > color: darkorange > - from: 1500 > to: 3750 > color: yellow > - from: 3750 > to: 7000 > color: lightgreen > colorPlate: "#00001f" > colorTitle: "#eee" > colorUnits: "#eee" > colorNumbers: "#eee" > colorMajorTicks: "#300000" > colorMinorTicks: "#00001f" > borders: false > needleType: arrow > needleStart: 30 > needleEnd: 85 > needleWidth: 4 > needleCircleSize: 12 > needleCircleOuter: true > needleCircleInner: true > colorBorderOuter: "#fff000" > colorBorderOuterEnd: "#111" > colorBorderMiddle: "#222" > colorBorderMiddleEnd: "#111" > colorBorderInner: "#111" > colorBorderInnerEnd: "#333" > colorNeedleShadowDown: "#333" > colorNeedleCircleOuter: "#333" > colorNeedleCircleOuterEnd: "#111" > colorNeedleCircleInner: "#111" > colorNeedleCircleInnerEnd: "#222" > valueBoxBorderRadius: 0 > colorValueBoxRect: "#222" > colorValueBoxRectEnd: "#333" > animationDuration: 1500 > animationRule: linear > grid_options: > columns: 6 > rows: auto > visibility: > - condition: numeric_state > entity: sensor.solar_total_output > above: 1 > > ``` > **grey gauge** > > ```auto > type: custom:canvas-gauge-card > entity: sensor.solar_total_output > name: null > card_height: 165 > shadow_height: 0% > font_size: 0.95em > font_color: "#000" > shadow_bottom: 10 > gauge: > type: radial-gauge > units: Watt > title: Zon output > width: 185 > height: 185 > borderShadowWidth: 3 > borderOuterWidth: 0.3 > borderMiddleWidth: 1 > borderInnerWidth: 2.76 > minValue: 0 > maxValue: 7000 > startAngle: 45 > ticksAngle: 270 > valueBox: true > majorTicks: > - "0" > - "750" > - "1500" > - "2250" > - "3000" > - "3750" > - "4250" > - "5000" > - "5750" > - "6500" > - "7000" > minorTicks: 3 > strokeTicks: true > highlights: > - from: 0 > to: 1500 > color: darkgray > - from: 1500 > to: 3750 > color: darkgray > - from: 3750 > to: 7000 > color: darkgray > colorPlate: "#00001f" > colorTitle: "#eee" > colorUnits: "#eee" > colorNumbers: "#eee" > colorMajorTicks: "#300000" > colorMinorTicks: "#00001f" > borders: false > needleType: arrow > needleStart: 30 > needleEnd: 85 > needleWidth: 4 > needleCircleSize: 12 > needleCircleOuter: true > needleCircleInner: true > colorBorderOuter: "#fff000" > colorBorderOuterEnd: "#111" > colorBorderMiddle: "#222" > colorBorderMiddleEnd: "#111" > colorBorderInner: "#111" > colorBorderInnerEnd: "#333" > colorNeedleShadowDown: "#333" > colorNeedleCircleOuter: "#333" > colorNeedleCircleOuterEnd: "#111" > colorNeedleCircleInner: "#111" > colorNeedleCircleInnerEnd: "#222" > valueBoxBorderRadius: 0 > colorValueBoxRect: "#222" > colorValueBoxRectEnd: "#333" > animationDuration: 1500 > animationRule: linear > grid_options: > columns: 6 > rows: auto > visibility: > - condition: numeric_state > entity: sensor.solar_total_output > below: 1 > > ``` ---
**Author:** ![daniel3](https://avatars.discourse-cdn.com/v4/letter/d/a4c791/32.png) [@daniel3](https://community.homey.app/u/daniel3)\ **Post date:** [December 16, 2024, 1:16am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1209 "2024-12-16T01:16:25Z")
Since some time I’m using the Hue Bridge via HA in Homey. This way I am using flows to control both my Hue lights and my Dimmer Switches. The lights are added as lights using this app and the Dimmer Switches are controlled using the following flow cards: ![Screenshot 2024-12-15 164711](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/9/89f206de59f7052ceea7923523ec3415441876b8.png) This all works as expected, but since I some other non Philips Hue Zigbee devices I have a second Zigbee network that is controlled via Homey. This is not a desirable solution for me, so I have decided to set up a new Zigbee network via MQTT, where all devices will be included. MQTT is hosted on HA, so I still want to use this app to show my devices in Homey. As a test I already transferred some lights and some dimmer switches to my new network. The lights work great, but I have a small issue with my Dimmer Switches. They only seem to work when using the “The state of entity has changed” card. Any other card, including the event card shown above as shown in the screenshot, or cards dedicated to the device (which I added as a sensor) do nothing. This is the case even though I see a change in the action entity in HA. Is using “the state entity has changed” the only option to use a Dimmer Switch using MQTT via HA or could it be that I’m missing something? ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [December 17, 2024, 6:27am UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1210 "2024-12-17T06:27:36Z")
Some technical details: A light has a persistent state (on/off, dim level) that is stored in entity state and attributes. A dim switch has no persistent state. It has only buttons and if one is pressed, the an event is thrown. The Hue bridge (for example) reacts on these events and changes the assigned lights(s). This way you have a light device with capabilities (the states) and you can react on events from the remote with event flow trigger. Mqtt has only persistent states. They are stores in topics. If a light changes, the topic changes its value. This is represented in a HA entity state and that is represented in a Homey device capability. For the remote it depents on the Zigbee/Mqtt integration how such events are handled. If you can see them as a HA entity state, the I think if you press one of the buttons, the topis value is changed (on/off). If that’s the case, you should have a HA entity with an on/off state (like a light). So you get a Homey device with the corresponding capability (onoff capability should be best to use). ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [December 19, 2024, 8:58pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1211 "2024-12-19T20:58:43Z")
New **test version(s) 1.8.2 and 1.8.3**: - HomeyEnergy: Set energy options in devcice settings Set meter\_power parameter for importing/exporting capability while adding/changing entities in custom devices. ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [December 20, 2024, 4:16pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1212 "2024-12-20T16:16:23Z")
Here is a short manual how to add a HA smartmeter to Homey: > **[HomeAssistant: Verwende deinen SmartMeter in HomeyEnergy – Ronny Winkler](https://rwdevelopment.de/2024/12/20/homeassistant-verwende-deinen-smartmeter-in-homeyenergy/)** ---
**Author:** ![Jan\_Peeters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan_peeters/32/86660_2.png) [@Jan\_Peeters](https://community.homey.app/u/Jan_Peeters)\ **Post date:** [December 22, 2024, 4:23pm UTC](https://community.homey.app/t/app-pro-home-assistant-community-app/71477/1213 "2024-12-22T16:23:36Z")
> [@RonnyW](#): > > Here is a short manual how to add a HA smartmeter to Homey: Hi Ronny, thank you for this manual. So much information packed on just one single page! Would you be willig to make a similar manual on how to add entities (smart plugs) to the energy tab? I am a bit lost there… I have some 80+ power meters in HA / zigbee but most of them are not shown in the energy tab. I have checked the capabilities and they all have the measure\_power and meter\_power capabilities and they are not set to cumulative. However, most of them have been added as switches. Is it possible only ‘customer devices’ / ‘sensors’ are shown? [Previous page](https://community.homey.app/t/app-pro-home-assistant-community-app/71477.md?page=59) [Next page](https://community.homey.app/t/app-pro-home-assistant-community-app/71477.md?page=61)