search

openhab / openhab-webui

Web UIs of openHAB
Eclipse Public License 2.0
221 stars 240 forks source link

Items Popup shows inconsistent list #2059

Closed JohnRoden78 closed 1 year ago

JohnRoden78 commented 1 year ago

The problem

I am setting up openHAB to control a set of Z-Wave radiator thermostatic valves. Some months ago, I tested openHAB V3 with 4 things (radiator controls coded CV, OJ, HL, SR). OpenHAB was subsequently updated (automatically) to V4. The test setup appeared to work without significant change.

I recently attempted to add 4 additional things (radiator valves, coded BD2, DR1,DR2,HP ) to openHAB but have run into a stange behavior. The new things were added as equipment to the model in the normal way and their channels appeared as expected in the items list (see openHAB_Items...). However, these same items do not appear when I attempt to assign the items to a widget (see openHAB_Widget_A...). The client browser is connected to http://192.168.0.64:8080).

THe openHAB server running on 192.168.0.64 can also be accessed via myopenHAB.org. Using this connection, the web interface behaves as expected, allowing the items to be seen in the popup list.

Expected behavior

All items in the Items page should appear in the items popup list. THe Web UI should behave the same way when accessed directly or via myopenHAB.org.

Steps to reproduce

  1. Given in the description of the problem. Not clear how to create a simple test case.

Your environment

runtimeInfo: version: 4.0.2 buildString: Release Build locale: en-IE systemInfo: configFolder: /etc/openhab userdataFolder: /var/lib/openhab logFolder: /var/log/openhab javaVersion: 17.0.7 javaVendor: Red Hat, Inc. javaVendorVersion: (Red_Hat-17.0.7.0.7-4.fc38) osName: Linux osVersion: 6.2.15-300.fc38.x86_64 osArchitecture: amd64 availableProcessors: 4 freeMemory: 149526544 totalMemory: 329252864 startLevel: 100 bindings: null clientInfo: device: ios: false android: false androidChrome: false desktop: true iphone: false ipod: false ipad: false edge: false ie: false firefox: true macos: false windows: false cordova: false phonegap: false electron: false nwjs: false webView: false webview: false standalone: false pixelRatio: 1 prefersColorScheme: light isSecureContext: false locationbarVisible: true menubarVisible: true navigator: cookieEnabled: true deviceMemory: N/A hardwareConcurrency: 8 language: en-US languages:

Browser console

I don't see anything relevant in the following but including it in case I've missed something.

``loading i18n messages from: ./tl.json app.e4469a9e02bf8bc86419.js:7:832018 loading i18n messages from: ./tr.json app.e4469a9e02bf8bc86419.js:7:832018 loading i18n messages from: ./uk.json app.e4469a9e02bf8bc86419.js:7:832018 loading i18n messages from: ./zh.json app.e4469a9e02bf8bc86419.js:7:832018 SSE connection closed: http://192.168.0.64:8080/rest/events?topics=openhab/items/*/added,openhab/items/*/removed,openhab/items/*/updated, 0 open app.e4469a9e02bf8bc86419.js:35:157010 Array [] loading i18n messages from: ./bg.json app.e4469a9e02bf8bc86419.js:7:832018 Proxy: need ZWave_Node_043_Radiator_BD2_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_043_Radiator_BD2_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_044_Radiator_OM_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_044_Radiator_OM_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_039_Radiator_HL_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_039_Radiator_HL_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_033_Radiator_OJ_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_033_Radiator_OJ_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_040_Radiator_SR_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_040_Radiator_SR_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_038_Radiator_CV_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Proxy: need ZWave_Node_038_Radiator_CV_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: Pending tracking list update, not calling the API app.e4469a9e02bf8bc86419.js:7:736944 Updating tracking list: ["ZWave_Node_030_DSB28_Home_Energy_Meter_G2_Electric_meter_watts","ZWave_Node_002_ZW100_MultiSensor_6_Sensor_temperature","ZWave_Node_047_Boiler_OnOff_Switch","ZWave_Node_041_Radiator_HP_Sensor_temperature","ZWave_Node_041_Radiator_HP_Setpoint_heating","ZWave_Node_042_Radiator_BD1_Sensor_temperature","ZWave_Node_042_Radiator_BD1_Setpoint_heating","ZWave_Node_043_Radiator_BD2_Sensor_temperature","ZWave_Node_043_Radiator_BD2_Setpoint_heating","ZWave_Node_044_Radiator_OM_Sensor_temperature","ZWave_Node_044_Radiator_OM_Setpoint_heating","ZWave_Node_039_Radiator_HL_Sensor_temperature","ZWave_Node_039_Radiator_HL_Setpoint_heating","ZWave_Node_033_Radiator_OJ_Sensor_temperature","ZWave_Node_033_Radiator_OJ_Setpoint_heating","ZWave_Node_040_Radiator_SR_Sensor_temperature","ZWave_Node_040_Radiator_SR_Setpoint_heating","ZWave_Node_038_Radiator_CV_Sensor_temperature","ZWave_Node_038_Radiator_CV_Setpoint_heating"] app.e4469a9e02bf8bc86419.js:7:737226 Setting keepalive interval seconds 10 47 app.e4469a9e02bf8bc86419.js:35:156427 Update item to UT 24.app.e4469a9e02bf8bc86419.js:1:27784 {"item":"UT","max":30,"min":5,"stepSize":0.5,"title":"Set Heat Point"} app.e4469a9e02bf8bc86419.js:23:14076 Setting keepalive interval seconds 10 app.e4469a9e02bf8bc86419.js:35:156427 Update item to ZWave_Node_033_Radiator_OJ_Sensor_temperature 24.app.e4469a9e02bf8bc86419.js:1:27784 {"item":"ZWave_Node_033_Radiator_OJ_Sensor_temperature","max":30,"min":5,"stepSize":0.5,"title":"Set Heat Point"} app.e4469a9e02bf8bc86419.js:23:14076 Setting keepalive interval seconds 10 189 app.e4469a9e02bf8bc86419.js:35:156427 Stop tracking states app.e4469a9e02bf8bc86419.js:7:736625 SSE connection closed: http://192.168.0.64:8080/rest/events/states, 0 open app.e4469a9e02bf8bc86419.js:35:157010 Array [] app.e4469a9e02bf8bc86419.js:35:157096 Proxy: need ZWave_Node_030_DSB28_Home_Energy_Meter_G2_Electric_meter_watts app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_002_ZW100_MultiSensor_6_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_047_Boiler_OnOff_Switch app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_041_Radiator_HP_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_041_Radiator_HP_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_042_Radiator_BD1_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_033_Radiator_OJ_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_043_Radiator_BD2_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_043_Radiator_BD2_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_044_Radiator_OM_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_044_Radiator_OM_Setpoint_heating app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Proxy: need ZWave_Node_039_Radiator_HL_Sensor_temperature app.e4469a9e02bf8bc86419.js:7:735276 updateTrackingList: No connection id, not calling the API app.e4469a9e02bf8bc86419.js:7:737464 Uncaught (in promise) Not Found



## Browser network traffic

<!--
Open the developer tools in your browser, go to the Network tab and paste
screenshots of the network traffic and the details of individual requests that failed.
-->

See attached openHAB_Network_A*.  This shows network activity for loading the WebUI page and showing the items popup (with missing items).
![openHAB_Items_A_2023-09-10_17-09-08](https://github.com/openhab/openhab-webui/assets/16032520/5b0bf602-bfa9-41a8-8240-6e04c40e7419)
![openHAB_Network_A_2023-09-10_17-46-08](https://github.com/openhab/openhab-webui/assets/16032520/ef3ce15f-e11d-4696-aef6-8b79707176bc)
![openHAB_Widget_A_2023-09-10_16-30-32](https://github.com/openhab/openhab-webui/assets/16032520/c9b0d2e4-02e8-41d1-b487-a142aed2dac5)
![openHAB_Widget_B_2023-09-10_16-32-34](https://github.com/openhab/openhab-webui/assets/16032520/9d236aa1-83fa-45b2-8359-92ccf47deea2)
![openHAB_Widget_C_2023-09-10_16-34-33](https://github.com/openhab/openhab-webui/assets/16032520/0c7cb479-89fe-43c9-8272-4de5817e8d16)
![openHAB_Widget_D_2023-09-10_16-34-33](https://github.com/openhab/openhab-webui/assets/16032520/817989c1-c332-4d24-91fb-2d6d9019f633)
![openHAB_Widget_E_2023-09-10_16-39-03](https://github.com/openhab/openhab-webui/assets/16032520/36f86635-361e-400a-9d66-8c2271160108)

​
## Additional information

<!--
Provide any information not pertinent to the above sections that you'd still like to share.
-->
JohnRoden78 commented 1 year ago

The attached files in the previous message are screenshots referenced in the text by the first words of the file name (e.g openHAB_Widget_A). They illustrate the case made in the text.

JustinGeorgi commented 1 year ago

firefox: true

This is a firefox issue. Its page caching has started interfering with UI pages properly getting updated information. You will not see the issue if you use a different browser. There are numerous reports in the forum of different areas in the UI where these symptoms appear.

I don't know if there's a fix on the UI side for this. Some users who wish to continue to use firefox have disabled page caching, but I don't know if that can be done on a page or domain level and I believe they have simply disabled all page caching which will have a notable impact on browser performance.

JohnRoden78 commented 1 year ago

Justin, many thanks for the rapid reply. It's odd that the UI seems to work via myopenHAB.org but not with the local connection. I'll investigate further when I get time. At least I have a workaround. Thanks again. John (should I close this bug -- it's not solved but is explained?)

florian-h05 commented 1 year ago

should I close this bug -- it's not solved but is explained?

Since it is a Firefox issue and no UI issue (although UI might be able to implement some workaround), yes.