CPDLC Unable to notify ATC

[MemesBananza]

Simulator Version

2020

Aircraft Version

Stable

Build info

{
    "built": "2024-11-09T16:32:29+00:00",
    "ref": "refs/tags/v0.12.3",
    "sha": "7c0bb7fee6051b07edd3435d923b7acf1cec2945",
    "actor": "FoxtrotSierra6829",
    "event_name": "manual",
    "pretty_release_name": "stable/v0.12.3",
    "version": "a32nx-v0.12.3-rel.7c0bb7f"
}

Describe the bug

Unable to notify ATC on CPDLC:

What happens:

Active ATC station (Indicated at https://www.hoppie.nl/acars/system/online.html and in ATIS of station!) is written into 4 orange boxes in the "NOTIFY" section of CPDLC (ex. EDYY), a few seconds pass, I get the message "ATC NOT AVALIBLE" (Or similar, I can't remember the exact message.). I have put in IVAO in my ATC/ATIS section, my ACARS on is set to "IVAO" on Hoppie's page.

Expected behavior

CPDLC should let my type in ATC callsign and let my send a log-on request.

Steps to reproduce

1. Set "IVAO" on FlyPad and Hoppie ACARS
2. Go online and encounter active ATC station on https://www.hoppie.nl/acars/system/online.html . (Radio contact was established)
3. Type the active ATC station into the "NOTIFICATION" page and click the softkey where the orange boxes are. (ex.: EDYY)
4. Message "ATC NOT AVALIBLE" spits out.

References (optional)

No response

Additional info (optional)

I can see 2 versions of my exact callsign on https://www.hoppie.nl/acars/system/online.html . One on network "IVAO" (Supposed to be IVAO) and one on "None". The aircraft could be logging on to this "None" network when IVAO is selected.

Discord Username (optional)

Some_One7409

[kdev]

I also have this bug. Followed the docs and the steps you provided.

[MemesBananza]

Tried to send a Log-On request on VATSIM. Didnt work. So I tried it with https://fsm.vsrsoftware.com/ and there it worked. But, what's interesting, is that the aircraft also receives messages that get sent to my Hoppie-ID. So, it's an issue with the aircraft itself.

Now because I really want to solve this problem, I dug deep and found the potential issue.

When I send a request to https://api.flybywiresim.com/api/#/HOPPIE/ with payload

curl -X POST "https://api.flybywiresim.com/api/v1/hoppie" -H "accept: application/json" -H "Content-Type: application/json" -d "{\"logon\":\"{MY HOPPIE LOGON CODE}\",\"from\":\"{MY ACTUAL CALLSIGN}\",\"to\":\"EDGK\",\"type\":\"poll\",\"packet\":\"/data2/1//N/REQUEST LOGON SERVUS\"}"

I get the response:

{"response":"ok"}

But when I look at the Hoppie message log, nothing actually got sent.

So it can, if the aircraft uses it, be a low-level issue with the API itself.