Announcement

Collapse
No announcement yet.

Egigeozone not triggering tasker, can I trigger MYHS direct ?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Egigeozone not triggering tasker, can I trigger MYHS direct ?

    I have moved phones, from a Samsung S6 with Android 5.1.1. to a Huawei P20 Pro with 8.1, I have exported my tasker and egi settings to the new phone. Tasker is working fine, it can control HS3 as it did on the old phone. Egi has all settings (as far as I can see by doing a comparison) from the old phone. Geofences are there, and change depending on my location. The appropriate tasker tasks are in the egi settings, but unlike the old phone, for whatever reason, egi does not want to trigger the tasker tasks. Again, I have checked everything. I will attach a egi log just in case someone has an idea why it has decided not to trigger... I have enables external access in tasker
    But maybe there is a way to trigger my virtual switches in MyHS from egi without going through tasker ?

    2018-10-08 19:53:51,435 - [ERROR::de.egi.geofence.geozone.Worker::de.egi.geofence.geozo ne.Worker] - 2: AccessBlocked: external access is blocked in the user preferences.
    2018-10-08 21:03:15,104 - [ERROR::de.egi.geofence.geozone.StartupReceiver::de.egi.geofe nce.geozone.StartupReceiver] - Logger set!
    2018-10-08 21:03:15,132 - [ERROR::de.egi.geofence.geozone.StartupReceiver::de.egi.geofe nce.geozone.StartupReceiver] - EgiGeoZone gestartet
    2018-10-08 21:03:15,135 - [ERROR::de.egi.geofence.geozone.StartupReceiver::de.egi.geofe nce.geozone.StartupReceiver] - call registerGeofencesAfterRebootOrUpdate: android.intent.action.BOOT_COMPLETED
    2018-10-08 21:03:15,136 - [ERROR::de.egi.geofence.geozone.StartupReceiver::de.egi.geofe nce.geozone.StartupReceiver] - in registerGeofencesAfterRebootOrUpdate
    2018-10-08 21:03:15,160 - [ERROR::de.egi.geofence.geozone.StartupReceiver::de.egi.geofe nce.geozone.StartupReceiver] - registerPathsenseAfterRebootOrUpdate
    2018-10-08 21:03:49,514 - [ERROR::de.egi.geofence.geozone.geofence.PathsenseGeofenceEve ntReceiverService::de.egi.geofence.geozone.geofence.Pathsens eGeofenceEventReceiverService] - Do not call events after reboot or at update
    2018-10-08 21:03:49,516 - [ERROR::de.egi.geofence.geozone.geofence.PathsenseGeofenceEve ntReceiverService::de.egi.geofence.geozone.geofence.Pathsens eGeofenceEventReceiverService] - Reboot: true
    2018-10-09 06:15:19,078 - [ERROR::de.egi.geofence.geozone.Worker::de.egi.geofence.geozo ne.Worker] - null: AccessBlocked: external access is blocked in the user preferences.
    2018-10-09 07:23:43,297 - [ERROR::de.egi.geofence.geozone.Worker::de.egi.geofence.geozo ne.Worker] - 1: AccessBlocked: external access is blocked in the user preferences.
    2018-10-09 17:15:54,670 - [ERROR::de.egi.geofence.geozone.Worker::de.egi.geofence.geozo ne.Worker] - 1: AccessBlocked: external access is blocked in the user preferences.
    2018-10-09 19:05:36,582 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - ******************************************
    2018-10-09 19:05:36,587 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - EgiGeoZone: 2.7.7
    2018-10-09 19:05:36,588 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Device name: HUAWEI CLT-L09
    2018-10-09 19:05:36,589 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Device brand: HUAWEI
    2018-10-09 19:05:36,590 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Android version: 8.1.0 (REL)
    2018-10-09 19:05:36,591 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - ******************************************
    2018-10-10 06:15:41,080 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - ******************************************
    2018-10-10 06:15:41,088 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - EgiGeoZone: 2.7.7
    2018-10-10 06:15:41,090 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Device name: HUAWEI CLT-L09
    2018-10-10 06:15:41,091 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Device brand: HUAWEI
    2018-10-10 06:15:41,091 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Android version: 8.1.0 (REL)
    2018-10-10 06:15:41,092 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - ******************************************
    2018-10-10 10:42:46,421 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - ******************************************
    2018-10-10 10:42:46,425 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - EgiGeoZone: 2.7.7
    2018-10-10 10:42:46,427 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Device name: HUAWEI CLT-L09
    2018-10-10 10:42:46,428 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Device brand: HUAWEI
    2018-10-10 10:42:46,428 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - Android version: 8.1.0 (REL)
    2018-10-10 10:42:46,429 - [ERROR::de.egi.geofence.geozone.Settings::de.egi.geofence.geo zone.Settings] - ******************************************
    Last edited by mikee123; October 10, 2018, 05:25 AM.
    Tags: None
    #2
    Have you tried the Auto Location plugin? Part of the auto apps suite. It's paid (~$3) but you can trial it for a week. I found it to be a somewhat reliable replacement to Egi after the Egi author gave up on development.

    Comment

      #3
      I used to use it, I had the paid version, but abandoned it for egi a few years ago. This is my fallback option, in case I cannot sort this out. I have a feeling its tasker rather than egi. I have created a tasker device for my phone (as I have for all my other devices) but when I try to send anything to my phone, TTS or other commands, its not reacting. I have tried turning external access off and on again in tasker, but no joy. So I think that is where the problem might be. Then autolocation would not work either...

      Comment

        #4
        Originally posted by mikee123 View Post
        I used to use it, I had the paid version, but abandoned it for egi a few years ago. This is my fallback option, in case I cannot sort this out. I have a feeling its tasker rather than egi. I have created a tasker device for my phone (as I have for all my other devices) but when I try to send anything to my phone, TTS or other commands, its not reacting. I have tried turning external access off and on again in tasker, but no joy. So I think that is where the problem might be. Then autolocation would not work either...
        Same thing happened to me. After months of tinkering I just gave up on Tasker integration with HS entirely. It's sad.
        Originally posted by rprade
        There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

        Comment

          #5
          Originally posted by S-F View Post

          Same thing happened to me. After months of tinkering I just gave up on Tasker integration with HS entirely. It's sad.
          It worked fine for me for 3 years. Now after moving phones, major issues. Pretty sure now its not egi, so at least I can rule that out. When I have time, I will try uninstalling tasker and start again... I took the HS3 PI off tasker yesterday, and reinstalled and linked it to HS3. Still no joy. Quite frustrating.

          Comment

            #6
            Ok that worked. I read somewhere that tasker doesnt like installing Plugins before creating a task first. Changing phones, it installed tasker with the HS3 PI, then I applied my backup. What I did now is uninstall tasker completely. Fresh install. Created a dummy profile and task. Installed HS3 PI. Linked the PI. Restored my backup. Bingo. Its working.

            Comment

              #7
              Just when I thought I had it. I didnt. HS3 sends commands to tasker via the HS3 device. Tasker can control HS3. But egi still does not trigger Tasker. External control is enabled and the egi setup identical to the working phone. I dont get it.

              Comment

                #8
                It is working now. I reinstalled tasker. then reinstalled egi. Then I renamed the tasks egi tiggers. Now its working. The only issue remaining, triggers are extremely slow compared to my old phone, with the same fences, it does take a long time after entering/exiting a fence before it triggers.I have changed the location method to high accuracy, which has helped a little. But its still not great...

                Comment

                  #9
                  Originally posted by mikee123 View Post
                  It is working now. I reinstalled tasker. then reinstalled egi. Then I renamed the tasks egi tiggers. Now its working. The only issue remaining, triggers are extremely slow compared to my old phone, with the same fences, it does take a long time after entering/exiting a fence before it triggers.I have changed the location method to high accuracy, which has helped a little. But its still not great...
                  Google has come up with the idea that Geofencing from Android 8 (Oreo) only reports entering / leaving every few minutes.
                  See also:
                  https://developer.android.com/traini...nceTransitions Look at the blue box and at the bottom of the page "Alerts can be late".
                  Note: On Android 8.0 (API level 26) and higher, if an app is running in the background while monitoring a geofence, then the device responds to geofencing events every couple of minutes. To learn how to adapt your app to these response limits, see Background Location Limits.
                  Alerts can be late. The geofence service doesn't continuously query for location, so expect some latency when receiving alerts. Usually the latency is less than 2 minutes, even less when the device has been moving. If Background Location Limits are in effect, the latency is about 2-3 minutes on average. If the device has been stationary for a significant period of time, the latency may increase (up to 6 minutes).
                  See also the Geofencing point here: https://developer.android.com/about/...on-limits#apis

                  The average responsiveness for a geofencing event is every couple of minutes or so.
                  Now you can understand one of the reasons, why I gave up the app. Maybe the PathSense is an option for you.

                  Edit: I am the EgiGeoZone developer

                  Comment

                    #10
                    Pathsense is not an option for me. I had a look, as far as I can tell, its only an api, so I would need to program something to make it work. Way way beyond my capabilities unfortunately. I hope Paul can make something out of this, he is a very capable chap. It is a shame Android has been going this way, if it wasn't for my hate of apple and all its limitations etc, I would consider going back. Geofencing for my wifes phone is ok ish on an older Android version, but mine is pretty bad. A few minutes after I arrived home I get a message Mike home... and the lights come on...

                    Comment

                      #11
                      Originally posted by mikee123 View Post
                      Pathsense is not an option for me. I had a look, as far as I can tell, its only an api, so I would need to program something to make it work. Way way beyond my capabilities unfortunately...
                      With Pathsense, I meant the setting in the EgiGeoZone app, where I have already implemented that API. There you can switch from Google to Pathsense.

                      Comment

                        #12
                        Ah yes I am using Pathsense in Egi, I found it to be better than google.

                        Comment

                        Previous template Next
                        Working...
                        X