We have moved at community.getvera.com

Author Topic: [Solved] Waiting Initial Data  (Read 2302 times)

Offline rafale77

  • Community Beta
  • Hero Member
  • ******
  • Posts: 1749
  • Karma: +101/-27
  • HA ≠ IoT as a blue sky is cloudless.
[Solved] Waiting Initial Data
« on: September 02, 2017, 01:35:12 pm »
I've been having a problem with ALTUI not loading since 2 weeks ago.
I am not sure what is causing it. The exact same symptom is observed both on the Vera Plus itself and on Openluup.

The UI starts loading and is stuck at "waiting initial data". What could be causing it? I don't know that I made any changes to the vera itself. Could it be looking for some website information and that my firewall is blocking it?
« Last Edit: November 29, 2017, 12:17:06 pm by amg0 »
openLuup (79 devices, 141 scenes, 19 apps) master to VeraPlus (142 zwave nodes, 8 Zigbee nodes, 221 devices,  20 scenes , 2 apps) +  Hubitat (15 Zigbee nodes) + Home-Assistant (API Integrations). Bridged to Siri and Alexa. Homewave. VeraPlus ExtRooted and mios server independent.

Offline amg0

  • Moderator
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: Waiting Initial Data
« Reply #1 on: September 02, 2017, 02:14:25 pm »
I've been having a problem with ALTUI not loading since 2 weeks ago.
I am not sure what is causing it. The exact same symptom is observed both on the Vera Plus itself and on Openluup.

The UI starts loading and is stuck at "waiting initial data". What could be causing it? I don't know that I made any changes to the vera itself. Could it be looking for some website information and that my firewall is blocking it?
It must load some js file from various cdn. Check the console log or the dev tools network page in chrome (f12) for some failures.

Offline rafale77

  • Community Beta
  • Hero Member
  • ******
  • Posts: 1749
  • Karma: +101/-27
  • HA ≠ IoT as a blue sky is cloudless.
Re: Waiting Initial Data
« Reply #2 on: September 02, 2017, 02:47:14 pm »
Thank you.

This is what the I am seeing on chrome (it fails also on Safari and edge)

Failed to load resource: the server responded with J_SiteSensor1_ALTUI.js a status of 404 (Not Found)

I am also getting a warning:
A Parser-blocking, cross site (i.e. different eTLD+1) script, https://www.google.com/uds/api/visualization/1.0/40ff64b1d9d6b3213524485974f36cc0/format+en,default+en,ui+en,table+en,gauge+en.I.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.

I am going to look up that js file. Not sure why it is not found.

Edit: No idea what this js file is I see no reference to it anywhere...
« Last Edit: September 02, 2017, 04:31:17 pm by rafale77 »
openLuup (79 devices, 141 scenes, 19 apps) master to VeraPlus (142 zwave nodes, 8 Zigbee nodes, 221 devices,  20 scenes , 2 apps) +  Hubitat (15 Zigbee nodes) + Home-Assistant (API Integrations). Bridged to Siri and Alexa. Homewave. VeraPlus ExtRooted and mios server independent.

Offline rafale77

  • Community Beta
  • Hero Member
  • ******
  • Posts: 1749
  • Karma: +101/-27
  • HA ≠ IoT as a blue sky is cloudless.
Re: Waiting Initial Data
« Reply #3 on: September 03, 2017, 02:41:23 am »
Found the problem. the sitesensor files are not all being downloaded. got it all fixed by manually uploading them.
openLuup (79 devices, 141 scenes, 19 apps) master to VeraPlus (142 zwave nodes, 8 Zigbee nodes, 221 devices,  20 scenes , 2 apps) +  Hubitat (15 Zigbee nodes) + Home-Assistant (API Integrations). Bridged to Siri and Alexa. Homewave. VeraPlus ExtRooted and mios server independent.

Offline ndoggac

  • Sr. Newbie
  • *
  • Posts: 42
  • Karma: +0/-0
Re: Waiting Initial Data
« Reply #4 on: November 27, 2017, 06:58:44 pm »
I'm seeing this same issue across all browsers after the last update.  How do I fix this?

Offline amg0

  • Moderator
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: Waiting Initial Data
« Reply #5 on: November 28, 2017, 12:47:18 am »
I'm seeing this same issue across all browsers after the last update.  How do I fix this?
Get on chrome open altui and and check what is in the console JavaScript
Ctrl + J

?dit : I see lots of users already on version 2245 so it must be a local problem
« Last Edit: November 28, 2017, 05:33:36 am by amg0 »

Offline ndoggac

  • Sr. Newbie
  • *
  • Posts: 42
  • Karma: +0/-0
Re: Waiting Initial Data
« Reply #6 on: November 28, 2017, 10:26:22 am »
Attached screen cap of chrome output.  I have ad-blocker disabled.

Offline amg0

  • Moderator
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: Waiting Initial Data
« Reply #7 on: November 28, 2017, 12:00:01 pm »
Attached screen cap of chrome output.  I have ad-blocker disabled.

please confirm exact version of ALTUI and your setup ( back end / front end )
in case of doubt force full install (onVERA) with
http://<yourip>:3480/data_request?id=action&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=CreatePlugin&PluginNum=8246&Version=35132

Make sure you do luup reload and then browser refresh

Offline amg0

  • Moderator
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: Waiting Initial Data
« Reply #8 on: November 28, 2017, 04:33:33 pm »
I potentially detected a load issue which could be visible on slower environment.
you can try the version on https://github.com/amg0/ALTUI to see if that works for you and let me know

Offline ndoggac

  • Sr. Newbie
  • *
  • Posts: 42
  • Karma: +0/-0
Re: Waiting Initial Data
« Reply #9 on: November 29, 2017, 09:43:36 am »
For whatever reason, it seemed to fix itself, and I was able to grab the next update.  Will update if I see the problem again.

Offline rafale77

  • Community Beta
  • Hero Member
  • ******
  • Posts: 1749
  • Karma: +101/-27
  • HA ≠ IoT as a blue sky is cloudless.
Re: [Solved] Waiting Initial Data
« Reply #10 on: December 24, 2017, 11:23:40 am »
@amg0, I am having issues with .js files from apps which were deleted and for which I delete files on vera units.

Somehow when ALTUI loads it is looking for the js files from these apps which are no longer on the unit. I am being forced to keep the .js files for them. I noticed in particular that the apps from Rigpapa have this problem. Both DeusExMachinaII and SiteSensor have been problematic for me. I try to keep my units clean and I sometimes move an app from one unit to another or to Openluup so when I delete an app, I delete all the files too. This prevents ALTUI from loading.
openLuup (79 devices, 141 scenes, 19 apps) master to VeraPlus (142 zwave nodes, 8 Zigbee nodes, 221 devices,  20 scenes , 2 apps) +  Hubitat (15 Zigbee nodes) + Home-Assistant (API Integrations). Bridged to Siri and Alexa. Homewave. VeraPlus ExtRooted and mios server independent.

Offline amg0

  • Moderator
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: [Solved] Waiting Initial Data
« Reply #11 on: December 24, 2017, 05:26:46 pm »
@amg0, I am having issues with .js files from apps which were deleted and for which I delete files on vera units.

Somehow when ALTUI loads it is looking for the js files from these apps which are no longer on the unit. I am being forced to keep the .js files for them. I noticed in particular that the apps from Rigpapa have this problem. Both DeusExMachinaII and SiteSensor have been problematic for me. I try to keep my units clean and I sometimes move an app from one unit to another or to Openluup so when I delete an app, I delete all the files too. This prevents ALTUI from loading.

Once an app declared itself into altui to act as a display plugin, it will be required...  you can reset altui config to default to overcome that problems.

Offline rafale77

  • Community Beta
  • Hero Member
  • ******
  • Posts: 1749
  • Karma: +101/-27
  • HA ≠ IoT as a blue sky is cloudless.
Re: [Solved] Waiting Initial Data
« Reply #12 on: December 26, 2017, 01:41:15 am »
Once an app declared itself into altui to act as a display plugin, it will be required...  you can reset altui config to default to overcome that problems.

Thanks! I will try that. How do you reset the config by the way? Sounds like a dummy question but I actually looked and couldn't find anything on the UI.
openLuup (79 devices, 141 scenes, 19 apps) master to VeraPlus (142 zwave nodes, 8 Zigbee nodes, 221 devices,  20 scenes , 2 apps) +  Hubitat (15 Zigbee nodes) + Home-Assistant (API Integrations). Bridged to Siri and Alexa. Homewave. VeraPlus ExtRooted and mios server independent.

Offline amg0

  • Moderator
  • Master Member
  • *****
  • Posts: 3174
  • Karma: +210/-8
Re: [Solved] Waiting Initial Data
« Reply #13 on: December 26, 2017, 03:40:13 am »
Once an app declared itself into altui to act as a display plugin, it will be required...  you can reset altui config to default to overcome that problems.

Thanks! I will try that. How do you reset the config by the way? Sounds like a dummy question but I actually looked and couldn't find anything on the UI.

Altui device settings page, button : default config. Or you can empty the variable  pluginconfig of the altui device
Either method, reload lump after.
( I am not in front of it right now so exact names or label can be slightly different. )

Offline powisquare

  • Full Member
  • ***
  • Posts: 146
  • Karma: +1/-0
Re: [Solved] Waiting Initial Data
« Reply #14 on: December 03, 2018, 06:19:44 am »
Have something similar. After hitting Default Configuration button in the Settings menu AltUI works normally for a while but then reverts back to Waiting Initial Data. I don't have AutoVirtualThermostat installed on this Vera - but I do on a separate pi. Is this the issue?

12/03/18 11:06:35.309   luup_log:27: ALTUI: debug: myALTUI_Handler: request is: ALTUI_Handler <0x2e8de680>
50   12/03/18 11:06:35.310   luup_log:27: ALTUI: debug: myALTUI_Handler: parameters is: { "command": "home" } <0x2e8de680>
02   12/03/18 11:06:36.759   luvd_get_info mg conn can't read /etc/cmh-ludl//J_AutoVirtualThermostat1_ALTUI.js or /etc/cmh-lu//J_AutoVirtualThermostat1_ALTUI.js from filename /J_AutoVirtualThermostat1_ALTUI.js pPtrFile (null) <0x2e2de680>
01   12/03/18 11:06:42.253   UserData::WriteUserData saved--before move File Size: 40571 save size 40571 <0x2ba83680>
02   12/03/18 11:06:42.253   UserData::TempLogFileSystemFailure start 0 <0x2ba83680>
02   12/03/18 11:06:42.279   UserData::TempLogFileSystemFailure 4857 res:1