@Damian 1st of all, I don’t think you need to do an npm install after cloning the repo (doesn’t say it in the readme… although its been a while since I set up my hive so cant remember although I dont have a ‘node_modules’ subfolder in my MMM-Hive folder so unlikely).

Not sure if thats 100% your problem but you could start off removing the folder & then recloning.

I modified my outside url to be http instead of https as I was getting that issue so that should work.

I’d recommend that you go back to basics… 1) does your mirror work with the MMM-Hive removed from the config? Check that 1st
2) As you’ve used just about every config option its hard to see which (if any) could be causing the issue. I’d start off adding in just the basics- u/n, password, receiver name (note I haven’t set this as I just use the default so cant advise where this may screw up). Then you can add in options one at a time.

As @mongo116 says the ‘debug’ option could also help to see a bit more where its going wrong.

@mongo116 no, thank you for making the module! I had a crack at making a hive module a while back & gave up as I couldn’t get it working so it was great when I saw you’d done all the hard work :)

@Damian Yes I think it would be best to just use the basic config from the readme 1st & see if that works (obvs with your username / password combo).

All @mongo116’s comments about authenticating / session IDs etc are more for if you are stepping through the code yourself with a debugger in your browser. I don’t think that’s what you’re trying to do. You don’t need to worry about any of that if you’re just wanting to view the module on your mirror as it should do all that in the background. If you did want to start trying to see where its going wrong you can enable the

debug : true

option and then connect your web browser on a computer to the mirror and use the web developer console too see some more detailed info on whats happening in the background.