Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛call_name is empty in message sensor #227

Closed
2 tasks done
Enkil666 opened this issue Jun 27, 2023 · 8 comments
Closed
2 tasks done

🐛call_name is empty in message sensor #227

Enkil666 opened this issue Jun 27, 2023 · 8 comments

Comments

@Enkil666
Copy link

What version of Integration has the issue?

V2.8.2

System Health details

Version core-2023.5.4
Installation Type Home Assistant Supervised
Development false
Supervisor true
Docker true
User root
Virtual Environment false
Python Version 3.10.11
Operating System Family Linux
Operating System Version 5.15.84-v8+
CPU Architecture aarch64
Timezone Europe/Stockholm
Configuration Directory /config

Checklist

  • I have enabled debug logging for my installation.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).

Describe the issue

I've been playing around with the messages for awhile now and I have noticed that the watch message sensor doesn't show anything under "call_name" (data.call_name) when displaying the CALL_LOG.

data.call_time is however working.

In the Xplora app, it shows correctly who the call was made to.

See image from Developer Tools:
Screenshot 2023-06-27 at 15 17 51

Reproduction steps

  1. Display the watch message sensor on a Markdown card
  2. See the call log
  3. Call log displays sender, receiver, call time but not call_name
    ...

Debug logs

Can't see any in the logs regarding this.
@github-actions
Copy link
Contributor

👋 @henkehedin, it is checked whether there is a bug. Please have some patience.
This action was performed automatically.

@github-actions github-actions bot added check for Bug it is checked whether there is an Bug wait in examination labels Jun 27, 2023
@Ludy87
Copy link
Owner

Ludy87 commented Jun 28, 2023

{
  "id":"***",
  "msgId":"***",
  "readFlag":2,
  "sender":{
	"id":"***",
	"userId":"__w__360_***",
	"name":"Lorry",
	"phoneNumber":"***"
  },
  "receiver":{
	"id":"***",
	"userId":"__g__49_***",
	"name":"Enrico",  <--- Try 
	"phoneNumber":"***"
  },
  "data":{
	"tm":1687934793926,
	"sender_name":"Lorry",
	"text":"",
	"Text":"None",
	"battery":"None",
	"poi":"None",
	"city":"None",
	"address":"None",
	"province":"None",
	"locate_type":"None",
	"emoticon_id":"UNKNOWN__",
	"emoji_id":"UNKNOWN__",
	"call_name":"Papa",
	"call_time":1687934775,
	"call_type":1,
	"lat":"None",
	"lng":"None",
	"radius":"None",
	"delete_flag":0
  },
  "create":1687934794,
  "type":"CALL_LOG"
}

Maybe the phone book between the clock and the Xplora database is not in sync, try the receiver.name variable.

Screenshot 2023-06-28 085951

@Ludy87 Ludy87 added Bug: False Alarm no Bug - False Alarm and removed check for Bug it is checked whether there is an Bug labels Jun 28, 2023
@Enkil666
Copy link
Author

Thanks Ludy87. Hm, receiver.name just gives me my name - and not the person the call was made to. If the phone book between the clock and the Xplora database is not in sync, how does one solve that I wonder?

My output (from your Markdown template) which displays nothing at "Angerufen wurde":

Screenshot 2023-06-28 at 09 30 39

But at least it's good to know that it's suppose to work :)

@Ludy87
Copy link
Owner

Ludy87 commented Jun 28, 2023

Yes you are right, the receivername is the app user.

I tried it now with a woman calling her, and her name is displayed at call_name.

So I assume the problem is with Xplora.

@Enkil666
Copy link
Author

Got it. I'll try to reinstall the integration and see if that solves anything.

Thanks!

@Ludy87 Ludy87 removed wait in examination Bug labels Jun 28, 2023
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 29, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 6, 2023

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2023
@Ludy87
Copy link
Owner

Ludy87 commented Dec 3, 2023

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@Ludy87 Ludy87 added the outdated label Dec 3, 2023
Repository owner locked as resolved and limited conversation to collaborators Dec 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants