Announcement

Collapse
No announcement yet.

Reverse Geocode error

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

    Reverse Geocode error

    I'm seeing this error in the logs:


    PHP Code:
    Sep-26 9:46:14 AM         PHLocation Error    (UpdateUserDeviceError getting reverse geocode for [412Lat39.xxxxxxxxxx Lon:-119.xxxxxxxxxxx 
    Michael

    #2
    I have also been getting the same error consistently in my logs. My location devices still seem to be updating but thought I would at least chime in.


    Sent from my iPad using Tapatalk
    HS4 4.2.6.0 &HSTouch Designer 3.0.80
    Plugin's:
    BLBackup, BLOccupied, BLShutdown, EasyTrigger, Ecobee, Nest, AK Bond
    EnvisaLink DSC, PHLocation, Pushover, SONOS, Blue Iris, UltraRachio3,
    weatherXML, Jon00 Alexa Helper, Network Monitor, MyQ, Z-Wave

    Comment


      #3
      Same issue for me. I only got one instance of this error today. It was for the 3rd point of a 4 point travel.

      Comment


        #4
        I suspect that Google have stopped free (without an API key) use of one or more of their API's which is why you see these errors.

        If you have obtained a Google Maps API key and entered it on the plug-in config page, then you will see these errors only if you exceed the free allowances.

        I have recently been reviewing the legalities of using various Google API's within the plug-in and even though it isn't for commercial gain the use of some API's may be bordering on a breach of the terms of use.

        I am currently looking at alternative solutions which will allow the plug-in to stay free of charge and not contravene any terms of use.

        Paul..

        Comment


          #5
          Originally posted by sooty View Post
          I suspect that Google have stopped free (without an API key) use of one or more of their API's which is why you see these errors ...
          Paul,

          I've checked my logs. For me, this error popped up every day since the 24th, both with my phone and my wife's. The errors are always a travel point in the middle of the total travel. This seems to indicate that requests subsequent to a given error are successful.

          Comment


            #6
            Originally posted by claude View Post
            Paul,

            I've checked my logs. For me, this error popped up every day since the 24th, both with my phone and my wife's. The errors are always a travel point in the middle of the total travel. This seems to indicate that requests subsequent to a given error are successful.
            From time to time you will see errors with the various Google API's like reverse geocoding. They can be associated with many different causes. The service may not be available at the time of the query for whatever reason or it may not be able to return an address for a given set of coordinates etc, etc...

            Generally the API does give a reason for the failure and I include this in the resulting HS3 log entry but for some unknown reason I neglected to do this with the reverse geocode.

            In your case, does it always happen at (or near to) the same location?

            Paul..

            Comment


              #7
              Originally posted by Rvtravlr View Post
              I'm seeing this error in the logs:


              PHP Code:
              Sep-26 9:46:14 AM         PHLocation Error    (UpdateUserDeviceError getting reverse geocode for [412Lat39.xxxxxxxxxx Lon:-119.xxxxxxxxxxx 
              Can I ask what version of the plug-in you are running?

              Reason is that I can't find that error message in the latest code.

              Paul..

              Comment


                #8
                Originally posted by sooty View Post
                ... In your case, does it always happen at (or near to) the same location? Paul..
                Different places, no apparent pattern. Using 3.0.1.90

                Comment


                  #9
                  Originally posted by claude View Post
                  Different places, no apparent pattern. Using 3.0.1.90
                  Claude,

                  Would you mind emailing or PMing me one of the actual recent entries from your log sowing the error. I'm searching the plug-in code for the exact error that Rvtravlr posted and I can't find it which is leading me to think that it was produced by an older version of the plug-in.

                  I do have all the previous versions archived so I can go back through and see when it changed, but I'm just being lazy

                  Paul..

                  Comment


                    #10
                    Paul,

                    I am also getting this error lately - since a week or so. It seems when I go out, at the first notice, the error occurs. At second notice, a correct reverse geocode is performed. The next is another error - and so on.

                    Here am at 3.0.1.90 as well. My log filtered on errors for the past few days:

                    Code:
                    sep-26 18:38:52	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat xx.2011169791708 Lon:x.95374050550717
                    sep-26 17:34:48	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.2227847436929 Lon:x.96325245686431
                    sep-26 17:16:18	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.2010202100987 Lon:x.95394418575424
                    sep-26 16:21:27	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.2011669857408 Lon:x.95380168685144
                    sep-26 15:54:07	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.2011994703691 Lon:x.95371608965726
                    sep-26 15:26:47	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.1936478832663 Lon:x.94648806579538
                    sep-26 15:17:29	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.1908692285446 Lon:x.94479172237196
                    sep-26 14:31:56	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.1851465863707 Lon:x.94303509855791
                    sep-26 14:22:49	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.1850942168871 Lon:x.94136353582697
                    sep-26 14:13:42	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.1870607507599 Lon:5.94196392865698
                    sep-25 22:02:25	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2927] Lat: xx.2112147348892 Lon:x.93149304136964
                    sep-25 21:25:36	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2927] Lat: xx.2231508652235 Lon:x.93946754932957
                    sep-25 15:16:12	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.2011419444113 Lon:x.95382644636287
                    sep-25 14:57:59	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: xx.2129842034096 Lon:x.94175656326668
                    sep-23 21:27:40	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2927] Lat: xx.2010696214179 Lon:x.95394921489614
                    sep-23 19:29:08	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2927] Lat: xx.1775053255746 Lon:x.9098278824295
                    Wim
                    Last edited by w.vuyk; September 27, 2017, 05:37 AM. Reason: X
                    -- Wim

                    Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

                    1210 devices/features ---- 392 events ----- 40 scripts

                    Comment


                      #11
                      Originally posted by w.vuyk View Post
                      Paul,

                      I am also getting this error lately - since a week or so. It seems when I go out, at the first notice, the error occurs. At second notice, a correct reverse geocode is performed. The next is another error - and so on.

                      Here am at 3.0.1.90 as well. My log filtered on errors for the past few days:

                      Code:
                      sep-26 18:38:52	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.2011169791708 Lon:5.95374050550717
                      sep-26 17:34:48	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.2227847436929 Lon:5.96325245686431
                      sep-26 17:16:18	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.2010202100987 Lon:5.95394418575424
                      sep-26 16:21:27	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.2011669857408 Lon:5.95380168685144
                      sep-26 15:54:07	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.2011994703691 Lon:5.95371608965726
                      sep-26 15:26:47	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.1936478832663 Lon:5.94648806579538
                      sep-26 15:17:29	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.1908692285446 Lon:5.94479172237196
                      sep-26 14:31:56	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.1851465863707 Lon:5.94303509855791
                      sep-26 14:22:49	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.1850942168871 Lon:5.94136353582697
                      sep-26 14:13:42	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.1870607507599 Lon:5.94196392865698
                      sep-25 22:02:25	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2927] Lat: 52.2112147348892 Lon:5.93149304136964
                      sep-25 21:25:36	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2927] Lat: 52.2231508652235 Lon:5.93946754932957
                      sep-25 15:16:12	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.2011419444113 Lon:5.95382644636287
                      sep-25 14:57:59	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2943] Lat: 52.2129842034096 Lon:5.94175656326668
                      sep-23 21:27:40	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2927] Lat: 52.2010696214179 Lon:5.95394921489614
                      sep-23 19:29:08	 	PHLocation Error	(UpdateUserDevice) Error getting reverse geocode for [2927] Lat: 52.1775053255746 Lon:5.9098278824295
                      Wim
                      Super, thank's Wim.

                      About to go to bed so I'll take a look at this tomorrow.

                      Do you have a Google API key specified in the plug-in?

                      Paul..

                      Comment


                        #12
                        Paul,

                        I guess not, as I did not find where to configure it. But I doubt I am pushing the limits as I have not really been out in the past days.

                        Thanks,

                        Wim
                        -- Wim

                        Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

                        1210 devices/features ---- 392 events ----- 40 scripts

                        Comment


                          #13
                          Ok,

                          Found the location. Added an API key and will see in the next few days if something changes.

                          Wim
                          -- Wim

                          Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

                          1210 devices/features ---- 392 events ----- 40 scripts

                          Comment


                            #14
                            I got a ton of these errors this morning as well. I was traveling at the time so no big surprise if I went over the limit. Then they automagically went away. I didn't get a single one later in the day or during my Looooooooonnngggggg drive home. This isn't the first time this has happened. It always seems to just disappear after a few hours.

                            No clue if I'm using a Google api key. My setup of this plugin is so lost in antiquity that all I remember is I used FollowMee at first. Everything else must have gotten cleared out of the attic during spring cleaning or intentionally been forgotten so as to not get squirrely from keeping too much jargon in mind.
                            Originally posted by rprade
                            There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                            Comment


                              #15
                              Originally posted by sooty View Post
                              Can I ask what version of the plug-in you are running?

                              Reason is that I can't find that error message in the latest code.

                              Paul..
                              Paul,

                              Running 3.0.1.90
                              Michael

                              Comment

                              Working...
                              X