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
After creating a sensor, you can open the sensor creation panel again and add a new sensor without any obstacles. That is, all the required fields for adding a sensor are present
What is the actual behavior?
When selecting a specific sensor type, configuration fields appear in the form. If these fields are filled and a sensor of this type is created, the sensor is successfully saved. However, when reopening the sensor creation modal, all configuration fields disappear. The fields reappear only if the sensor type is switched to another type and then switched back.
Relevant log output
Relevant logs...
What did you try?
nothing for now
What is your environment?
I'm running the code with...
How can we reproduce the bug?
Open the sensor creation modal.
Select a specific sensor type (e.g., "GPIB" or "Tinkerforge").
Fill in the configuration fields and create a sensor.
Reopen the sensor creation modal.
Observe that the configuration fields are missing.
Switch to a different sensor type and then switch back to the original type.
Notice that the configuration fields reappear.
The text was updated successfully, but these errors were encountered:
What is the expected behavior?
After creating a sensor, you can open the sensor creation panel again and add a new sensor without any obstacles. That is, all the required fields for adding a sensor are present
What is the actual behavior?
When selecting a specific sensor type, configuration fields appear in the form. If these fields are filled and a sensor of this type is created, the sensor is successfully saved. However, when reopening the sensor creation modal, all configuration fields disappear. The fields reappear only if the sensor type is switched to another type and then switched back.
Relevant log output
What did you try?
nothing for now
What is your environment?
I'm running the code with...
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: