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
Consider the Reality
The naming of the shutter datapoints is quite confusing
Is your feature request related to a problem? Please describe.
This is not a problem but I have to keep a list where I noted what the different datapoints represents
Describe the solution you'd like
The datapoints need to be renamed so it is clearly to recognize what data each datapoint holds
The following datapoints are effected (X stands for corrosponding shutter number):
PositionX – acts like Shutter1_Target (holds target position after setpoint was changed) is it neccesary?
SHUTTERX - displays the new position after motor has stopped - Should have name: ShutterX_FinalPosition
ShutterX_Position - updates position every second when motor is active - Should have name: ShutterX_LivePosition
ShutterPositionX - set point for new position - Should have name: ShutterX_SetPoint
I hope the naming is done in the Adapter and is not predefined bei the Tasmota Device...
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Consider the Reality
The naming of the shutter datapoints is quite confusing
Is your feature request related to a problem? Please describe.
This is not a problem but I have to keep a list where I noted what the different datapoints represents
Describe the solution you'd like
The datapoints need to be renamed so it is clearly to recognize what data each datapoint holds
The following datapoints are effected (X stands for corrosponding shutter number):
I hope the naming is done in the Adapter and is not predefined bei the Tasmota Device...
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: