You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have several switches attached to scene channels on zwave things but configured with no semantic class and they show fine on the model screen when checking the "show non-semantic" checkbox but have noticed that if I add state description metadata to translate the scene numbers to something more friendly, the item disappears from the model screen entirely unless I give it semantic metadata like "point". If I remove the metadata, it comes back as well under "show non-semantic". Verified this with several items as well.
Edit: I just noticed the same behavior with expire metadata on non-semantic items, so I suspect it's really ANY metadata that triggers this behavior. Unfortunately, that makes writing rules through the UI difficult as those items with metadata can't be picked from the view for triggers and anywhere else where the model picker is used.
The text was updated successfully, but these errors were encountered:
I have several switches attached to scene channels on zwave things but configured with no semantic class and they show fine on the model screen when checking the "show non-semantic" checkbox but have noticed that if I add state description metadata to translate the scene numbers to something more friendly, the item disappears from the model screen entirely unless I give it semantic metadata like "point". If I remove the metadata, it comes back as well under "show non-semantic". Verified this with several items as well.
Edit: I just noticed the same behavior with expire metadata on non-semantic items, so I suspect it's really ANY metadata that triggers this behavior. Unfortunately, that makes writing rules through the UI difficult as those items with metadata can't be picked from the view for triggers and anywhere else where the model picker is used.
The text was updated successfully, but these errors were encountered: