New H1 G2 Firmware

[jhd25]

Manager 1.73 / Master 1.55 offered today and (gulp!) installed.

No issues as such (although oddly after install battery discharge ramped up slowly ). However the Forced Discharge SoC limit revert to grid import issue is still present .

[Spooksman]

I seem to remember that when I did the last update, the maximum draw from the grid was reduced and I had to fix that on the inverter front control panel - is that what your are describing? If so, I've lost my notes of what I did on the front panel - I think I had to do something to set it back to 14000 (?) somewhere (so it would charge the battery and the car at full rate at the same time).

Can anyone give me a clue what I might have done before I think about updating...?

I hate getting old

[jhd25]

I seem to remember that when I did the last update, the maximum draw from the grid was reduced and I had to fix that on the inverter front control panel - is that what your are describing? If so, I've lost my notes of what I did on the front panel - I think I had to do something to set it back to 14000 (?) somewhere (so it would charge the battery and the car at full rate at the same time).

Can anyone give me a clue what I might have done before I think about updating...?

I hate getting old

The grid import limit didn't get changed as far as I can see . Rather when it came back initially the battery was charging from the solar but the load was being met from grid. The battery discharge power then slowly ramped up so that the normal self use behaviour was obtained.

[Spooksman]

Thanks

[nrb501]

The slow ramp-up of inverter power output is normal following a restart. Should be approx 60secs IIRC.
The ability to change behaviour when FDSoC is met during a mode schedule slot should be coming but will require updates to the app and web pages.

[NickJH]

When I updated, like before, when FDSoC was met on discharge, it switched to Home Use from Grid Import and Solar panels charging the batteries. I haven't done any restarts, just updated the two firmwares.

[NickJH]

@mods This firmware is still listed as "In Testing" in the Firmware Spreadsheet. It was released and available through the app about 2 weeks ago.

[daveg]

Manager 1.73 / Master 1.55 had been showing as available updates in the Foxcloud App. I didn't apply them because Will's spreadsheet still showed them as testing.
Yesterday evening the App updated and now I notice that they are no longer showing as available updates. Instead 1.70/1.53 have reverted to showing as Latest.
I have no idea whether this is because they failed testing and have been withdrawn or because of a glitch in yesterday's App update.
I find it hard to have confidence in FOXESS updates not to introduce new issues. That situation isn't helped by the fact that they don't issue meaningful changelogs.
Edit - now I see that 1.76/1.57 have been offered to some users today (but not me so far) - so maybe 1.73/1.55 have been superseded.

[daveg]

Today I see that Will's spreadsheet now has 1.76/1.57 'In Testing' and they have also been offered to me as updates today.
Is there any provision for standard users to roll back firmware updates if they don't work well?
TIA
Dave

[Spooksman]

I'm a little new to this, and am a bit confused... I'm being offered 1.76/1.57 today as well - if they are being offered out to 'normal people' like me, how can they also be 'In Testing'?

Is the testing just an informal thing on here, and who decides when the status goes to 'Production (Latest)'?

Thanks

[Spooksman]

Well, I clicked the upgrade button, but no joy!

There was an error on the Manager update (error: 41206) after about 58%, followed by an error on the Master (Code: -1, Pre-upgrade exception).

I guess I'll leave it a while to see what other people find out...

[NickJH]

I've upgraded. Crossing my fingers now ......

[jhd25]

I've upgraded. Crossing my fingers now ......

I upgraded earlier today - no issues so far ...

[Spooksman]

Well, I clicked the upgrade button, but no joy!

There was an error on the Manager update (error: 41206) after about 58%, followed by an error on the Master (Code: -1, Pre-upgrade exception).

I guess I'll leave it a while to see what other people find out...

I tried the update again last night, and it upgraded just fine (as far as I can see) - not sure what was going on before...

[carrot1401]

I'm a little new to this, and am a bit confused... I'm being offered 1.76/1.57 today as well - if they are being offered out to 'normal people' like me, how can they also be 'In Testing'?

Is the testing just an informal thing on here, and who decides when the status goes to 'Production (Latest)'?

Thanks

I can explain this bit, site admin Will isn't part of Fox, rather just a super cool dude that works with them. He is likely doing his own testing. As ever I wait to see what he says to see what fixes and improvements (if any) updates bring. If it ain't broken....don't fix it!

[jhd25]

I'm a little new to this, and am a bit confused... I'm being offered 1.76/1.57 today as well - if they are being offered out to 'normal people' like me, how can they also be 'In Testing'?

Is the testing just an informal thing on here, and who decides when the status goes to 'Production (Latest)'?

Thanks

I can explain this bit, site admin Will isn't part of Fox, rather just a super cool dude that works with them. He is likely doing his own testing. As ever I wait to see what he says to see what fixes and improvements (if any) updates bring. If it ain't broken....don't fix it!

A sensible warning - I keep hoping that new firmware will revert the Force Discharge behaviour to the prior behaviour of switching to running off battery when FDSOC is reached rather than importing from grid at peak rate.... Currently I am having to use HA/MODBUS to sell power in the evening octopus flux peak.

[Spooksman]

I'm a little new to this, and am a bit confused... I'm being offered 1.76/1.57 today as well - if they are being offered out to 'normal people' like me, how can they also be 'In Testing'?

Is the testing just an informal thing on here, and who decides when the status goes to 'Production (Latest)'?

Thanks

I can explain this bit, site admin Will isn't part of Fox, rather just a super cool dude that works with them. He is likely doing his own testing. As ever I wait to see what he says to see what fixes and improvements (if any) updates bring. If it ain't broken....don't fix it!

Thanks for taking the time to explain - good to know, and thanks goes to Will for the work he puts in.

I will heed your warning going forward about updates

[stevo125]

I'm a little new to this, and am a bit confused... I'm being offered 1.76/1.57 today as well - if they are being offered out to 'normal people' like me, how can they also be 'In Testing'?

Is the testing just an informal thing on here, and who decides when the status goes to 'Production (Latest)'?

Thanks

I can explain this bit, site admin Will isn't part of Fox, rather just a super cool dude that works with them. He is likely doing his own testing. As ever I wait to see what he says to see what fixes and improvements (if any) updates bring. If it ain't broken....don't fix it!

A sensible warning - I keep hoping that new firmware will revert the Force Discharge behaviour to the prior behaviour of switching to running off battery when FDSOC is reached rather than importing from grid at peak rate.... Currently I am having to use HA/MODBUS to sell power in the evening octopus flux peak.

I saw on another thread here that this is fixed on one of the most recent updates, though it required an installer-only switch to enable that behaviour. Had a quick look and can't find the post now

[NickJH]

When I updated to Master v1.57 and Manager v1.76, like before, when FDSoC was met on discharge, it switched to Home Use from Grid Import and Solar panels charging the batteries. I haven't done any restarts, just updated the two firmwares. So, no improvement.