Homey Community Forum

Measure_xxx_changed trigger not fired

Developers
#1

Hi,

The documentation states:

Custom capabilities starting with alarm_ , meter_ and measure_ will automatically try to trigger a Flow. You only need to define this Flow trigger in your /app.json .

Numbers

Calling setCapabilityValue('measure_my_number', 1) will try to start a Flow trigger with ID measure_my_number_changed , with a Tag value .

And so I though I had ‘easy’ ‘changed’ trigger flow cards. They show up and I can use them in my flow as expected. The only problem I have is that they do not fire. Can anyone take a look at what I am doing wrong here? The values are correctly updated, and the naming is what it should be, so what is going wrong?

Knmi (Dutch weather, for Homey firmware v5 or above)
#2

I think you missed that.

#3

If I missend them, how would I be able to use them in my flows?

#4

So if you add them to app.json they still don’t fire?

#5

Else I would not have created this topic.

#6

The app.json in the repository you’re linking to doesn’t contain them, else I wouldn’t have asked…

Apologies, I wasn’t looking properly :woozy_face:

#7

The one I was testing is on line 594.
It’s name is:
measure_current_temp_changed, it is a trigger flow as required.

The linked capability is on line 1150 and 1227 and named measure_current_temp. It is a number capability just like in the example.

For the trigger to work the trigger must have a tag/token with id value, that too is present, I don’t know what I am missing.

I can see the current temp property in the device being updated, but the notification that I should receive when it is changed does not come. Manually testing my test flow does result in a notification.

This app can be installed from this link so you can test the on change triggers for yourself. It’s already certified, but I won’t publish to live prior to there being some nice on change flow triggers that properly work. Perhaps I’ll even wait for Homey v5 to go live before publishing.

#8

I realize this is written for the unstable SDK v3, so perhaps this is still a bug?
Should I just keep my code as it currently is and wait for this to be fixed, or is the documentation incorrect and should I be doing something different?

#9

Are you making a KNMI app? Looks very promising if so

#10

Yes, the topic for this app is here.

It is already testable except for the fact that the triggers don’t get fired, except for the one trigger that is fired after manually requesting the latest data via the action card.

It’s already running for a couple of days now on my own Homey, without any other issues whatsoever.

#11

Nice, at this moment i retrieve these data with the http request app, which gives quite a lot off flows.

#12

The answer here took too long for me, removed the automatic triggers and done it with own code.

The automatic trigger only has one value, the new ones (my own custom triggers) now have the old and the new value. And my custom triggers do fire.