Thank you very much for the update. I didn’t expect this to appear so fast.
Are you sure that adding out all THEN commands is a good idea?
I understand that you want to keep the compatibility, but this makes already complex setup even more overwhelemed with.
There are a lot of outdated things, that is very questionable to be there. I personally believe that just - Label, Top Label, SVG, LED Color, and On/Off states should be there.
The bugs:
Using the new Device independent parameters form 1.0.10 with advanced flows:
The Left Button on Configuration 1 on Page 1 - Single click, (just this button on this page and this config) does not report state properly. It reports always “On”. Also on the button LCD display it adds “+” or “-” to the text that is already there, and these ± change upon clicks. UPD: looks like the internal logic for this specific button treats Single Click as Double click and this causes it to behave such way. On Device Capabilities everything is set to None and “Flow Trigger Only” I double checked.
Using device Capabilities (No Advanced flows) I tried to make a configuration for my Air Conditioner. Left/Rights buttons are used - one for temp up and other to temp down
The result - Despite I set Step value to “-1” designated button do increase the temperature insted of decreesing it.
Using device Capabilities (No Advanced flows). For some reason, the Label Text or SVG preset for the button is overiden with Device Capabilities output. Instead of getting temperature logos, like below. I am getting the Target temperature value. (which is rises with both buttons, and can go all the way from 0 to 100)
P.S. Adrian, I beg you - start another App Thread and remove all the outdated features, otherwise the bugs will spread all over the leftovers, people will come and ask to fix them creating more bugs like a snow ball, especially if you are involving AI in the coding. All these Click Release Events, Delays, counters are cool options but they are not essential. Button+ is an awesome device, but UX is horrible, I cannot setup a single button for two months just because it is too advanced.
For the bug: I sent you the Log report. I can also send you the config if you replay me in the email. I think I found the source from where it is coming from and looks like to replicate you will need TWO+ Button+ devices.
The Config is pulling the capabilities from the other Button+ for some reason. I can only see the trace of it in the App’s interface. I switch from STD to AVD mode and enter Advanced configuration.
This is what see, I didn’t SET these settings myself and All Flows are disabled throughout. When I clean out these, set everything to None, save the config. Button behavior don’t change it is still worked incorrect. It showed me either 28%+ or 28%- on the click.
I tried to figure out what is 28% and it turned out that it is Brightness of my Second Button+ Device.
Looks like the config just slipped one line. Adding the settings of Page Back to the Left Button on the Connector 2.
To conclude:
If the very same Row Configurations is used across multiple Buttons, settings do not apply properly. I am pretty sure that it was working fine before you added a Wizard, because App not behaving that way before. As my fist Button is on the wall for quite a while and the Second one is on the table. Their config is differs only in the third row of buttons.
I can then load that onto my devices in simulator mode and see what is happening.
I have removed the app level cards you mentioned (as they were extras added for you request).
I think I have also found the issues you have reported, but I need the configuration to test it.
Sorry, I missed this config export button, just sent you the Export.
I really appreciate what you are doing, the thing that you did create is the most complex and advanced app in the entire Homey Store. And very sorry about arguing on the interface to be too advanced at some points. The main thing I am struggling with is HUE Bridge integration which references non-Device relationship for executing the Scenes, so they cannot be executed via Button+ App interface and I forced to go with advanced flows.
I was thinking on what may caused such behavior, and giving you more clue.
Before the bug happened. I found potentially useful flow card Information (info).
I decided to use it as kind of Global Variable to output color Scene Names or last Action of the button, As it it only assignable to the in the Display Configuration, I did set it the for one of the files as “Target Button+” and (info).
I still cannot do this with just with ADV buttons, because I am controlling the Group of HUE lights that are not a Device, it is a Flow Card.
To use just Buttons, without flows I have a option to make a Virtual device in “Device Capabilities App” route all this logic, but not quite sure that this is the good variant.
As I am using quite different logic for Dimming reverse than yours, which is based on Double Click.
I am using scripts so each button have three diffrent functions, Single click for on/off, Double Click - for 85% brightness, and Long Press for dim up dim down, which is calculated via separate script and depends on the current brightness level.
By the way, I think that artificial delay on Click event (to decouple it from Long Press), as you did this before may come cause the conflict when somebody will set up the Long Press delay to 0 (from 500ms) via button configuration. Thus I am voting on Long Press Release.
I am Using Left Button for rising and Right Button For lowering the temperature.
Left is set to “Click Step Value” to +1, Right is set for “Click Step Value” to -1
Both buttons simultaneously go in the same direction and then switch to the oposite, despite Double Click and Long Press are set to “None”
Looks like the “Reverse direction” logic is involved here, which applies to the Capability instead of button.
Wizrad is cool but in my setput it applies the unnecessary LED glow. And this Glow, cannot be turned off. It somehow goes behind the LED configuration and overrides it. So I cannot turn it off.
Further more in my setup I tried to apply LED capability to track if my AC is On or off. IT doens’t work.
You can debug this usigin the configs I gave you earlier, I didn’t change anything and observe such behavior
You will need to set the LEDs to black if you want them to switch off.
Also, check the configuration as the one you sent to me has the right button long press incrementing the temperature by 2. Also make sure the double click event is set to Flow only (or at least not set to toggel)
As for now, everything that I mentioned looks stable.
I will take a closer look at the others functions tomorrow. I am always trying to pull the most from the config and also consulting with AI to create most user friendly UI experince, this is how 2 increment appreared.
P.S. as for now, as a spent hours with your app, I am aware of most of the functions and what logic you enclosured during the years of Button+ App existent, I am completely adore what you done and I will keep chalanging the app till perfection, and we are pretty close
I will send you the current config, take a look at Page 3, Row 2 (Configuration 2). These are the buttons, that you fixed last time - Temperature Up and Down with SVG. When I physically press the button, the preset SVG changes to the temperature value for a second and than switches back to SVG.
This is very cool thing, and I actually like it a lot, but looks like it is there there not by intend, as this behavior was not configured anywhere. I think that it also comes from the bug caused LED lights to be uncontrollable after running a Wizard.
I was thinking if it is possible to achieve such behavior using a flow cards, showing the value for a sec and than falling back to the state that was set in the App’s Configuration.
Like adding the option “Flow Trigger Only” here. So it will react on the the state change and than fallback to what is preset in the configuration panel. This may also work the LED controls.
In case there is no text or SVG applied for the Configuration, leaving the the value that came from the dedicated flow card or capability on screen.
