Hi, can you please check again writing a timeline entry? Just to be sure it’s not the pushmessage causing duplicated messages.
Double entries in the timeline too (the two middle ones are coming from another flow that also uses the alarm capability flow card):
Thanks, will check it later.
1 Like
I tried with a custom device, imported a boolean capability into alarm_generic:
Works as expected for me.
I changed the state at HA entity. Then the flow is triggerred once.
Are you also using boolean states? Or a switch? Can you please give me some details about the entity you are using and how it’s imported (custom device, sensor device, capability used in device)? Thanks.
Not sure why, but the duplicate messages stopped today. I didn’t change anything, so I don’t really understand what caused it. But I’m glad it works as expected again.
Thanks for checking!
I saw this in the past when the connection was initialized twice or if HA sends the messages twice.
Then it can happen that two identical messages are received that are processed asynchronous in parallel.
I thought this should not happen. But perhaps there was a connection issue (HA restart or something else) that results in a connection lost at Homey side (that reconnects) resulting a duplicated event handler at HA side.
HomeAssistant and its entities compared to Homey and its capabilities and how they work are not easy to understand. But you need to know some basics to manage your (custom) devices and import entities in a good way.
That’s why I created a blog post with some details. I hope this clears up some questions.
If you have any suggestions or if there are any questions, please let me know.
It is a somewhat late reply, but I tried what you said. The State of Entity change card didn’t work for me because all it returned was the date and time. Your second option did work though :D. I created an custom device where I added both the Event Type and the Button, which both are attributes from the entity event.Bureau_dimmer_switch_action.
After I added the entities in the repair view could create an flow that I could create the following flow:
One thing to notice for other people who walk into the same problem: Whenever you restart Zigbee2MQTT the event type cleared and after a short moment pushed again to Home Assistant. Because of that Homey thinks that the entity has changed and triggers the flow. You can bypass this by letting it check that the Old Value is not blank. That way reboots of Zigbee2MQTT are bypassed in the flow and you don’t have flows starting ‘out of random’.
All my dimmer switches are working again as do the lights and motion sensors! This is exactly what I wanted before I started the migration from the Hue Bridge to Zigbee2MQTT.
Now for something mostly unrelated. I also added my Robot Vacuum to Homey via HA and MQTT. The device works as expected but there is an ‘dimming option’ within the device that I think isn’t supported with my device. It should change the speed but when I change it nothing happens. There is also the speed selection option and that works as expected. If I look in either HA or Valetudo (the software I use for my Robot Vacuum) I don’t see a speed slider anywhere else. Only the options from the select list. Is there a way to remove the speed slider from the pre-made devices?
Thanks again for all the help!
The vacuum domain has a service “set_fan_speed” that can take a enum value (mode list) or a percentage value (0…100). That’s why the app adds both options.
The entity should support both, but many devices only support one of them. But you can’t see what is working or not. The device has only a feature “fan_speed”, but doesn’t tell you if it supports mode and/or percentage.
That explains a lot. And is there a way to remove the percentage value from Homey so I can keep it tidy?
Currently not.
1 Like
New test version 1.10.0:
- Added dynamic mode lists for media device (source/sound mode)
1 Like
I think I found a strange little bug. When I press a button on a remote, I also show the time the button is pressed in Homey. This is done via the Event action capability. The strange thing is that the time is an hour off even though the correct time is shown in Home Assistant.
This is the time in Home Assistant that the button was pressed.
This is the time in Homey that the same button is pressed. I already converted it using:
(value) => { return new Date(value).toLocaleString('nl-NL', {hour12s: false, hour: '2-digit', minute: '2-digit', second: '2-digit', day: '2-digit', month: '2-digit', year: 'numeric' }); }
I have checked both the settings in Home Assistant and in Homey to check if they use the correct time, which is the case. It seems like the UTC time is displayed rather than the time of the timezone.
Can you please check the entity state in HA developer tools if it’s UTC or not?
Hi Ronny, firstly thank you for the great app. I have a smart water pump from DAB, which sadly doesn’t have an app in Homey, so I am using the Community App to import data it into Homey. Now with the new Homey Energy tab, I would like to use this data for my water consumption. Is there a way to assign a water meter attribute to this device so Homey recognises it as a water meter?
Do you mean this? That one is in UTC.
It’s easy 
I think you already have a device where you want to add a meter sensor? If not, just create a “custom device”.
Go to repair view, select “add entity”.
Then select your water meter sensor.
Select “meter_water” capability (clear the field and select from list).
Now add entity.
Then go to device settings and select “cumulative” flag.
1 Like
Genius, it works! Thank you so much!
1 Like
Got it. You need the timezone in addition. The locale nl-NL converts to NL visualization. Time zone added the +1h.
Example:
(value) => {
return new Date(value).toLocaleString(
'de-DE',
{
timeZone: 'Europe/Berlin',
hour12s: false,
hour: '2-digit',
minute: '2-digit',
day: '2-digit',
month: '2-digit',
year: 'numeric'
});
}
