Homey Community Forum

Switching from Domoticz to Homey

It depends on your model ofc, but Justin is busy releasing a proper app for roborock

1 Like

The native apps are not a PWA implementation, they were built separately and way before the current web app was available. The web app is newer and shares a lot of similarities, but has more options in some parts and (as it’s still in development) less on others. Athom seems to be heading towards a PWA with it though.

The web app is similar for normal use, has access to insights and homeyscript, the native app has not. The flow editor is better in web i.m.o., so is the device overview. However, the web app still lacks in settings, energy and at some points is a slightly bit less touch friendly (but remember - it is still in beta).

If you use the web app across devices, it will behave just fine on all of them, but it is not optimized for phone.

2 Likes

Thank you for your extensive reply! I will strip some parts and respond with some follow up questions here and there…

Great!

Nice! That way, I can trigger stuff from the car using the built in web browser and I don’t need to touch my phone

Good to know!

That’s what I meant with “type” it is not the sheer number of apps, it differs per app how much it affects the system.

That’s good to know! It does however raise another question that I haven’t asked yet. Perhaps this is also a Domoticz only issue…
For Domoticz I had written a script to switch on a light bulb if movement was detected. That went south quickly! It started switching on the light every few milliseconds the motion sensor was “on” (so movement was detected). Then I added to only switch on the light in case movement was detected AND the light was currently off. I am sure you can do stuff like that with Homey as well, but the thing was: I noticed the issue by examining the log. Can I examine the log like that as well in Homey?

The current interface is through Domoticz (the one I want to get rid of :slight_smile: )The P1 cable is split. One end goes into the Toon interface, the other end goes into the USB stick connected to the machine running Domoticz. I’m pretty sure the Homey Toon app will also be able to get these values. I’ll figure that out.

Yeah, I was planning on doing that. So basically: everything built on the Tuya platform is controlled by the Tuya app on the phone only and then I use the Homey Tuya app to create that bridge.
I don’t mind that some Chinese Tuya dude may be able to watch me switch on the lights. That paranoia is one of the reasons for me to move away from Domoticz. The community seems filled with “wappies”. But that is a different discussion…let’s steer away from that :wink:

There are sufficient options. That’s all I need to know for now.

Great to see, I will most likely just have to work with it!

Thanks, will look into it!

That’s good to know. All my current Z-Wave power plugs have power metering. That availability was implied :wink:

Just read somewhere that this is done basically the same way in Homey; by creating a virtual device that is either on or off indicating the scene being enabled or disabled.

Yes, in that case you start working with the device class. I can do that. And then in one script you can always loop through stuff. This is the level of programming that I like and can do.

Will look into that as well.

Yes, I’ve found those and I noticed: “The power changed” wasn’t sure if you can also check for a specific value.

Seems to be pretty much ok!

Thank you for all your replies! I think I got everything covered now.
Nice to have would be the central ventilation.

And of course there is the Zigbee limit I was not aware of :frowning:

1 Like

You’re welcome Rudi!

That should work.

Ah I see.
To be sure you can ask the community how much MB’ certain apps use @ their Homey.
But as you can see, many apps stay below 10MB’s.
Athom states in general an app uses around 15MB’s.
Some apps tend to grow and grow, for these you can easily restart them automatically via a flow, at a convenient time (which is not always while you try to sleep :wink: )

You can use zones for that. Or timers. Some aqara and tuya sensors “pause” for one minute after a motion detection.
To view what your flows are or aren’t doing, I add a Papertrails log card to every THEN and, if used, THEN ELSE action.
This can be done in one go luckily (in Dutch).
(There’s sadly no user viewable Homey log. Only Athom can view it when you send a “diagnostic report” at their request).
Also the phone app device timeline shows what / who switched a device, which I already mentioned.

Looks promising:

You could consider to connect your domotica Wifi to the guest network, or a dedicated vlan. If ‘they’ might want to check for interesting stuff on your network, it’s at least a lot more difficult :crazy_face:

If it has a 3 position switch, there are solutions available using a 2-gang or 3-gang relais.

Ah, yes, that isn’t shown. There’s mostly 1 (or more) variable/tag available you can use as a condition.
Like:
IF power has changed
AND power is below x (or equal to / above x)
THEN do x

Also new trigger cards are available. Like:
IF power is below x (or above x)
THEN do x

Difference:
-The first triggers every time as the power changed up or down, BUT only if it stays below x
-The latter only triggers once if the power drops below x.
It triggers again if power has been above x and then drops below x again.

Powermeasurement is only available for the first socket, in the past is was available for all sockets, maybe if you can find/use an old version of the app, it could be used.

1 Like

There’s 2 supported Tuya zigbee 3 and 4 socket powerstrips, but it also cannot switch individual sockets. No power measure option :see_no_evil:

That’s too bad. But still all six can be switched independently? Does that one socket then only measure the one socket or is it aggregated?

The flowcards only say “device turned on” and “device turned off”
So unfortunately no switching of individual sockets.

Kudos to you Peter for taking the time for such helpful replies to Rudi’s post

Rudi - if you get stuck implementing an integration on Homey you can always leave a minimal Domoticz install running and publish the info to MQTT and then read that into Homey, probably providing control back to Domoticz too. That way you can tread water until a suitable Homey integration appears.

1 Like

I’m running both Domoticz and Homey.
Using Homey for communication with Google Home and zwave.
For communication between Domoticz and Homey I use webhooks where needed.
Running this combo for several years now.

Yes,The Greenwave sockets can be switched on/off independendly, the power measurement is only done on the first socket.
Peter is talking about the Tuya powerstrips.

Nope, b/c Tuya doesn’t have power measurement as I mentioned.

I don’t own a Greenwave, but I posted the available flow cards already. There’s no separate socket 1, 2, 3, 4, 5 & 6 flow card. Just “device on/off”.
But maybe it’s not a realistic picture?
I believe you if it’s possible to switch all sockets individually😉
It’s just peculiar the app page keeps it hidden.

Every socket of the power brick will be their own “device” inside Homey, so I you’ll get 6 (maybe even 7 counting the zwave chip) different entities, which is why there is only on/off.

But indeed they removed the power reading from each separate socket, I believe there is only a aggregate one now, they removed reach power reading because of the amount of data causing issues for some users if they put the polling rate too low, and didn’t want to bother anymore.

I do have 2 of them, using them every day, so trust my comments.

1 Like

Oh I do trust your comments, Jan. That’s not it.
It was just strange to me the flow cards on the app page don’t show it’s capability to switch all 6 independently :hugs:

Ah! Got it & never thought of that. Thanks.

Welcome @Rudi_Hendrix , somehow I have the feeling I know you :grinning:
As I told you: “Stop messing around with Domoticz, You can’t live without a Homey”
WAF goes up and happy wife = happy life.