Can't disable protection on a setpoint

[Andrex]

I have a setpoint that has the "protected" switch enabled, if I turn it off and click on update, if I go back it's still enabled (and it still asks me the password to change the setpoint).
How can I disable the protection?
Thanks!

[waltervl]

What if you go to another domoticz page and go back to the setpoint page? It could be a caching/refresh issue.

[Andrex]

What if you go to another domoticz page and go back to the setpoint page? It could be a caching/refresh issue.

I've thought that too, so I've checked with another browser, but the setpoint is still protected.

[Kedi]

I checked it and it's a bug.
You can reverse directly in the database by settings the Options field of Table DeviceStatus to null (I did it, and it works)

[waltervl]

Please report it in a GitHub issue so it gets noticed...

[Andrex]

Please report it in a GitHub issue so it gets noticed...

Done!

[waltervl]

I just tested this on a setpoint device and cannot reproduce this on latest stable.
I can switch on/off protection without issues.

[Andrex]

I can switch on/off protection without issues.

I can do that too, but not on that single setpoint. I'm also thinking that the protection kinda activated by...itself.

[waltervl]

Something else special on this particular setpoint device?
It is managed by a specific hardware gateway?

[Andrex]

Something else special on this particular setpoint device?
It is managed by a specific hardware gateway?

Nope, it's exactly the same as the others. I just get the values from them from MQTT, there is no interaction.

[waltervl]

Perhaps remove it an recreate this setpoint like you did with the others.
If still an issue look what is different, other MQTT messages, strange characters in the name etc.

[Andrex]

Perhaps remove it an recreate this setpoint like you did with the others.
If still an issue look what is different, other MQTT messages, strange characters in the name etc.

That setpoint has been there for...years and has been created like the other ones.
By the way, believe it or not, this morning there is no password on that damned setpoint!