r/homey

Looking for similar functionality like Philips Hue Scenes for their bulbs without using Addons.

The current system is very poor and switching between moods via flows is too much to ask for multiple rooms or lightning setups.

Some experience to share:

For legacy reasons, I have a more complex automation setup than I'd prefer. The main automation hub is a Homey, using a Google Nest Wifi mesh backbone, Hue lights, an Aqara M3 and a few other bits and bobs.

I decided to consolidate a lot of devices on Matter a few months ago and gradually bought a load of IKEA devices (amongst a few from other brands). They all worked OK but I had been having Thread network issues for a while (lost packets, dropped devices etc), ranging from minor annoyance to the odd major collapse. At one point I thought I had narrowed it down to a faulty Grillplats (posted elsewhere), but was still having issues.

I eventually did narrow the ongoing issues down to the Grillplats (8 of), and did some experiments:

* With all 8 Grillplats, unstable and with loads of discarded packets

* Removed all the Grillplats, network stabilised completely

* Replaced 4 of the Grillplats with Onvis plugs (slightly higher on the budget ladder), network even more stable as they took over some routing.

* Added back just 1 Grillplats, the GrillPlats immediately started discarding huge numbers of packets and took out some local devices.

* Removed that Grillplats, repowered lost devices, network now healthy again, with low packet lost

My other IKEA devices are fine. I'm pretty sure the Grillplats were OK when I had a smaller Thread network. My theory is that Grillplats just can't cope with a network this busy, where the Onvis can. Other theories are most welcome, but maybe we need to avoid Grillplats on larger Thread networks.

Hey all,

I have a question about an architectural problem I'm facing.

TLDR: I cannot figure out how to prevent one automation from undoing the work that another automation just did. One automation can turn on a light because of X. Then, when X is still relevant, unrelated Y could tell another automation to turn that light off, not even knowing about X.

The main question is how you manage devices that should be controlled by multiple events.

For example. Let's say you're going to watch a movie during daytime. I could write an automation that checks for that, then tells the curtains to close if it's daytime. But there is already another automation that also checks if the sunlight is very bright today (and would heat up my house) so it will close or open the curtains based on weather information.

Hopefully you see where I'm going with this. I do not want my sun/heat blocking automation to open my curtains when I'm watching a movie during daytime. But adding a condition to the sun/heat blocking automation will inevitably make my automation more complex.

I want to keep these concerns separated, but also want to prevent automations with another goal to prevent actuating something that is in that state because another automation put it there and has more priority now. Basically when one automation has done something to an actuator, how can I prevent another automation from undoing that when it's fired a little later.
It's almost like I need a mutex on my actuator lol.

This is just a little example, but there are many situations where you'd have two or more automations controlling for example a single light.

I have not solved this and I'm not sure if Home assistant has the ability to solve this in a pretty way.

Things I've thought about

• Disabling automations with automations: Personally I think this is ugly because in the HA interface there is no way to know if the automation is disabled because I need to fix something still, or because it is temporarily disabled. Also, this introduces some state that requires recovering whenever HA is restarted for some reason. It would allow a higher priority automation to disable the lower prio one and re-enable when the situation changed. But how does one determine priority correctly? In the example mentioned before: If movie is turned on during daytime but it's heavily clouded. The curtains can stay open. Then I'd want the curtains to be closed later whenever the sun returns and I'd want the other automation to be enabled still.
• Creating helper binary sensors like "is_movie_on" or "is_it_sunny" that are composed of various inputs to condense it down to just a on/off. Then abstract those by creating another helper sensor that can take in all the different sensors and state of the to be actuated thing and then use that as a trigger for automations and let that decide which automation must be fired. This can work but may be a little complex in knowing which helper sensor is used for which automation eventually. I figure it can grow out of hand quite quickly

What do you guys think? Have you tackled this? Do you experience similar issues? Is there an alternative? Is your cat watching you reading this post?

Tuya has been a little on the fritz for me lately. I'm at a point where I'm restarting the app almost daily and sometimes twice or more a day. I've reinstalled the whole thing twice.

I'm not exactly stoked for the prospect of having to replace every tuya switch and socket in our house. Not just because of the cost, but also the effort as a lot of them are in the walls.

So my questions are:

Is anyone else suffering like this?

Does anyone have a more lasting solution than just constantly restarting the app?

Hello, moved over to Homey recently and am trying to automate some lights using a mmWave presence sensor, but I want to have a little bit of delay before turning the lights on when detecting motion. Essentially, I want to have a flow with "If motion is detected for 50ms, turn on light" since the sensor is pretty sensitive. I hope Athom realizes that some of us could use time values under a second at some point.

Currently I'm mitigating this by automating it in Home Assistant right now, but I've also seen HomeyScript. It would just be nice if we could use milliseconds in flows.

I've really had enough of sonoff and homey. Not sure who is at fault, but homey is not the best at telling you what's wrong or reconnect automatically. As disabled guy really not helpful bending down to reset them and funny sonoff said it's not there issue and one of there sellers. I said OK when it works and you reak the benefits. But when it's a fault you blame the reseller, I said only want on or off, they then said valid point. But still doesn't the fix issue. Any ideas as really not ideal got three of them. Thank you so much.

Bonjour, je suis en train de faire construire ma résidence principale, j’ai demandé à l’électricien de m’amener des cables RJ45 sur les façades et aux endroits où je souhaite des caméras.

Voici les équipements que j’ai prévu pour mon domicile en sachant que les caméras seront alimentées en POE via un switch POE+, j’aurais également deux caméras sur batterie que je mettrai dans la maison seulement quand on part en vacances.

Objectif à tout regrouper sur le même hub via le réseau et le wi-fi (une bonne wi-fi est prévu).

En sachant que l’ensemble remontera sur la box domotique Homey.

Voici les produits :

- Home hub pro
- 3x RLC820A
- 2x Argus Magicam
- Reolink Vidéo Doorbell POE

Dans l’attente de vos avis et retour.

Cordialement,

Dear Homey Community,

I will soon be getting a Homematic IP heating control system. From what I have read so far, integrating Homematic IP into Homey seems to be rather complicated.

Has anyone successfully connected Homematic IP to Homey? If so, how did you do it? Is there a clear and up-to-date guide available?

Thank you in advance for sharing your experience and support!

Best regards,
Stefan