[MMM-Remote-Control](v2-dev) Extensible REST API, Dynamic Menus, and Socket Communications, plus other updates

shbatm

@dazza120 said in [MMM-Remote-Control](v2-dev) Extensible REST API, Dynamic Menus, and Socket Communications, plus other updates:

Can this also update modules like MMM-Remote-Control-Repositories, in just this one module?

Yes. This version pulls the list of modules from the Wiki and updates the modules.json file when its started (at most 1x per day).

dazza120

@shbatm cheers I’ve looked through the read me and I am completely lost, it’s not just like doing a git clone and then putting stuff in the config file 🧠😁

Cr4z33

This post is deleted!

shbatm

@dazza120 Sorry, I’ve been away. What are you lost with? Can I help point you in the right direction?

If you’re just looking to install this version, see a couple posts up. For the most part it functions just like the other version, but adds a lot of advanced control features on top–like controlling your mirror from a browser or home automation controller (via API) or adding module control menus to the existing “/remote.html” page.

robiv8

Is there any way to track traffic from remote control Nothing is visible in pm2 logs.
A kind debuging or like.
Alert it does not work. It comes the OK for transmit but nothing appears. Restart works and also monitor ON OFF.
But the browser does not refresh again.
Everything works as long as I only have the sample config.
But as soon as I have several other modules running (Page-Selector, Buttons, DWD-Warn-Wetter, PublicTransportHafas, etc.), it is no longer possible.
I would like to know what blocks the module.

shbatm

@robiv8 I don’t have a debug mode, but you can try adding:

console.log(notification, payload); to Line #988 of node_helper.js to print all notifications received by the back-end from other modules; or console.log(query) to Line #644. If you are using the API, you should be getting a response back in the browser or Postman.

Looking at your list, I have a sneaking suspicion that Page-Selector is causing the issues, just because it may be inadvertently suspending the module. If you troubleshoot and find that to be the case, and can’t find a work around with that module, you can try using MMM-Carousel w/ Navigation which is what Page-Selector was originally based off of. I know there is an option in that module to “exclude” a module from being suspended.

robiv8

@shbatm
Thanks for your explanation
I will try it tonight and then report it.

And yes, I also suspect that it is the page selector.
Whereby I set “Alert, notification, buttons and podcast2” to exclude. And nevertheless.
I’ll take a look.

Cr4z33

@shbatm I’ve done the Italian translation if you want to add it. ;)

https://www.dropbox.com/s/u8hwhecv0exrmcj/it.json?dl=0

robiv8

@shbatm
are you sure with console.log(notification, payload); to Line #988
my node_helper.js is going only to line 958

shbatm

@cr4z33 thanks! I’ll add it when I get a chance.