Item Does Not Appear in Model

Setup, Configuration and Use Items & Sitemaps
1

Run OH 4.0.2 Release on a RPi 4B running openhabian

I have one item on a device that I cannot get to appear on the Model. I’m sure I’m missing something, but it sure looks like it should be there.

Based on How Group Items are displayed via UI, I played with the Semantic Class, but nothing I tried made a difference. There doesn’t appear to be a Semantic Property for a Color Item.

Here is the item:

image
image735×1333 49 KB

and its code:

label: colour_data
type: Color
category: ColorLight
groupNames:
  - Lumary_retrofit_recessed_can_lights_A2
  - gExteriorLightsColor
groupType: None
function: null
tags:
  - Setpoint
  - Point

It is a member of an Equipment Group
![image|287x500](upload://qDrStjZw8uRnrND2k28gjseCILW.png)

Other items in the group work as expected, e.g.
![image|342x500](upload://rW0BzgOYtQ2bU57anYzK6rjEC0r.png)


label: bright_value
type: Dimmer
category: Light
groupNames:
  - Lumary_retrofit_recessed_can_lights_A2
  - gOLP_Brightness
groupType: None
function: null
tags:
  - Setpoint
  - Point

In the Semantic Model, this is what I see:
image
The Color Item doesn’t show up.

I appreciate any suggestions to help me troubleshoot this.

2

If you are running Firefox there is a known issue without a solution right now. Firefox changed how they are doing caching which is resulting in changes made through MainUI not appearing in MainUI until you do a force reload of the page. IIRC ctrl-shift-r will do that. Restarting the browser should also work. Or use ony of the other browsers.

3

Thanks for the suggestion.

I’m using the Brave browser, which I understand is based on Chrome. Regardless I tried a forced reload and a different browser (Edge), with the same, unchanged result.

Any other suggestions?

4

I don’t have access to my OH instance at the moment. Make sure that the Item contains only one tag of a given type, IIRC “Setpoint” is a type of “Point” tag. Having both a “Setpoint” and “Point” tag is likely to cause problems. I would expect to see tags along the lines of “Setpoint” and “Light” or “Color” (is there a Color tag?) for an Item like this.

Make sure that only one of Luminary_retrofit_recessed_can_lights_A2 and gExteriorLightsColor are semantically tagged. If both are that means this one Point Item appears in the model in two different places which is not allowed.

Look at the logs for potential circular Group membership errors or any other errors for that matter.

5

Thanks for the additional suggestions.

Color is not one of the options for Semantic Property in the UI (I assume that is what you mean by a Tag).

I tried removing the “Point” tag, which I had added because one of the other items that works had it. I selected “Light” from the Semantic Property list. No change in behavior.

gExteriorLightsColor has no tags.

I searched the openhab log for errors. None of what I found looks like they would be relevant. Perhaps I need to restart openhab and look in that log.

openhabian@openhabian-spring4:/var/log/openhab $ cat openhab.log | grep -i error
2023-12-13 04:47:59.272 [DEBUG] [ernal.communication.RokuCommunicator] - Error executing player GET command, URL: http://192.168.1.127:8060/query/device-info, java.io.EOFException: HttpConnectionOverHTTP@e5028d::SocketChannelEndPoint@465854{l=/192.168.1.151:37164,r=/192.168.1.127:8060,ISHUT,fill=-,flush=-,to=0/0}{io=0/0,kio=0,kro=1}->HttpConnectionOverHTTP@e5028d(l:/192.168.1.151:37164 <-> r:/192.168.1.127:8060,closed=false)=>HttpChannelOverHTTP@1bef51b(exchange=HttpExchange@16c258{req=HttpRequest[GET /query/device-info HTTP/1.1]@17443d[TERMINATED/null] res=HttpResponse[null 0 null]@233b13[PENDING/null]})[send=HttpSenderOverHTTP@c515a1(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@9b1863{s=START}],recv=HttpReceiverOverHTTP@b8221(rsp=IDLE,failure=null)[HttpParser{s=CLOSED,0 of -1}]] 
2023-12-13 05:34:05.952 [DEBUG] [ernal.communication.RokuCommunicator] - Error executing player GET command, URL: http://192.168.1.91:8060/query/device-info, java.io.EOFException: HttpConnectionOverHTTP@2b5f5b::SocketChannelEndPoint@67c0a6{l=/192.168.1.151:45204,r=/192.168.1.91:8060,ISHUT,fill=-,flush=-,to=0/0}{io=0/0,kio=0,kro=1}->HttpConnectionOverHTTP@2b5f5b(l:/192.168.1.151:45204 <-> r:/192.168.1.91:8060,closed=false)=>HttpChannelOverHTTP@cd1046(exchange=HttpExchange@2ac9ee{req=HttpRequest[GET /query/device-info HTTP/1.1]@ab8177[TERMINATED/null] res=HttpResponse[null 0 null]@7d0774[PENDING/null]})[send=HttpSenderOverHTTP@46add(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@c5b28a{s=START}],recv=HttpReceiverOverHTTP@9b3b5c(rsp=IDLE,failure=null)[HttpParser{s=CLOSED,0 of -1}]] 
2023-12-13 06:10:04.369 [DEBUG] [ernal.communication.RokuCommunicator] - Error executing player GET command, URL: http://192.168.1.127:8060/query/device-info, java.io.EOFException: HttpConnectionOverHTTP@1d5fb86::SocketChannelEndPoint@c6125d{l=/192.168.1.151:47308,r=/192.168.1.127:8060,ISHUT,fill=-,flush=-,to=1/0}{io=0/0,kio=0,kro=1}->HttpConnectionOverHTTP@1d5fb86(l:/192.168.1.151:47308 <-> r:/192.168.1.127:8060,closed=false)=>HttpChannelOverHTTP@d450fe(exchange=HttpExchange@1af0c85{req=HttpRequest[GET /query/device-info HTTP/1.1]@132c2bd[TERMINATED/null] res=HttpResponse[null 0 null]@11c72fc[PENDING/null]})[send=HttpSenderOverHTTP@19b9001(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@4b7493{s=START}],recv=HttpReceiverOverHTTP@10d714d(rsp=IDLE,failure=null)[HttpParser{s=CLOSED,0 of -1}]] 
2023-12-13 06:56:41.059 [WARN ] [ntrol.internal.connection.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"f7ef0608-aca2-44df-8aa0-891519436a2e","entityType":"APPLIANCE","parameters":{"action":"turnOn"}}]}' resulted in error(s): {"entity":{"entityId":"f7ef0608-aca2-44df-8aa0-891519436a2e","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-12-13 07:00:01.184 [WARN ] [ntrol.internal.connection.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"f7ef0608-aca2-44df-8aa0-891519436a2e","entityType":"APPLIANCE","parameters":{"action":"turnOn"}}]}' resulted in error(s): {"entity":{"entityId":"f7ef0608-aca2-44df-8aa0-891519436a2e","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-12-13 07:07:41.607 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to execute rule 'SetFrontSmartLightTuyaStatus': Failed to execute action: 1(Unexpected error from weaving hook.)
2023-12-13 07:10:09.129 [WARN ] [ntrol.internal.connection.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"dd4ce484-58a3-4421-80d8-9240e2251afc","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"dd4ce484-58a3-4421-80d8-9240e2251afc","entityType":"APPLIANCE"},"code":"NoSuchTargetError","message":"NO_SUCH_ENDPOINT","data":null}
2023-12-13 07:24:06.373 [WARN ] [ntrol.internal.connection.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"f7ef0608-aca2-44df-8aa0-891519436a2e","entityType":"APPLIANCE","parameters":{"action":"turnOff"}}]}' resulted in error(s): {"entity":{"entityId":"f7ef0608-aca2-44df-8aa0-891519436a2e","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-12-13 07:58:25.471 [WARN ] [ntrol.internal.connection.Connection] - Smart home device command failed. The request '{"controlRequests":[{"entityId":"f7ef0608-aca2-44df-8aa0-891519436a2e","entityType":"APPLIANCE","parameters":{"action":"turnOn"}}]}' resulted in error(s): {"entity":{"entityId":"f7ef0608-aca2-44df-8aa0-891519436a2e","entityType":"APPLIANCE"},"code":"TargetApplianceUnreachableException","message":"ENDPOINT_UNREACHABLE","data":null}
2023-12-13 08:38:12.498 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to execute rule 'SetFrontSmartLightTuyaStatus': Failed to execute action: 1(Unexpected error from weaving hook.)
2023-12-13 08:41:05.933 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to execute rule 'SetFrontSmartLightTuyaStatus': Failed to execute action: 1(Unexpected error from weaving hook.)
2023-12-13 09:09:31.162 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to execute rule 'AniCloudDeviceLocationChangedCalculateDistanceAndPresence': Failed to execute action: 2(Unexpected error from weaving hook.)
2023-12-13 09:37:02.664 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to execute rule 'SetFrontSmartLightTuyaStatus': Failed to execute action: 1(Unexpected error from weaving hook.)
2023-12-13 10:57:16.819 [DEBUG] [ernal.communication.RokuCommunicator] - Error executing player GET command, URL: http://192.168.1.67:8060/query/device-info, java.io.EOFException: HttpConnectionOverHTTP@24f3a7::SocketChannelEndPoint@1c0a97b{l=/192.168.1.151:46654,r=/192.168.1.67:8060,ISHUT,fill=-,flush=-,to=0/0}{io=0/0,kio=0,kro=1}->HttpConnectionOverHTTP@24f3a7(l:/192.168.1.151:46654 <-> r:/192.168.1.67:8060,closed=false)=>HttpChannelOverHTTP@1be7748(exchange=HttpExchange@a6ad3{req=HttpRequest[GET /query/device-info HTTP/1.1]@1001bfe[TERMINATED/null] res=HttpResponse[null 0 null]@1a1f4d4[PENDING/null]})[send=HttpSenderOverHTTP@11bd7df(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@e7e5d{s=START}],recv=HttpReceiverOverHTTP@17844c9(rsp=IDLE,failure=null)[HttpParser{s=CLOSED,0 of -1}]] 
2023-12-13 10:57:29.941 [ERROR] [e.automation.internal.RuleEngineImpl] - Failed to execute rule 'SetFrontSmartLightTuyaStatus': Failed to execute action: 1(Unexpected error from weaving hook.)
openhabian@openhabian-spring4:/var/log/openhab $

I think I will look at the items in the API and see if I notice any differences.

6

Yes, that’s what I mean and I must have been remembering the Colortemperature tag. Ultimately it doesn’t matter so long as certain rules are applied:

  • Only one of a Location tag, Equipment tag, or Point tag are allowed (can’t have an Equipment and a Point or two Point tags).
  • If a Point tag is applied, there is an optional property tag that can be applied. Property tags cannot be used with Locations or Equipment.
  • Any semantically tagged Item can only appear in the model once. You can’t have a light in two different locations at the same time (for example).

If you check “show non-semantic items” does this Item show up?

7

No. I can’t find it anywhere on the Model list, even with the box checked.

8

Have you tried a force reload to see if ti appears. If it doesn’t appear at all it’s probably not an issue with the Item. MainUI’s Model view simply knows nothing about the existence of this Item.

9

Deleted the item. Then created a new one from the channel for the Thing in UI. The new one appears in the Semantic Model.

Thanks!