Login

Recent searches

No recent searches

Search options

Only available when logged in.
social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

488
active users

social.coop: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#nodered

5 posts5 participants0 posts today
Public
brett
Recently traveled interstate so my partner could see a concert and in doing so discovered that a band I love had come to Australia a couple of years ago and I had no idea. So this morning's #project was ensuring that never happens again using #nodered

Once a week, it'll pull Last.fm's events page for my city and a giant radius around Melbourne/Sydney/Canberra, then try to match events against all of the artists in my music server. Any new matches will be posted to fedi with my user tagged so I get a notification.
Two fediverse posts, of the format "Found an upcoming event for (band), details here: (last.fm link)" The two bands are The Wombats and Bloc Party.
Continued thread
Public
Abishek Muthian

The issue was with nr-gotify node, it crashed the NodeRED when it couldn't reach my gotify server. Now I check if the gotify server is reachable before sending the message. Also added catch all node and used JSONata for first time to concat timestamp with the message.

Looking forward to use more of the JSONata to avoid writing JavaScript in the NodeRED, JS is weirder than usual here.

NodeRED flow to restart modem when Internet is down. Lot of different colored boxes in a flowchart type setup.
#HomeAssistant#nodered#gotify
Public
Beko Pharm

Parsing the Elite Dangerous Journal

I gave in and changed my event forwarding method in node-red for the Elite Dangerous Journal. This file is updated on various in-game events but in a way that makes it difficult to get new events only since last update. Another problem is that it’s not really a valid JSON file because it has one JSON per line but it’s not a valid JSON array. This is why it has to be parsed line by line and mashed together by event type (name) again to get the latest data for each event type per dump. Each event has it’s own timestamp by set by the game. The latest timestamp is now saved on the special flow const so node-red keeps the value in the “global” memory of the current flow:

msg.payload.event = "Journal";let newJournalTimestamp = flow.lastJournalTimestamp;Object.keys(msg.payload).forEach((key) => {  if (msg.payload[key].timestamp) {    const keyTimestamp = new Date(msg.payload[key].timestamp).getTime();    if (!flow.lastJournalTimestamp || flow.lastJournalTimestamp < keyTimestamp) {      // this entry is new - keep it. MULTIPLE events may have the      //  same timestamp so wait with reassigning so we don't skip      //  em or get the latest a 2nd time if nothing else changes.      // update the next latest timestamp if this is newer      if(!newJournalTimestamp || newJournalTimestamp < keyTimestamp) {        newJournalTimestamp = keyTimestamp;      }    } else {      // lastJournalTimestamp is newer, skip this      msg.payload[key] = null;    }  }});// make sure this is a valid date for the next timeflow.lastJournalTimestamp = newJournalTimestamp || new Date().getTime();// remove all nulled events from the payloadmsg.payload = Object.fromEntries(  Object.entries(msg.payload).filter(([_, p]) => p !== null));msg.payload.timestamp = new Date(flow.lastJournalTimestamp);return { payload: msg.payload };

So I do now keep track of the last read timestamp and reject every event that is older than the last read keeping the Journal dump smaller. This way I don’t have to try to keep track of the “latest” event to drag data from. Refuelling e.g. can happen from whopping 4 (or more) different events and it’s painful to compare all and check which one is the latest to keep track of the real current fuel levels for each tank.

Downside is I won’t get a full set of data for the current session any more if I have to reload my HUD app. This could be mitigated by using MQTT though where I could simply persist each event topic. That is already implemented and I can choose between SocketIO or MQTT in my app anyway.

https://beko.famkos.net/2025/03/29/parsing-the-elite-dangerous-journal/

#EliteDangerous#EliteDangerousOdyssey#homeCockpit
ExploreLive feeds
About