@Klinge Just tested the module and it is working fine for me. The module requires a language in the config but it is not in the sample. So you may want to check that. As for the error you are getting, Have you changed anything in line one of the node_helper? The comment section.

@drdeath I applaud you for the effort and time you put into this. I was just explaining what the encoding meant and how the others could go about decoding it. I have a fully setup system and my own dev environment and probably would not be able to test your script. My apologies for that. But again, good work and nice effort.

P/s - do not take offence to the community. We are all dev’s around the table and we try and assist to make things better where we can.

@drdeath I think what the guys were saying or are trying to say, is that for the standard MM user, looking at the script and seeing “coded” code they may be hesitant to test the script. Although it can easily be decoded with echo 'base64 string' | base64 -d which would reveal the coded strings, the normal user does not know this.

It does make the script so much smaller but for a newb looking at that would scare them away.

Just my 2pence.

@foggy Your config works fine as is for me. Are you seeing any errors in the logs or the developers window?

@osnapus maybe @CFenner can have a look at this or advise. He seems to be a contributor to that project.

@brentmatthews Hi, yes, I did not require a css file for the module. You are welcome to add and submit a pr if you like.

@rvnbrg Jinja is a dependency of Flask and Flask V1.X.X uses the escape module from Jinja, however recently support for the escape module was dropped in newer versions of Jinja

To fix this issue, simply update to the newer version of Flask V2.X.X in your requirements.txt where Flask no longer uses the escape module from Jinja.

I see there is a requirements.txt where the version of Flask is specified. Maybe updating that to 2.1.1, which is the recommended version that no longer has a dependency on escape would resolve this.

This is all just guessing. Was trying to figure out how this module hangs together. 🫣

@danfagerburg What errors do you see? Are there errors in the pm2 logs or on the console? Also, check the Dev Window for any errors.

@mumblebaj There were changes to Growatt API and the current version of the module has stopped working throwing errors.

Please update to the latest version of the module, v2.0.5 which now works,

Thanks
BM

@mumblebaj Thanks Sam. Anything else I need to worry about?