Inara not getting updates

[Tallyrald]

What's Wrong

Expected

Inara data to be updated.

Observed

Inara is receiving some kind of data, because the API events log (on Inara) is showing successful events (no errors or warnings), but the relevant star systems and markets are not updated when I try to actually use the website. I haven't tested other types of data.

Steps to reproduce

1. Start EDDI
2. Have Inara API key set
3. Play the game
4. Jump to a system or go to a station and open the commodity market
5. Open the relevant page on Inara and observe the last updated datetime

Configuration

• Version
  • EDDI Version: 4.1.1
  • VoiceAttack Version: -
• Localization [if applicable]
  • EDDI's language: English
  • Voice: -

My Investigation

Investigation Notes

Version 4.0.4 updated Inara almost instantly. Now basically nothing on the site gets refreshed. When I press the 'Import game data' button on Inara in my profile, partial updates are reflected, but this isn't how it used to be - nor how it should be, since that button is not for real-time data fetch.

EDDI Logs

Log

2025-03-22T09:29:43.1827879Z [Info] StarSystemSqLiteRepository:CreateOrUpdateDatabase Starsystem repository schema is version 3
2025-03-22T09:29:43.1968208Z [Info] EDDI:.ctor EDDI 4.1.1 starting
2025-03-22T09:29:43.2028834Z [Info] CargoMonitor:.ctor Initialized Cargo monitor
2025-03-22T09:29:43.2038809Z [Info] EDSMResponder:.ctor Initialized EDSM Responder
2025-03-22T09:29:43.2060411Z [Info] CrimeMonitor:initializeCrimeMonitor Initialized Crime monitor
2025-03-22T09:29:43.2225315Z [Info] MaterialMonitor:.ctor Initialized Material monitor
2025-03-22T09:29:43.2256107Z [Info] MissionMonitor:initializeMissionMonitor Initialized Mission monitor
2025-03-22T09:29:43.2869216Z [Info] VoiceAttackResponder:.ctor Started VoiceAttack responder
2025-03-22T09:29:45.9438542Z [Info] NavigationMonitor:.ctor Initialized Navigation monitor
2025-03-22T09:29:45.9469282Z [Info] ShipMonitor:.ctor Initialized Ship Monitor
2025-03-22T09:29:45.9474325Z [Info] StatusMonitor:.ctor Initialized Status monitor
2025-03-22T09:29:45.9489460Z [Info] EDDI:.ctor EDDI 4.1.1 initialised
2025-03-22T09:29:45.9504559Z [Info] EDDI:Start EDDP monitor is disabled; not starting
2025-03-22T09:29:45.9504559Z [Info] EDDI:Start Galnet monitor is disabled; not starting
2025-03-22T09:29:45.9504559Z [Info] EDDI:Start Starting keepalive for Mission monitor
2025-03-22T09:29:45.9514598Z [Info] EDDI:Start Starting keepalive for Status monitor
2025-03-22T09:29:45.9514598Z [Info] EDDI:Start Started EDDN Responder
2025-03-22T09:29:45.9504559Z [Info] EDDI:Start Starting keepalive for Journal monitor
2025-03-22T09:29:45.9514598Z [Info] EDDI:keepAlive Starting Journal monitor (0)
2025-03-22T09:29:45.9551484Z [Info] EDDI:keepAlive Starting Mission monitor (0)
2025-03-22T09:29:45.9566578Z [Info] EDDI:Start Started EDSM Responder
2025-03-22T09:29:45.9566578Z [Info] DataProviderService:syncFromStarMapService Syncing all flight logs from EDSM
2025-03-22T09:29:45.9514598Z [Info] EDDI:keepAlive Starting Status monitor (0)
2025-03-22T09:29:45.9581658Z [Info] EDDI:Start Started Inara Responder
2025-03-22T09:29:45.9581658Z [Info] SpeechResponder:Start Initialized Speech Responder
2025-03-22T09:29:45.9581658Z [Info] EDDI:Start Started Speech Responder
2025-03-22T09:29:45.9581658Z [Info] InaraResponder:Start Initialized Inara Responder
2025-03-22T09:29:46.0855485Z [Info] JournalMonitor:ParseJournalEntry GameVersion: 4.1.0.200, Build r311981/r0.
2025-03-22T09:29:46.1141478Z [Info] JournalMonitor:ParseJournalEntry Active expansions... Horizons: True, Odyssey: True.
2025-03-22T09:29:46.1738090Z [Info] ResourceBasedLocalizedEDName:FromEDName Unknown ED name Unoccupied in resource EddiDataDefinitions.Properties.PowerplayState
2025-03-22T09:29:47.5437045Z [Info] EDDI:.ctor EDDI access to the Frontier API is enabled.
2025-03-22T09:33:58.2012128Z [Info] EDDI:eventLocation Location StarSystem: Col 285 Sector AO-L b23-2
2025-03-22T09:33:58.2012128Z [Info] EDDI:eventLocation Vehicle mode is Ship
2025-03-22T09:33:58.2257085Z [Info] EDDI:eventJumped Jumped to Col 285 Sector CO-L b23-0
2025-03-22T09:33:58.2936270Z [Info] EDDI:eventJumped Jumped to Col 285 Sector SJ-Q d5-85
2025-03-22T09:33:58.3307280Z [Info] EDDI:eventJumped Jumped to Aknandan
2025-03-22T09:33:58.3902260Z [Info] EDDI:eventJumped Jumped to Cuachini
2025-03-22T09:33:58.4321897Z [Info] EDDI:eventJumped Jumped to Col 285 Sector KT-G c11-11
2025-03-22T09:33:58.4660155Z [Info] EDDI:eventJumped Jumped to Col 285 Sector OZ-E c12-15
2025-03-22T09:33:58.4941061Z [Info] EDDI:eventJumped Jumped to Col 285 Sector AO-L b23-2
2025-03-22T09:33:58.5575105Z [Info] EDDI:eventJumped Jumped to Col 285 Sector CO-L b23-2
2025-03-22T09:33:58.5962408Z [Info] EDDI:eventJumped Jumped to 30 Serpentis
2025-03-22T09:33:58.6576113Z [Info] EDDI:eventJumped Jumped to Col 285 Sector WP-O d6-86
2025-03-22T09:33:58.7187140Z [Info] EDDI:eventJumped Jumped to Col 285 Sector AO-L b23-2
2025-03-22T09:33:58.7581889Z [Info] EDDI:eventJumped Jumped to Col 285 Sector CO-L b23-2
2025-03-22T09:33:58.7989192Z [Info] EDDI:eventJumped Jumped to 30 Serpentis
2025-03-22T09:33:58.8567163Z [Info] EDDI:eventJumped Jumped to Col 285 Sector WP-O d6-86
2025-03-22T09:33:58.8977314Z [Info] EDDI:eventJumped Jumped to Col 285 Sector AO-L b23-2
2025-03-22T09:33:58.9340086Z [Info] EDDI:eventJumped Jumped to Col 285 Sector CO-L b23-2
2025-03-22T09:33:58.9877887Z [Info] EDDI:eventJumped Jumped to 30 Serpentis
2025-03-22T09:33:59.0316368Z [Info] EDDI:eventJumped Jumped to Col 285 Sector WP-O d6-86
2025-03-22T09:33:59.0660929Z [Info] EDDI:eventJumped Jumped to Col 285 Sector AO-L b23-2
2025-03-22T09:33:59.1075516Z [Info] EDDI:eventJumped Jumped to Col 285 Sector CO-L b23-2
2025-03-22T09:33:59.1378643Z [Info] EDDI:eventJumped Jumped to 30 Serpentis
2025-03-22T09:33:59.1866040Z [Info] EDDI:eventJumped Jumped to Col 285 Sector WP-O d6-86
2025-03-22T09:33:59.2215741Z [Info] EDDI:eventJumped Jumped to Col 285 Sector AO-L b23-2
2025-03-22T09:33:59.2584421Z [Info] EDDI:eventJumped Jumped to Col 285 Sector CO-L b23-2
2025-03-22T09:33:59.2994163Z [Info] EDDI:eventJumped Jumped to 30 Serpentis
2025-03-22T09:33:59.3481862Z [Info] EDDI:eventJumped Jumped to Col 285 Sector WP-O d6-86
2025-03-22T09:33:59.3987057Z [Info] EDDI:eventJumped Jumped to Col 285 Sector AO-L b23-2
2025-03-22T09:33:59.4554728Z [Info] EDDI:eventJumped Jumped to Col 285 Sector CO-L b23-2
2025-03-22T09:33:59.4937560Z [Info] EDDI:eventJumped Jumped to 30 Serpentis
2025-03-22T09:33:59.5628148Z [Info] EDDI:eventJumped Jumped to Col 285 Sector WP-O d6-86
2025-03-22T09:33:59.5996996Z [Info] EDDI:eventJumped Jumped to Col 285 Sector AO-L b23-2
2025-03-22T09:34:58.3977026Z [Info] EDDI:eventJumped Jumped to Col 285 Sector CO-L b23-2
2025-03-22T09:35:48.9281889Z [Info] EDDI:eventJumped Jumped to 30 Serpentis

[Tkael]

The Inara Responder does not directly update station commodity data on Inara. There is no API endpoint for submitting that data directly to Inara. (see https://inara.cz/elite/inara-api-docs/).

The Import game data button on Inara pulls information from the Frontier API and has nothing to do with EDDI. As you noted, this button is also not intended to provide real-time data.

Commodity data must be gathered either from the Frontier API or (if you open the commodities page) from market.json and transmitted via EDDN. Inara listens to messages transmitted via EDDN and uses that information to update its station commodity data.

There are a few different possibilities:

1. The message wasn't transmitted to EDDN correctly (this would normally be signaled via an exception that we'd see in EDDI's log)
2. The message was transmitted to EDDN correctly but wasn't re-transmitted to Inara immediately (EDDN does some processing on the message and re-transmission to Inara is not instant)
3. The message was not re-transmitted from EDDN to Inara (this can occur if EDDN identifies the message as a duplicate of another message or there is some other problem with the message)
4. Inara received the message but there was some delay in updating the forward facing website.

If I had information about the specific station and a timestamp then I might be able to track down a record and confirm whether EDDN received / re-transmitted the message.

Alternately, you could look at Spansh or a similar website to confirm whether Spansh received the same message from EDDN.

[Tallyrald]

Hi! Thank you for a great summary! Unfortunately I'm not entirely sure how to help you identify this issue further.
I tried to do some digging and I made a jump. Found this in the verbose logs. Is this what you're looking for?

2025-03-23T14:29:03.5305095Z [Debug] EDDNResponder:Handle Received event

Event details

{
  "timestamp": "2025-03-23T14:29:04Z",
  "event": "FSDJump",
  "Taxi": false,
  "Multicrew": false,
  "StarSystem": "30 Serpentis",
  "SystemAddress": 48555361468,
  "StarPos": [-10.96875, 105.0, 141.0625],
  "SystemAllegiance": "Independent",
  "SystemEconomy": "$economy_Refinery;",
  "SystemEconomy_Localised": "Refinery",
  "SystemSecondEconomy": "$economy_Extraction;",
  "SystemSecondEconomy_Localised": "Extraction",
  "SystemGovernment": "$government_Patronage;",
  "SystemGovernment_Localised": "Patronage",
  "SystemSecurity": "$SYSTEM_SECURITY_low;",
  "SystemSecurity_Localised": "Low Security",
  "Population": 99379,
  "Body": "30 Serpentis",
  "BodyID": 0,
  "BodyType": "Star",
  "ControllingPower": "Nakato Kaine",
  "Powers": ["Nakato Kaine"],
  "PowerplayState": "Exploited",
  "PowerplayStateControlProgress": 0.177241,
  "PowerplayStateReinforcement": 35,
  "PowerplayStateUndermining": 0,
  "JumpDist": 11.826,
  "FuelUsed": 0.623863,
  "FuelLevel": 60.159878,
  "Factions": [
    {
      "Name": "30 Serpentis  Protectorate",
      "FactionState": "None",
      "Government": "Patronage",
      "Influence": 0.031936,
      "Allegiance": "Independent",
      "Happiness": "$Faction_HappinessBand2;",
      "Happiness_Localised": "Happy",
      "MyReputation": 0.0
    },
    {
      "Name": "30 Serpentis Industries",
      "FactionState": "None",
      "Government": "Corporate",
      "Influence": 0.07485,
      "Allegiance": "Independent",
      "Happiness": "$Faction_HappinessBand2;",
      "Happiness_Localised": "Happy",
      "MyReputation": 0.0,
      "RecoveringStates": [{ "State": "PublicHoliday", "Trend": 0 }]
    },
    {
      "Name": "30 Serpentis Coordinated",
      "FactionState": "None",
      "Government": "Cooperative",
      "Influence": 0.027944,
      "Allegiance": "Independent",
      "Happiness": "$Faction_HappinessBand2;",
      "Happiness_Localised": "Happy",
      "MyReputation": 0.0
    },
    {
      "Name": "The Explorer's Consortium",
      "FactionState": "None",
      "Government": "Corporate",
      "Influence": 0.052894,
      "Allegiance": "Independent",
      "Happiness": "$Faction_HappinessBand2;",
      "Happiness_Localised": "Happy",
      "MyReputation": 0.0
    },
    {
      "Name": "LGC - Cartographers's Guild",
      "FactionState": "None",
      "Government": "Patronage",
      "Influence": 0.812375,
      "Allegiance": "Independent",
      "Happiness": "$Faction_HappinessBand2;",
      "Happiness_Localised": "Happy",
      "MyReputation": 1.41155,
      "PendingStates": [{ "State": "Expansion", "Trend": 0 }],
      "RecoveringStates": [{ "State": "PirateAttack", "Trend": 0 }]
    }
  ],
  "SystemFaction": { "Name": "LGC - Cartographers's Guild" }
}

And yet about 10 minutes later this is what I see (I am GMT+1):
Spansh:

Inara:

System/faction data is 2 hours old (recorded by someone else). The same jump on EDDI 4.0.4 resulted in basically an instant update.

[Tkael]

Ah. I was able to confirm that EDDN had not received the message. I think I also found the source of the problem - the EDDN responder was skipping over an important piece of the code during its startup. o7