I have published a new test version.
I just installed it and tested some changes. It looks like it holds the broker-settings!![]()
Hello Adrian.
This morning I noticed, again, as I mentioned once before that the status of one of the buttons on my panel had changed to an incorrect status. It hadn’t happened since that previous time.
So, out of curiosity I checked if there had been an update to the button+ app and lo & behold… 21 hours ago a new version was automatically installed. That is in the timeframe the change of button status has happened.
I’m not sure if this is intentional or not… but something tells me an update of the Homey app should not change the button status of my panel… or should it? It doesn’t feel right to me. But I’m easily persuaded to change my mind about it. ![]()
Anyway, I thought I should mention it. Take care, thanks!
What is the source of status?
None of the buttons are sourced. All is handled by flows. (And that worked for many weeks now.) Now I’ve sourced them (with the corresponding variable), I need to review all the flows (it’s not working anymore sadly…).
Maybe I’ll go back to un-sourcing them if it’s too much work…
and accept the change of states when there is an upgrade of the app.
I may have succeeded. The next few weeks will prove if I have. ![]()
I have a little complicated setup with 2 domotica hubs (Homeseer being the dominant one) and I’ve included the button+ panel in Homey. Which I used to replace a touch panel that was included in the Homeseer network. I did ask for trouble…
Using a variable as source means there is a direct relation to ‘on’ and ‘off’ state corresponding to ‘Yes’ and ‘No’ of the variable. Sometimes this is in reverse in my old set up (and depends on the name of the variable)… this gave me a lot of trouble as I have some buttons with that logic one way, some others with the other way. I guess this On-Yes and Off-No logic is a Button+ given…