This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
That'll be fun recreating! Grr.
I'm trying to drag a token from my Aeotec Multisensor to set a number variable using the Better Logic number variable card. It appears it doesn't want to work, and will only let me drag it to the string variable card. Athom said this is an issue with the Better Logic app? Any ideas?
use the "set a variable" card, not the "set a number variable" card.
Read more people are having this problem, weird that it seems to be random...
it is probably because the tag is an object without any indication that it is a number?
I'd expect that to be broken all the time, not intermittently
Usure yet. Though in the inputs I configured them to be numeric. So I assumed if a tag contains a numeric value it would be a numeric type. This because the validation is done in homey code,not mine.
well when i was trying to create triggers (for dropdown) and used a number as the id (so without quotes), it still came true the "state" as a string and not as a number (with quotes), so i assume this is the same for tags.
maybe add a small debug as what is being send inside the tag, even when a number
Flow 1
Example value is set to 0.1 (rain mm) value shows in better logic correctly.
Flow 2 trigger of your choice
And column better logic card is set to: value is higher/lower/is exactly e.g. 0.1 after saving the flow shows 0. The flow triggers on any value that is in between 0.0 and 0.9
Does anybody have the same experience?
My interpretation of "Variable is set" was to trigger a flow even if variable had the same value before.
I have a boolean "tv" that turns socket on/off, which works OK on its own. But let's say I turn off socket directly with android app - now my remote won't turn on the socket as I expect. Variable is TRUE from before, and a new TRUE is sent - shouldn't the use of "Variable is set" commence this flow?
(Flows for ON is the same setup)
Turning off with remote first, then turning on again makes it work again. So it behaves like "variable has changed". What's the difference between "changed" and "set" if this is normal behavior?
As a workaround, I've adjusted all of these flows with number variables instead of boolean.
2 and 0 are triggers for ON/OFF, and second flow always ends with setting variable to 1 so that a future change is detected.
I think it's a stab in the back of the project and possible the end of it?!
Half empty
Uranday asked for help on Slack, no reaction.
That same evening he issued it o Git (while Emile was closing a bunch of issues) and also no reaction.
Don't think is half full and it's more almost empty....
This is one of the first user generated apps and deserves more attention that it is currently getting. Especially because it provides core functionality to some (if not most) users.
Oh @Uranday - go create a Donate button somewhere
Great initiative! Let's wait and see how this develops. Getting a @RamonBaas apps feeling.
Tomorrow I have some time scheduled to do some fixes. For now my todo's are:
- Check basic adding/deleting of variables
- Try to make a backup button, hope this is easy to do. Probably it will give you a long string and that string you can insert after a remove all variables. (cheaters can use it for mass adding of variables
- Check what is going on with the inputs when a token is dropped. I think this is something controlled by the firmware. If this is the case Ill add a generic card to support this
- Check equality comparators on decimal values
- Try to turn on isights
- Add donate button
Thanks for the effort @Uranday ;