Does the MeshCentral API not report powered on or connected status for Windows agents?

[DaanSelen]

As the title asks, does it not?

"mesh//lgNwoUxCblablabla57ghcd9": [
            {
                "mtype": 2,
                "_id": "nblablablaCft1AjX@",
                "icon": 1,
                "name": "N-DESKTOP1",
                "rname": "N-DESKTOP1",
                "domain": "",
                "host": null,
                "ip": "172.16.25.234",
                "osdesc": "Microsoft Windows 11 Home - 24H2/26100",
                "av": [
                    {
                        "product": "Windows Defender",
                        "updated": true,
                        "enabled": true
                    }
                ],
                "wsc": {
                    "antiVirus": "OK",
                    "autoUpdate": "OK",
                    "firewall": "OK"
                },
                "users": [],
                "lastbootuptime": 1734779438000,
                "defender": {
                    "RealTimeProtection": true,
                    "TamperProtected": true
                }
            }
        ]

Compared to a Linux machine it does not report the powered on or connected status?

[si458]

Well what api command did u call to get the current information as it might be a different command

[DaanSelen]

Yes lets leave it at that. For me personally it would make it easier, but let me know what he thinks. If he does agree, then good. If not I'll make another call for the nodes.

[DaanSelen]

P.S you can use the --filterid [id] with nodes to only return the single device you are asking for

This would make another call for every device reported. I think its more efficient to make 2 general calls and just reference the data.

[si458]

@DaanSelen the way the web ui does it

1. it calls nodes to list all the devices,
2. then when u pick a device, it calls other functions to get details about the device (deviceinfo for meshctrl.js example)

ws.send(JSON.stringify({ action: 'getnetworkinfo', nodeid: args.id, responseid: 'meshctrl' }));
ws.send(JSON.stringify({ action: 'lastconnect', nodeid: args.id, responseid: 'meshctrl' }));
ws.send(JSON.stringify({ action: 'getsysinfo', nodeid: args.id, nodeinfo: true, responseid: 'meshctrl' }));

the idea of getDeviceDetails from the looks of it is to merge those 3 commands together so its a single call

you can also specify nodeids with a list of devices you want it to return data for

example: { action: 'getDeviceDetails', nodeids: ['id1','id2'], responseid: 'meshctrl' }

[si458]

OMG your issue about merging the pwr,conn was already asked/answered 3 years ago 😆
#2933

edit: it appears to have maybe been missed! so i might add it in for you!
can you open an enhancement request plz asking for this feature 👍

[DaanSelen]

OMG your issue about merging the pwr,conn was already asked/answered 3 years ago 😆 #2933

edit: it appears to have maybe been missed! so i might add it in for you! can you open an enhancement request plz asking for this feature 👍

I've read the Issue, and looks like Ylianst forgot about it. I don't blame him! Lets pick it up if he agrees.