-
Notifications
You must be signed in to change notification settings - Fork 172
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
ON_OFF Cluster (CON-1178) #945
Comments
Are you using the namespaces?
|
Just needed to add the cluster namespace, thanks. Why would adding a custem cluster change the icon to a light? Is there a way to set the icon to something else? |
No, |
The end point is defined as on of light, without adding a custom on of cluster, the icon is different from when the custom cluster is added. Why would this be, since the endpoint did not change? |
What was the old icon and what new icon? Please attached some snapshots. What custom cluster you have added? |
On the right is a on_off_switch endpoint with no custom clusters configure, on the left is when a on_off cluster was added to the endpoint. How do I prevent it from changing? The endpoint and cluster was created as stated in the documents as specified in the first comment. Also visible in the image below. The uncommented part is to add the cluster, which then changes the icon to a light. |
@RoootNoodle This should not happen. We are looking into the issue. |
What app is that screen shot from? |
ESP-Rainmaker app |
@RoootNoodle could you please try out the latest iOS ESP Rainmaker app from Github or App Store with the above changes and see if it works? |
Unfortunately it still shows the same. Once the on off cluster is added the icon changes to a light icon as shown in previous comments. App version v3.3.2 |
I am trying to create a custom cluster as shown by the guide https://docs.espressif.com/projects/esp-matter/en/latest/esp32/developing.html#defining-your-own-data-model . But the on-off config_t is not recognize, am I missing an include or how can this be fixed?
The text was updated successfully, but these errors were encountered: