Test several things in a single scene?

Hello,
I gave in to an absolutely useless and therefore totally necessary gadget (Tuya Ivy Smart Planter, endloser Spaß über 49 reichhaltige Ausdrücke, 7 Smart-Sensoren, AI-Chips machen Pflanzen leicht und lustig anzuheben - AliExpress) which unfortunately my wife likes a lot and wants to have in several rooms.
Is it possible, without creating one scene per connected gadget, to create a single scene that could report the status (lack of water or sunlight, too much water or sunlight) for all the gadgets?
Thanks,
Jean

Hi @jean_bruder :slight_smile: That looks nice indeed

How are you currently retrieving the state?

That reminds me I also have a plant-watering issue aha

I searched a bit on Aliexpress, I found this ( WiFi Tuya Smart Bewässerung Maschine Automatische Micro-tropf Bewässerung System Pflanzen Controller System Bewässerung Werkzeug Alexa Google - AliExpress 44 ), unfortunately it’s not Zigbee but it could be useful to me, thanks for sharing :joy:

1 Like

Hi @pierre-gilles,
For the moment, it’s not yet connected to Gladys. I’m more trying to see how to do it before doing it, which saves me time :slight_smile:
In the end, the question asked here comes back to the one I had already asked regarding handling a group of lights, to which you replied that it’s not possible, that’s a shame :frowning:

Plenty of options — ideally the best approach would be to add support for this device to the Tuya Gladys integration, but that requires development skills :slight_smile:

Otherwise, it’s likely possible via Node-RED too!

And what about by type of MQTT message received in the scene?

Hello @lmilcent :slight_smile:
Can you expand on your idea? It might be able to address several of my requests (for example: a single scene that notifies about a low battery level on a set of sensors, specifying the sensor and the value)?
Thanks :slight_smile:
Jean

Sorry for the latency in my replies!

Actually it depends on your technical knowledge of Gladys and especially Zigbee2MQTT.
For a while now, Gladys has allowed triggering a scene via an MQTT message. Each Zigbee device sends messages with a topic (topic in English) to say who it is and what information it provides.

In scenes you can use this topic to then trigger an action. Handy if an object isn’t yet supported by Gladys in particular!

In my opinion you should:

  • Connect your device to Gladys and therefore to Zigbee2MQTT (the underlying component)
  • Connect to the Zigbee2MQTT interface (Gladys’s IP address on port 8080, for example http://192.168.1.2:8080)
  • The password is visible in the Gladys interface, in the Zigbee2MQTT service (in addition to the configuration file on disk)
  • Look at the different messages sent by your device and find the specific topic you’re interested in
  • Create a scene triggered based on that topic

I don’t have anything on hand yet to make you a more complete and tested guide, sorry!

Otherwise there may be an easier way, but again, I don’t have anything on hand to validate it.

Go to the Gladys integrations, then « MQTT » and finally the « Debug MQTT » menu. From there you’ll see all the topics (or « external ID » that start with « mqtt: ») received by your sensors.

Once you find the topic that interests you, you can create your scene.

@lmilcent it doesn’t really work because the MQTT broker used for the Zigbee2mqtt integration, when started automatically, is not the same as the MQTT broker of the MQTT integration (also when started automatically) ^^

Good evening @lmilcent,

Thanks for that suggestion. When you say « Create a scene triggered based on the topic in question », do you mean that one and the same scene can be triggered by several devices whose topic would trigger the execution? Because otherwise, @pierre-gilles has already helped me find a solution, and we both concluded that it would be necessary to create one scene per device, which in my case is tedious (just for the temperature sensors, there would therefore be at least 12 to create …).

My idea would have been to have a solution so that a single scene could « cycle » through all the devices of a « collection » to estimate their battery level, for example :slight_smile:

There you go, there you go …
Have a nice evening,
Jean,

Oh darn, that’s a shame. I don’t know what to do then :sweat_smile: