[APP][PRO] Home Assistant - Community App

Another question… There is no option to use a scene as trigger. So, WHEN “scene x” has been triggerd, THAN…

Is this something you can fix? Or is this not possible… Please let me know if this is something I have to add to the wiki. :hugs:

I haven’t seen a scene trigger in the API. I think you cannonly set a scene. HA doesn’t send information back about a set scene because that’s a HA internal automation.

Edit: I checked in detail. There are only events for scripts started and automation triggered, but not for a set scene.

After the new update there is no way to change the device class of a switch. The feature is really handy if you use “all the light off” or an app like Vthermo with a switch.
The first picture is a switch I added yesterday and the second one is a device I just add. It’s both the same switch.

The picture is in dutch. To show the change.

Yes, you are right.
I changed the device type for a switch from “plug” to “button” to appear in the “right” area of the add device dialog, because as there are so many devices now it’s shown in device type rows:

grafik

As there is no “switch” device type in Homey I can only recert back to “socket” type.

Then it will look like this:

grafik

For me, that’s the best solution. This way you can say for yourself what is plugged into a switch and use ‘turn on all lights’ or for other purposes like Vthermo.

It will be a bit more area’s, but you can use a switch the way you want.

1 Like

It’s ok. I will change it back in the next version.

1 Like

New test version 0.4.1:

  • Changed device class for the switch back to “socket” to be able to change the device class.
  • Fix for correctly unregistering devices when deleting
1 Like

Thank you!!

1 Like

Example of adding air quality (purifier) data to Homey as compound device

@Wesley_Witjes @Marcel_Visser

I would like to show the way to define a compound device for airpurifier or air quality details in general.

Home Assistant has another way of device definition than Homey.
The elements, HA is working with, are the entities (switch, sensor, fan…). Each entity is the base component for the Homey device you can add directly.

For example, a climate device is defined in HA as entity with a defined set of attributes, modes and services. This entity is imported as device to Homey to offer a seamless control as it would be a Homey internal device.

The HA “devices” are just a set of (independent) entities. If you don’t use special Lovelace dashboard controls, you need to add each sensor or switch as entity to your Lovelace dashboard. There you can see that they are not directly dependent to the climate/fan device.

That’s my example of a Dyson fan/heater/purifier:


You can see the climate an fan entity that can be added as Homey device.
All other entities for air quality data are differnent sensors or switches. And there will be a lot of different versions for all the purifiers of different brands.
So there is no good possibility to add these sensors into a climate/fan device.
You can add every sensor as single device to Homey and place all devices into a “room”. That would be analogous to the Lovelace dashboard adding each entity as Lovelace element.

The better way is to combine these air quality data into a compound device.

  • Search all the sensors and switched by the device name in the HA entity list
  • If you need to know the data type (numeric/char), you can list the entities in the developer view.
  • Create a compound definition, use the best fitting Homey measure type (or the generic measure_numeric for numberns or measure_generic for text)
    All possible meassure capabilities can be found in the repository description (link below).
  • If you are using a capability more than once in the capabilities list, make sure you add a subcapability id using the format “capability.subcapability”.
dyson_air:
  name: Dyson Air quality
  capabilities:
    onoff.continuous: switch.pure_hot_cool_continuous_monitoring
    onoff.night: switch.pure_hot_cool_night_mode
    measure_humidity: sensor.pure_hot_cool_humidity
    measure_temperature: sensor.pure_hot_cool_temperature
    measure_numeric.no2: sensor.pure_hot_cool_nitrogen_dioxide
    measure_numeric.pm25: sensor.pure_hot_cool_pm_2_5
    measure_numeric.pm10: sensor.pure_hot_cool_pm_10
    measure_numeric.organic: sensor.pure_hot_cool_volatile_organic_compounds
    measure_numeric.filtercarb: sensor.pure_hot_cool_carbon_filter_life
    measure_numeric.filterhepa: sensor.pure_hot_cool_hepa_filter_life
  capabilitiesTitles:
    onoff.continuous: Continuous Monitoring
    onoff.night: Night Mode
    measure_humidity: Humidity
    measure_temperature: Temperature
    measure_numeric.no2: NO2
    measure_numeric.pm25: PM 2.5
    measure_numeric.pm10: PM 10
    measure_numeric.organic: Organics
    measure_numeric.filtercarb: Filter Carbon
    measure_numeric.filterhepa: Filter Hepa

