@sdetweil Do you know if there’s a way to run the node_helper on the client device?
Something like a semi-independent client that uses a config from a serveronly device while additionally running part of it’s own?
Read the statement by Michael Teeuw here.
Latest posts made by skhynix
-
RE: Screencast on all clients
-
RE: Screencast on all clients
@sdetweil When I cast, my pi4b opens a cast window on the server even in serveronly mode. the server is running the latest raspbian os with GUI. Aside from casting, the serveronly instance does not show any MM2 UI.
The clientonly device is a pi400, also running the latest raspbian os. The only difference between the client and server is that the clientonly does not have any of the modules or config files set up. Those are all run from the server. -
RE: Screencast on all clients
@sdetweil The client does not present a cast window in clientonly or browser mode.
-
Screencast on all clients
I can’t find anything easily, is there a way to have the MMM-Screencast module show on multiple devices?
I’ve got 2 raspis, one running serveronly and one clientonly, the serveronly creates a youtube instance while the client does not. (tested using RDP to view server pi) -
Request: Klipper
https://www.klipper3d.org/
Didn’t see any posts for klipper, the 3d printing firmware, so maybe someone could make this?
it would be nice to show print completion data as well as either a webcam feed or photo.
The moonraker telegram bot already accesses the api, so that can probably help make everything (https://github.com/nlef/moonraker-telegram-bot)
Screenshot showing what currently shows up attached
I would make it myself but don’t have any js experience