MMM-Growatt

nowayto

@mumblebaj First of all, thak you again.
I might found 2 syntax errors:

    {
        module: "MMM-Growatt",
        position: "middle_center", //Works best at middle_center. May not display all that well in other positions
        disabled: false,
        config: {
            username: "username",
            password: "password",
            usServer: true, // only used by US Registered users
            debug: false, // set to true if you want to create a debug log
            mode: "dual", // Specify 'dual' when running https://github.com/mumblebaj/MMM-Growatt.git and https://github.com/mumblebaj/MMM-Growatt-Stats.git together else specify 'single'
            view: "table", // Only add this if you want a minimalystic table view
            rowToDisplay: [ "loadPower", "batteryPower", "solar", "loadPower" ] //Remove items you do not want to display on the table. Table will be ordered in the same order as items appear in the list. Not required of view is not table
            updateInterval: 1000*60*30 //Update every 30 minutes
            
                    }

},

inside the rowToDisplay line, after the closing square comma, a comma is missing
and between the two square commas there are two “loadPower” so I wrote"gridPower" instead and seems working but in that moment solar power is higher than load so I don’t have any valor in it.

Two question: can I enhance the charachters dimension?
can I add “exportedPower” to it?

Thanks

mumblebaj

@nowayto Hi. I will fix the README when I get some time. Unfortunately you cannot add exportedPower as that is not defined in the module when it gets the text and icons etc.

nowayto

@mumblebaj I fix it by myself, butI just though you were interested about the two errors for other people.
Anyway thank you for everything, exportedPower is not a problem but is there a way to just enhance charachter dimension?

mumblebaj

@nowayto Yes, you can add your own dimensions in the ~/MagicMirror/css/custom.css.

I have noticed an error in the module css. I have corrected it. Please do a git pull before attempting the below changes.

You could set it as follows:

.growatt-table {
    font-weight: bold;
	color: orangered;
    font-size: 0.5rem;
}

mumblebaj

@mumblebaj

Update v2.1.3 - Released

Added animation to the lines to show a visual effect of charging or discharging. Have been wanting to do this for a while and only had the chance to implement this.

The above change is on my dev branch being tested by myself. I welcome others to checkout the dev branch and assist with testing. Everything looks good thus far. If no issues raised against the dev branch then I will release to main over the weekend.

Couple of examples below showcasing the changes.

mumblebaj

Update v2.1.4 - Released!

The module display has been too rigid and only worked in the middle_center position.

I have made a number of changes to the css which now allows the module to be displayed in any of the other regions.

The updates are currently on my dev branch for anybody who would like to test. I will release to main by the end of the weekend.

mumblebaj

v2.2.0 Upgrade

I have decided to refactor the code to make it a little easier to manage

Update growatt library to latest
Added helper functions
Add a connection retry in cases where connection to the Growatt server is down or interrupted
Add better error handling

Current users do NOT have to update to the latest version unless you want to be on the latest version.

If you do decide to upgrade and experience any issues, please open an issue on the MMM-Growatt Github page.

The same updates were applied to the MMM-Growatt-Stats module. If you update and experience any issues please open a ticket at the MMM-Growatt-Stats Github page.

nowayto

@mumblebaj
My module is working right now and I read you suggest to not upgrade it if it’s working but I’m interested about the “connection retry” function because sometimes (very rare) it stay still on a previous lecture.
Like half an hour ago or more

mumblebaj

@nowayto Hi. That sounds more like something else. Have you checked the logs to see if you see any errors during the time when there is no update? Let me know if you see anything.

The retry will try 3 times, first after 1000 milliseconds and and then at 2000 milliseconds and the last time at 3000 milliseconds and will return a warning. The next time it will try is at the refresh interval which is whatever value you have set.

You can update if you want to check this out. You can let me know if you experience any issues.

I am thinking about making the retry interval configurable but not sure if it is warranted at the moment.