Announcement

Collapse
No announcement yet.

Data Parsing Error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Data Parsing Error

    Having problems with the InControl app. It stopped working on the Windows 8.1 phone about two weeks ago and I have not been able to get it working since. I cannot connect to the InControl Server with the phone regardless of what I try.

    The Windows Server is running on a HS Zee-S2 and is licensed. I have both InControl WinPhone and InControl WinStore running on the S2 - both are licensed. I have removed all of the plug-ins and downloaded and installed them again. I have done the same with the Windows Phone.

    I have also removed and re-added the app on my Windows 10 machine, and finally removed and installed the new InControl Universal application.

    The only error I receive is a Error 1009 - Data Parsing Error on the Win Phone. I can't get the Universal App on the machine to do anything at all.

    I am using http://xxx.xxx.xxx.xxx as the URL which displays when clicking the View button on the phone. User name is one of the admin accounts set up in Web/HS Touch User Settings and the password is the one set there as well.

    Everything used to work up until about two weeks ago. I had a controller crash about that time but was able to restore successfully from a backup file and everything came back up.

    Appreciate any help you can give me!


    Whenever either the Universal or Phone App try to connect this error is generated in the log:

    Jun-25 23:15:56 Error Getting web page from plugin page 10578:Object reference not set to an instance of an object.

    The credentials are definitely correct - if I change them to something known to be wrong the bad login shows in the Homeseer Log. It would appear that the login is successful and then the Bad Parsing error is thrown. Right afterwards the Object Reference Error appears in the log.
    Last edited by bebaldin; June 25th, 2016, 11:11 PM. Reason: Additional Information

  • #2
    Bebaldin, I'm sorry you are running into issues. Typically the data processing error occurs when a HomeSeer device is not compatible or sending data that the application cannot handle.

    To start determining where the issue is, can you disable all but one device from being sent to InControl, but deselecting the "Show device in InControl" option on the device. The one that remains should be a simple on/off or on/off/dim device. Note, if you have a lot of devices, you can also backup/rename the InControl3.Ini in the HS\Config directory, restart HS and then simply enable one device.

    If that resolves the issue, we can then determine the specific device and work through how to set that up to eliminate the error.

    Let me know how that goes.



    Originally posted by bebaldin View Post
    Having problems with the InControl app. It stopped working on the Windows 8.1 phone about two weeks ago and I have not been able to get it working since. I cannot connect to the InControl Server with the phone regardless of what I try.

    The Windows Server is running on a HS Zee-S2 and is licensed. I have both InControl WinPhone and InControl WinStore running on the S2 - both are licensed. I have removed all of the plug-ins and downloaded and installed them again. I have done the same with the Windows Phone.

    I have also removed and re-added the app on my Windows 10 machine, and finally removed and installed the new InControl Universal application.

    The only error I receive is a Error 1009 - Data Parsing Error on the Win Phone. I can't get the Universal App on the machine to do anything at all.

    I am using http://xxx.xxx.xxx.xxx as the URL which displays when clicking the View button on the phone. User name is one of the admin accounts set up in Web/HS Touch User Settings and the password is the one set there as well.

    Everything used to work up until about two weeks ago. I had a controller crash about that time but was able to restore successfully from a backup file and everything came back up.

    Appreciate any help you can give me!


    Whenever either the Universal or Phone App try to connect this error is generated in the log:

    Jun-25 23:15:56 Error Getting web page from plugin page 10578:Object reference not set to an instance of an object.

    The credentials are definitely correct - if I change them to something known to be wrong the bad login shows in the Homeseer Log. It would appear that the login is successful and then the Bad Parsing error is thrown. Right afterwards the Object Reference Error appears in the log.

    Comment


    • #3
      I found the problem with the data parsing error. What had happened was that one of the child devices for a switch (a KwH metering device) had somehow become enabled with InControl Server. Not sure how this happened because there was no tab in the entry for ICS on this device. I only found it by going to the Device Listing in the plug-in and going through each check box manually.

      Since there was no tab, I had to delete the offending child device and then run a rescan of the root device to pick the child back up. After this InControl connected correctly on my phone and I could see the other devices.

      Not an easy process but it did work.

      I still can't get the new InControl Universal to display anything at all on my Windows 10 machine. Purchased the app last night but all I get is a blank screen when I open it with the name of my server at the top. I can see that the app is connecting in the HS logs as it shows the following:

      Jun-26 07:24:45 InControl Server Completed send of all InControl devices to WINSTORE device

      No devices appear, however.

      Comment


      • #4
        Hi Bebaldin,

        Can you check to make sure that you have the correct HomeSeer version (HS2 or HS3) selected in your HomeSeer Servers setting?

        Also, let's check the error log on the InControl Universal app. First go into Settings/Log Settings, enable the Status to On and Logging Level to Debug. Then close and restart the app. After you do that, you can return to Settings/Log Settings, click Open Log File and then review and paste details here (or send me a private message).

        Thanks!

        Originally posted by bebaldin View Post
        I found the problem with the data parsing error. What had

        I still can't get the new InControl Universal to display anything at all on my Windows 10 machine. Purchased the app last night but all I get is a blank screen when I open it with the name of my server at the top. I can see that the app is connecting in the HS logs as it shows the following:

        Jun-26 07:24:45 InControl Server Completed send of all InControl devices to WINSTORE device

        No devices appear, however.

        Comment


        • #5
          Confirmed to be HS3 in the server settings.

          The take from the log file:

          2016-06-26 12:50:55 - A0001(M) - -------------------------------------------------------------
          2016-06-26 12:50:55 - A0002(M) - Performing initial load of HomeSeer
          2016-06-26 12:50:55 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:51:15 - M1015(M) - Listener started on service name 22315
          2016-06-26 12:51:15 - M1033(M) - UDP Listener started on service name
          2016-06-26 12:51:15 - G8011(N) - Sending message - SOURCE=WSX;TYPE=ACK
          2016-06-26 12:51:16 - G8013(N) - Sending message complete - SOURCE=WSX;TYPE=ACK
          2016-06-26 12:53:58 - A0001(M) - -------------------------------------------------------------
          2016-06-26 12:53:58 - A0002(M) - Performing initial load of HomeSeer
          2016-06-26 12:53:58 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:54:18 - M1015(M) - Listener started on service name 22315
          2016-06-26 12:54:18 - M1033(M) - UDP Listener started on service name
          2016-06-26 12:54:18 - G8011(N) - Sending message - SOURCE=WSX;TYPE=ACK
          2016-06-26 12:54:18 - G8013(N) - Sending message complete - SOURCE=WSX;TYPE=ACK
          2016-06-26 12:58:02 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:58:02 - D8002(E) - Server URL not valid
          2016-06-26 12:58:05 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:58:05 - D8017(N) - Creating devices and groups
          2016-06-26 12:58:05 - D8017(N) - Creating devices and groups
          2016-06-26 12:58:34 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:58:49 - A0001(M) - -------------------------------------------------------------
          2016-06-26 12:58:49 - A0002(M) - Performing initial load of HomeSeer
          2016-06-26 12:58:49 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:59:09 - M1015(M) - Listener started on service name 22315
          2016-06-26 12:59:09 - M1033(M) - UDP Listener started on service name
          2016-06-26 12:59:09 - G8011(N) - Sending message - SOURCE=WSX;TYPE=ACK
          2016-06-26 12:59:09 - G8013(N) - Sending message complete - SOURCE=WSX;TYPE=ACK
          2016-06-26 12:59:25 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:59:28 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:59:28 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:59:29 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:59:29 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:59:29 - D8001(N) - Preparing for http request (Function=)
          2016-06-26 12:59:29 - D8001(N) - Preparing for http request (Function=)


          One thing that I note is that I cannot remove the HomeSeer server I originally created (Zee S2) or Server 1 (which I never made).

          I have also deleted and reinstalled the Winstore plugin but this does not seem to have any effect.

          Comment


          • #6
            I'm very sorry you are having these issues....

            I just pushed a new version of InControl Universal (1.1.10) to the Microsoft Store which will fix the delete issue and also has a new feature to check the connection of your Server settings. So we will definitely want to try that version when it is available (usual takes a few days).

            In the mean time, does the "Demonstration" server work? Also, maybe try creating a brand new HomeSeer server connection. One of the log entries shows "Server URL not valid", so possibly the Server Setting is corrupt.



            Originally posted by bebaldin View Post
            Confirmed to be HS3 in the server settings.




            One thing that I note is that I cannot remove the HomeSeer server I originally created (Zee S2) or Server 1 (which I never made).

            I have also deleted and reinstalled the Winstore plugin but this does not seem to have any effect.

            Comment


            • #7
              The Demonstration server does appear to work fine. I went ahead and removed the app completely and then reinstalled it from the Store. This got rid of the unused server entries. I added my server again but got the same results.

              I think I will wait until the updated version comes out on the Store and try that to see what happens. The custom screens are exactly what I am wanting to use so I hope we can get this resolved. Will post again once I try the newest version with results.

              Comment


              • #8
                Originally posted by lamanmi View Post
                I'm very sorry you are having these issues....

                I just pushed a new version of InControl Universal (1.1.10) to the Microsoft Store which will fix the delete issue and also has a new feature to check the connection of your Server settings. So we will definitely want to try that version when it is available (usual takes a few days).

                In the mean time, does the "Demonstration" server work? Also, maybe try creating a brand new HomeSeer server connection. One of the log entries shows "Server URL not valid", so possibly the Server Setting is corrupt.

                Tried the new version last night but no change in results. The status check always fails with 'Request was canceled' after a few seconds. I tried adding a new connection but this also did not help. The delete function also does not work and crashes the app every time. When the app is restarted, the deleted server reappears.

                I have a Surface on Windows 10 that I will try tonight and see if it will work.

                Comment


                • #9
                  Installed on the Surface - exact same issues. Demonstration mode works but I cannot contact the server. The server check also cancels the same way it does on the desktop.

                  From the HS3 log:

                  Jun-28 23:23:28 InControl Server Completed send of all InControl devices to WINSTORE device

                  Thanks again for looking into this.

                  Comment


                  • #10
                    I added some additional error logic in the next release that may be able to help narrow down the issue. Also, fixed the issue with the Delete. Watch for InControl Universal 1.1.11 to show up in the store over the next few days.

                    In the mean time, just a few more items to check:

                    - Have you tried putting in the IP address of your HomeSeer server (instead of name)
                    - Make sure there are no special characters in the server name, user id and password
                    - Try putting in an incorrect server name and to the check (it should say host not found)
                    - What if you put in an incorrect user id/password

                    Again, I am very sorry you are encountering this issue. We'll get to the bottom of it!!

                    Originally posted by bebaldin View Post
                    Installed on the Surface - exact same issues. Demonstration mode works but I cannot contact the server. The server check also cancels the same way it does on the desktop.

                    From the HS3 log:

                    Jun-28 23:23:28 InControl Server Completed send of all InControl devices to WINSTORE device

                    Thanks again for looking into this.

                    Comment


                    • #11
                      Originally posted by lamanmi View Post
                      I added some additional error logic in the next release that may be able to help narrow down the issue. Also, fixed the issue with the Delete. Watch for InControl Universal 1.1.11 to show up in the store over the next few days.

                      In the mean time, just a few more items to check:

                      - Have you tried putting in the IP address of your HomeSeer server (instead of name)
                      - Make sure there are no special characters in the server name, user id and password
                      - Try putting in an incorrect server name and to the check (it should say host not found)
                      - What if you put in an incorrect user id/password

                      Again, I am very sorry you are encountering this issue. We'll get to the bottom of it!!
                      I have been running the static IP address http://x.x.x.x in the server URL from the beginning so that should not be an issue.

                      Here are the results I get with Check Status:

                      Server URL

                      x.x.x.x Request was Cancelled
                      http:\\x.x.x.x Request was Cancelled
                      <server name> Exception Error
                      http:\\<server name> Exception Error

                      I noticed that you said not to use special characters in the password and mine did, so I set up another account without the special characters. This did not change the results. Note that the WinPhone login works fine with the special characters in the password.

                      Any host name in the Server URL gives an exception error in the status box.

                      If I enter an incorrect password, status returns "Homeseer User ID/Password Not Valid" so it would seem that at least the authentication works.

                      From the HS log:

                      Jul-02 17:01:08 InControl Server ERROR: Login not valid (9002)

                      Changing the password back to the correct value yields:

                      Jul-02 17:02:39 InControl Server Completed send of all InControl devices to WINSTORE device

                      I will keep an eye out for 1.1.11 and upgrade it as soon as I can.

                      Comment


                      • #12
                        1.1.11 hit the store late last night and I downloaded and installed. Not much new to report, unfortunately. I still do not see any devices at all in the app.

                        The delete server function does now seem to work correctly and I was able to delete all of the test entries I had created before, and add my server from scratch. The login was successful - I also tested whether a wrong credential would be rejected and it was - but that was as far as I could get.

                        When testing the connection now, I get the same canceled message but now the client crashes out immediately after every time. It also seems to crash if I leave it sitting on the server profile for even a few seconds.

                        Here are the latest debug logs:

                        2016-07-05 00:23:48 - A0001(M) - -------------------------------------------------------------
                        2016-07-05 00:23:48 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:23:58 - XXXXX(E) - Request cancellation error - TaskCanceledException_ctor_DefaultMessage
                        2016-07-05 00:23:58 - XXXXX(E) - Request cancellation error - <unknown>
                        2016-07-05 00:23:58 - A9999(E) - Error accessing specific homeseer servers
                        2016-07-05 00:23:58 - M1015(M) - Listener started on service name 22315
                        2016-07-05 00:23:58 - M1033(M) - UDP Listener started on service name
                        2016-07-05 00:23:58 - G8011(N) - Sending message - SOURCE=WSX;TYPE=ACK
                        2016-07-05 00:23:58 - G8013(N) - Sending message complete - SOURCE=WSX;TYPE=ACK
                        2016-07-05 00:24:34 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:24:35 - D8017(N) - Creating devices and groups
                        2016-07-05 00:24:35 - D8017(N) - Creating devices and groups
                        2016-07-05 00:25:25 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:25:26 - D8017(N) - Creating devices and groups
                        2016-07-05 00:25:26 - D8019(E) - Data error in results
                        2016-07-05 00:25:26 - D8017(N) - Creating devices and groups
                        2016-07-05 00:25:26 - D8019(E) - Data error in results
                        2016-07-05 00:25:36 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:25:36 - D8017(N) - Creating devices and groups
                        2016-07-05 00:25:36 - D8019(E) - Data error in results
                        2016-07-05 00:25:36 - D8017(N) - Creating devices and groups
                        2016-07-05 00:25:36 - D8019(E) - Data error in results
                        2016-07-05 00:25:51 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:25:51 - D8017(N) - Creating devices and groups
                        2016-07-05 00:25:51 - D8019(E) - Data error in results
                        2016-07-05 00:25:51 - D8017(N) - Creating devices and groups
                        2016-07-05 00:25:51 - D8019(E) - Data error in results
                        2016-07-05 00:26:06 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:26:38 - A0001(M) - -------------------------------------------------------------
                        2016-07-05 00:26:38 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:26:38 - D8017(N) - Creating devices and groups
                        2016-07-05 00:26:38 - D8017(N) - Creating devices and groups
                        2016-07-05 00:26:38 - M1015(M) - Listener started on service name 22315
                        2016-07-05 00:26:38 - M1033(M) - UDP Listener started on service name
                        2016-07-05 00:26:38 - G8011(N) - Sending message - SOURCE=WSX;TYPE=ACK
                        2016-07-05 00:26:38 - G8013(N) - Sending message complete - SOURCE=WSX;TYPE=ACK
                        2016-07-05 00:26:53 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:27:08 - A0001(M) - -------------------------------------------------------------
                        2016-07-05 00:27:08 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:27:18 - XXXXX(E) - Request cancellation error - TaskCanceledException_ctor_DefaultMessage
                        2016-07-05 00:27:18 - XXXXX(E) - Request cancellation error - <unknown>
                        2016-07-05 00:27:18 - A9999(E) - Error accessing specific homeseer servers
                        2016-07-05 00:27:18 - M1015(M) - Listener started on service name 22315
                        2016-07-05 00:27:18 - M1033(M) - UDP Listener started on service name
                        2016-07-05 00:27:18 - G8011(N) - Sending message - SOURCE=WSX;TYPE=ACK
                        2016-07-05 00:27:18 - G8013(N) - Sending message complete - SOURCE=WSX;TYPE=ACK
                        2016-07-05 00:27:39 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:27:42 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 00:27:46 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 05:56:51 - A0001(M) - -------------------------------------------------------------
                        2016-07-05 05:56:51 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 05:57:01 - XXXXX(E) - Request cancellation error - TaskCanceledException_ctor_DefaultMessage
                        2016-07-05 05:57:01 - XXXXX(E) - Request cancellation error - <unknown>
                        2016-07-05 05:57:01 - A9999(E) - Error accessing specific homeseer servers
                        2016-07-05 05:57:01 - M1015(M) - Listener started on service name 22315
                        2016-07-05 05:57:01 - M1033(M) - UDP Listener started on service name
                        2016-07-05 05:57:01 - G8011(N) - Sending message - SOURCE=WSX;TYPE=ACK
                        2016-07-05 05:57:01 - G8013(N) - Sending message complete - SOURCE=WSX;TYPE=ACK
                        2016-07-05 05:57:25 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 05:57:43 - A0001(M) - -------------------------------------------------------------
                        2016-07-05 05:57:43 - D8001(N) - Preparing for http request (Function=)
                        2016-07-05 05:57:53 - XXXXX(E) - Request cancellation error - TaskCanceledException_ctor_DefaultMessage
                        2016-07-05 05:57:53 - XXXXX(E) - Request cancellation error - <unknown>
                        2016-07-05 05:57:53 - A9999(E) - Error accessing specific homeseer servers
                        2016-07-05 05:57:53 - M1015(M) - Listener started on service name 22315
                        2016-07-05 05:57:53 - M1033(M) - UDP Listener started on service name
                        2016-07-05 05:57:53 - G8011(N) - Sending message - SOURCE=WSX;TYPE=ACK
                        2016-07-05 05:57:54 - G8013(N) - Sending message complete - SOURCE=WSX;TYPE=ACK

                        Comment


                        • #13
                          Thanks for working through this. One more build has been submitted to the store (1.1.12). As normal it will take a few days for it to appear. That exception you are encountering implies that the call to the server is timing out. It was at 10 seconds, I have increased it to 30 seconds, lets see if that helps. In addition, the app has the ability to communicate with other instances of the app on other devices, I added a setting to disable that by default to eliminate other problems. Also, I again added further debug information. Please note/try the following:

                          - Approximately how many devices do you have marked to be sent to InControl?
                          - Ensure the InControl Universal Log Settings are set to DEBUG and give it another try

                          Let me know how it goes.



                          Originally posted by bebaldin View Post
                          1.1.11 hit the store late last night and I downloaded and installed. Not much new to report, unfortunately. I still do not see any devices at all in the app.

                          Comment


                          • #14
                            SUCCESS!

                            Whatever changes were made in 1.1.12 - it seems to have fixed all the problems. All of my devices loaded up immediately and I am able to use all the features.

                            Can't wait to start designing custom screens in Universal. Thank you again!

                            Comment


                            • #15
                              Great news!!! Over the next few weeks I'll be publishing more instructions on how to fully use the Universal capability. There is a lot there already, but looking to continue to grow that out.....

                              Originally posted by bebaldin View Post
                              Whatever changes were made in 1.1.12 - it seems to have fixed all the problems. All of my devices loaded up immediately and I am able to use all the features.

                              Can't wait to start designing custom screens in Universal. Thank you again!

                              Comment

                              Working...
                              X