core icon indicating copy to clipboard operation
core copied to clipboard

cannot change location using service device_tracker.see

Open StCyr opened this issue 1 year ago • 5 comments

The problem

I've created a simple automation:

alias: Change Emilie location
description: ""
trigger: []
condition: []
action:
  - service: device_tracker.see
    data:
      location_name: not_home
      dev_id: iphone_de_emilie
mode: single

If I understand the documentation (https://www.home-assistant.io/integrations/device_tracker/#device_trackersee-service) correctly, this should set the value of the device_tracker.iphone_de_emilie entity to not_home. However it doesn't and there's no error in the automation traces

What version of Home Assistant Core has the issue?

core-2023.10.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

device_tracker

Link to integration documentation on our website

https://www.home-assistant.io/integrations/device_tracker/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

StCyr avatar Oct 21 '23 09:10 StCyr

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (device_tracker) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of device_tracker can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign device_tracker Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


device_tracker documentation device_tracker source (message by IssueLinks)

home-assistant[bot] avatar Oct 21 '23 09:10 home-assistant[bot]

hoho, I'm now seeing this in the log:

2023-10-21 11:39:55.264 ERROR (MainThread) [homeassistant.components.device_tracker] The see service is not supported for this entity device_tracker.iphone_de_emilie

That explains why the value isn't changed... but why isn't the see service supported for this entity? And, why doesn't the automation traces show this error?

StCyr avatar Oct 21 '23 09:10 StCyr

hi

same for update location

alias: Detection Wifi 
description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.s21_wifi_connection
    to: My_Wifi
    enabled: true
condition: []
action:
  - service: device_tracker.see
    data:
      dev_id: s21
      location_name: not_home
mode: single

Error in LOG :

The see service is not supported for this entity device_tracker.s21

LiloBzH avatar Nov 09 '23 20:11 LiloBzH

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

up . not solved

LiloBzH avatar Feb 07 '24 21:02 LiloBzH

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

still not solved

StCyr avatar May 09 '24 08:05 StCyr

+1

LiloBzH avatar May 09 '24 08:05 LiloBzH

The device_tracker.see service is only for legacy device tracker devices. Device tracker entities that are part of an integration showing up in the devices and services page don't support this service.

Since this is a legacy service all parts of it doesn't behave according to modern practices in regards to error tracking.

MartinHjelmare avatar May 09 '24 11:05 MartinHjelmare