unfoldedcircle / feature-and-bug-tracker

Feature and bug tracker repository for Unfolded Circle products
22 stars 0 forks source link

Web Configurator Hard Buttons Not Saving #229

Open AryasDad opened 6 months ago

AryasDad commented 6 months ago

Is there an existing issue for this?

Description

When I go to an Activity and change the command associated with a hard button, it does not get saved to the remote. I have tried resetting the button and re-adding a command instead of just changing it and the same thing happens.

In order to force a save I have to remove a soft button and recreate it, then any changes to hard buttons get saved. This is confirmed by the little pop-up message saying changes have been saved.

Note, the pop-up doesn't occur when editing the hard buttons.

How to Reproduce

  1. Go to Web Configurator
  2. Go to Activities & macros
  3. Click on existing Activity
  4. Click on Edit user interface
  5. Edit command for hard button
  6. Nothing gets saved to remote

Expected behavior

Every change to a hard button gets saved just like any edit to the soft buttons.

System version

v1.5.2

What part of the system affected by the problem?

Web Configurator

Additional context

No response

zehnm commented 6 months ago

@AryasDad I assume you are referring to the following button configuration, correct?

image

Are there any red error popups at the bottom when assigning a command to the button? A successful command assignment to a button will not show a confirmation popup.

Another thing to check for are "dangling entities" in the activities. These are included entities which were removed, but are still referenced in the activity. They have a 🚫 icon on the main activity page:

image

If there's such an entity, the activity cannot be edited and an error popup should appear.

AryasDad commented 6 months ago

Sorry for the delayed response. Just found the notification of your reply in my inbox.

Yes, I am referring to that button configuration. I get no errors (i.e. red alerts) when I change a command. The change does no propagate to the remote.

I haven't checked recently if it still occurs, but it happened to me a few times when tweaking my remote setup. I would change a command associated with a physical button and the remote would not use the new command. I only got the changes to propagate when I did some edited of the screen buttons, as well. I.e. adding or removing image/text buttons to the screen layout.