Closed mattreim closed 6 months ago
The CLIP sensors should definitely be exposed over the API. Whether they should be visible to users is up to the API client interacting with the user, ioBroker in your case?
Yes, the data is processed with the ioBroker. But the CLIP sensors are stored under sensors and therefore all external programs have this problem.
My external programs don't have this problem, as they explicitly offer the feature to interact with CLIP sensors. It's up to the user to configure the program which sensors should be visible. Phoscon as external program doesn't have this issue, as it explicitly filters out CLIP sensors. Exposing CLIP sensors this way is according to spec, and not a bug.
Ok thanks, then I'll probably have to live with it.
Just to understand: the API cannot access other folders such as secrets?
This looks like the database. It contains tables, not folders. And its structure is undocumented, and not exposed by the API. See https://dresden-elektronik.github.io/deconz-rest-doc/ for an overview of the API.
Closing as this is not a bug
Does the issue really belong here?
Is there already an existing issue for this?
Describe the bug
These CLIPSensors must be visible to the user? They are actually only intended for internal processing and not for external processing.
Or can you get your own folder? (e.g. FakeSensors;)
Steps to reproduce the behavior
Sensor list
Expected behavior
No FakeSensors to see
Screenshots
RESTED:
These have been added with version 2.26.1-beta.
ioBroker:
Environment
deCONZ Logs
No response
Additional context
No response