-
-
Notifications
You must be signed in to change notification settings - Fork 31k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newly renamed Synology_DSM platform not setting up from YAML #34858
Comments
Hey there @ProtoThis, @Quentame, mind taking a look at this issue as its been labeled with a integration ( |
Hi ! Please look closely at breaking changes introduced in 0.109.0 and/or the documentation
Before 0.109.0: sensor:
- platform: synologydsm
... From 0.109.0: synology_dsm:
- ... This will fix your config. |
If you wanna help the development (mainly testing) of Synology DSM, you can register here : ProtoThis/python-synology#26 |
The breaking changes section does not mention the sensor domain at all, it only explicitly calls the renaming of the platform and the removal of Given the YAML excerpt provided is almost exactly the same as the previous sensor configuration, I feel some extra clarity in the breaking changes would be a good thing: configuration.yaml (new):
sensor.yaml (old):
|
Old was not as you described but as here #34858 (comment) I mentioned it on my refactor #32704, but I'm not making releases 😉 (we see there is not I personally split in an other way:
|
The problem
Renamed my
synologydsm
sensor tosynology_dsm
as noted in the release docs but the platform does not get set up.The following event is logged regarding setup of this sensor:
The synology_dsm platform for the sensor integration does not support platform setup. Please remove it from your config.
Environment
Problem-relevant
configuration.yaml
Sensor.yaml:
Traceback/Error logs
Additional information
Setting it up via the UI works, but not preferred. If the documented YAML setup is supposed to continue working this should be investigated, or if not, the documentation updated to reflect that UI configuration is the only way forward.
The text was updated successfully, but these errors were encountered: