@silfa718, switches aren’t exposed as ‘switch’ entity in HA via deCONZ, you need to listen for deconz_event events in order to use them. DrZzs recently published a good video describing the process. Have a look here starting at 14:30 (he’s doing it with Xiaomi switches, but the process is the same).
But no matter how many times I read that page I cannot figure out how I am supposed to use then or know what they are called or how the syntax looks when I write an automation in a text editor. It is like the documentation is incomplete
Hi
Thanks. I understand now. But that only works when you do automations via GUI.
Like most I have automations organised in many YAML files as automations quickly build up to several hundred and the GUI is very limited in what it can do.
You could say that the GUI could be a beginner friendly way to get started and then later move to YAML by copying the automations created from the automation.yaml to other files.
But for the device automations a Deconz remote automation looks like this (just created one for the learning)
This could all have been good if the implementers had not chosen to use the not very human friendly unique IDs like 595dd96cc68d455eadc14a9aa37a4a98
How is anyone ever going to be able to go back to such an automation in a YAML file and actually edit it or enhance it? I think the project goes the wrong way with this approach. I fully understand the idea but why did they choose not to use the human readable entity_id?
With current approach I would not recommend using the automation editor and the device triggers at all. Once you have just 50 automations and you want more advanced automations that the GUI does not support, you will hate yourself for that choice. It is better to learn to use the events which uses the friendly names for the devices. It would be nice if the events had the text aliases available in addition to the numbers.
If you’re down in the yaml files writing your automations you are not the main focus of device triggers.
Device and entity are two different things. The device triggers are to make it simple to expose functionality from devices. Devices can be such things as hue dimmer remotes which don’t hav entity_ids
But he will be very quickly because the GUI only supports the basic features and I find it sad that the yaml created by the GUI cannot be reused as the beginner advances his knowledge.
This is a thread about deconz so we should take any discussion elsewhere.
But in a deconz context, my personal opinion and my personal recommendation is that the device trigger feature is of limited use and can become an annoyance quickly as a new user wants to have more control of automations in yaml due to the way it is implemented. I would take the event route even though it is a little harder. But once you know how to listen to events it is not hard to do and it is well documented in the deconz integration doc
pff, tried now channel 15 , succeeded again with 1 xiaomi pir to use an ikea plug as router
1 succeeded, 3 other ones, just dont want to pair with it…
i was on the same place when i did the pairing process
i give up
They did them for a while here in Germnay. They were branded as Aldi Tint. They did e27, e14 and GU10. Either RGBW or colour temp. They also packaged some with a remote (support by deconz isn’t working yet but has been requested).
Unfortunately they seem to have stopped selling them now and they sold them all off cheap aa few months ago (I got an e14 colour temp for €5 and a GU10 colour with remote for €7).
They were actually made by a company called Müller Licht. Saturn and Media Markt here still sell them.
Who has xiaomi pir sensors, that are connected to a router and not conbee… Do looking for a cheap router (no bulb) and Ikea smart plug is a no-go either
It’s done. I moved my complete hue/osram/innr/Müller bulbs, switches and dimmer actors to deconz.
This morning I had to restart deConz before it was able to search for the last bulbs from the livingroom.
Last step: I connected Hue essentials to deconz. Works great.
Thanks to dresden-electronics for the great work
By the way: my alexa is now much leaner and with quicker response as I did not export all bulbs but only the groups and some special ones.
I never did anything specific, that just how deconz has connected it all together. The map does change a little from day to day though.
Other Aqara sensors I have have connected themselves to Osram bulbs, a CC2531 USB router and other IKEA sockets.
I also have a few devices that don;t even look like they are connected to the map but work fine
you must be lucky i think
according to other users, seems the xiaomi only want to pair with conbee itself
once they are paired, then never find another route
there must be a way though…