Added to Homey it looks this way:
grafik
The first uses switch is used as quick action for the tile.
The sensors are shown in device details:

If your HA entity does not provide a unit, you can set it in the YAML definition:

  capabilitiesUnits:
    measure_numeric.no2: my unit

Don’t know how to install the custom component to HA?
Here is a description:

And here you can find the component:

You can install it as file of if you are using HACS, you can just add this repository as custom component.
A direct HACS import is in work…

3 Likes

Hi Marcel,
good news. I found a way to react on a activated script. The entity state (timestamp) changes on activation and that can be used as trigger.
So there will be a device trigger for scripts in the next version :slight_smile:

1 Like

Great!! Thanks for the explanation! :smiley: I’m running an custom compound already. I will follow your example for my purifier. :+1:t2:

Test version 0.4.2 is online

Added trigger for:

  • scene device trigger
  • script device trigger
  • script app trigger with script name filter
  • automation app trigger with automation name filter

Now all scenes/scripts/automations can be traced in Homey.

@Marcel_Visser You can test the trigger for scene device now :slight_smile:

4 Likes

If you have HACS already installed in your HomeAssistant system, you can add the Homey Compound integration directly to HACS (sorry, screenshot is only german):

grafik

Open HACS / Integrations, click on “Search and download repositories” and search for “homey”.

5 Likes

New live version 0.4.3:
You can send now notifications via HA using the three new flow action cards (on app level):

  1. This is a general version for sending simple text notifications to HA. HA will use the defautl notify service to process this message. As default this will result in a push message for the HA mobile app.
    grafik

  2. The second is similar but offers a service selection. You can send notification to other services (your TV, message provider…).
    grafik

  3. The 3th one offes an image token in addition. You can send a notification including a Homey image like it’s done with the Homey image push messages.
    grafik
    The image is passed as URL. You can select whether Homeys local or cloud URL should be used (dependent on your network topology)

This works with the HA notify domain (all services starting with “notify.”) and with other services named “.send_message” or “.send_photo” like the telegram bot.

6 Likes

New test version 0.5.0:

  • Added cover and lock device
    grafik grafik
10 Likes

Great progress again!!!

2 Likes

It just never stops! :smiling_face_with_three_hearts:

2 Likes

New test version 0.5.1:

There are some new flow action for lights for different light adjustments:

  • set light color with color picker (including hue, saturation, dim)
  • set light color by name
  • set light color by name and adjust dim value
  • set light temperature and dim value
  • set light hue, saturation and dim value

The first one is the easiest color selection.
The name selection offers the original color in one card and a combination with dim in the other card.
The last two cards are combining color selection and dim for light change with only one service call. This avoids a seperate dim and color step and enables you to create instant and smooth light transitions.

11 Likes

is there a possibility to “round” values to 2 decimals (AUSGABEN & EINNAHMEN)?

example:

> huaweipricing_compound:
>   name: Stromkosten
>   icon: measure_generic
>   capabilities:
>     **measure_numeric.consumption_cost: sensor.huawei_power_meter_consumption_cost**
>     measure_numeric.energy_price: sensor.energy_price
>     **measure_numeric.exported_compensation: sensor.huawei_power_meter_exported_compensation**
>     measure_numeric.energy_price_export: sensor.energy_price_export
>   capabilitiesTitles:
>     measure_numeric.consumption_cost: "Ausgaben"
>     measure_numeric.energy_price: "Tarif"
>     measure_numeric.exported_compensation: "Einnahmen"
>     measure_numeric.energy_price_export: "Rückliefertarif"
>   capabilitiesUnits:
>     measure_numeric.consumption_cost: "CHF"
>     measure_numeric.energy_price: "CHF/kWh"
>     measure_numeric.exported_compensation: "CHF"
>     measure_numeric.energy_price_export: "CHF/kWh"

I’m wanting to add power consumption to my lights so I can track these in Homey, so looked at creating a compound device for these.
The power works well, but how do I add Dimmer and colour functions?

light:
  name: Kitchen Light
  capabilities:
    onoff: light.kitchen_light
    dim: input_number.set_value
    meter_power: sensor.kitchen_light_power_2
    measure_power: sensor.kitchen_light_electric_consumption_kwh
  capabilitiesConverters:
    dim: 
      from: (state) => { return parseFloat(state) * 0.01; }
      to: (value) => { return value * 100; }