Remove unsupported Protected argument from Domoticz device creation#1
Merged
Merged
Conversation
Copilot created this pull request from a session on behalf of
MadPatrick
May 31, 2026 13:16
View session
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plugin startup failed during device initialization because
Domoticz.Device(...)was called withProtected=1, which is not accepted in this Domoticz runtime (TypeError: 'protected' is an invalid keyword argument).Problem scope
API Payload,API Trigger), leaving the plugin in a broken initialization state.Code changes
plugin.pyplugin_core.pyProtected=1keyword from bothDomoticz.Device(...)calls while preserving all other device metadata (Name,Unit,Type*,DeviceID,Used).Behavior impact
Domoticz.Deviceparameters, allowing device creation to proceed on runtimes that rejectprotected/Protected.