This seems like working good.
Would it be possible to have trigger cards for when a specific number capability changed. Now there is only become greater / less than
There is also Value changed, but it doesn’t tell which value.
That trigger would be particularily useful for latitude/longitude changes to tigger GPS to address flows to update current address.
Also there is the Text changed, but now the question is which string capability, I have two in the configuration?
That is standard Homey logic.
Every numeric capability gets a higher/lower flow trigger generated.
But only main capabilities get default flow cards generated (value changed).
The app has two custom capabilities for generic values (measure_string, measure_number) wich such trigger cards. But also only for main capabilies. I think the trigger cards are coming up from these capabilities.
Ok, I’m using the measure_number for all numerics, since there is no standard capability for the number values I use. So yes, there are sub capabilities quite a few.
Hi! Thanks for the app!
Until now I’ve used it to create different MQTT devices. Mostly ESP32 stuff. And they are working. Now I decided to add a descoverable device. I "manually” published device properties to its topic. The device is discovered, but never gets update. In the MQTT Explorer looks like:
▼homie
▶deviceid
▼lightsensor
$homie = 3.0.1
$name = lightsensor
$nodes = light-sensor
$state = ready
▼light-sensor
$name = Ambient_Light_Sensor
$type = sensor
$properties = measure_luminance
▼measure_luminance = 12
$name = Luminance
$datatype = float
$unit = lx
$retained = true
$settable = false
In the Homey tools capability of the device is shown as:
{“measure_luminance”:{“stateTopic”:“homie/lightsensor/light-sensor”}}
But when I “manually" (with MQTT Explorer, for example) set the value for the homie/lightsensor/light-sensor/measure_luminance, in the device card it is not updated.
What am I doing wrong?
