You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a virtual sensor channel with 2 inputs, and then emptying the second input value, the value is still visible in the web frontend - until the frontend is reloaded.
Steps to reproduce:
Create new channel of type "Verbrauchssensor (virt.)"
Fill values for "Eingang 1" and "Eingang 2" and save
Edit the channel and remove the value for "Eingang 2" and save
A PATCH request is sent, removing the value. The object data returned by the server do not contain "in2" anymore.
The edit window closes automatically
Click the channel's info button. "Eingang 2" is still shown and still has the value that was just deleted. <-- this is a bug
Click the edit button and remove the value again in the "Eingang 2" field. Save.
The PATCH request fails with status code 400: Object { message: "Entity has no property: 'in2'", type: "Exception", code: 0, … } <-- this is a bug
Reload the tab in the browser
Open the channel's info popup: The "Eingang 2" value is gone.
Somehow the web interface keeps the in2 field internally.
The text was updated successfully, but these errors were encountered:
When creating a virtual sensor channel with 2 inputs, and then emptying the second input value, the value is still visible in the web frontend - until the frontend is reloaded.
Steps to reproduce:
Object { message: "Entity has no property: 'in2'", type: "Exception", code: 0, … }
<-- this is a bugSomehow the web interface keeps the in2 field internally.
The text was updated successfully, but these errors were encountered: