Role back firmware?

Does anyone have a way to role back firmware? I do not need to do it yet but I might role back from 3007 to 3005

Many thanks

The last update notes do mention that this might be possible in certain situations but doesn't give any details.

Are you having problems with 3007? I haven't applied it yet as I waiting to see if there were any reports of issues first.

judgepd Performance appears to be much worse. How fast the system ramps up and down to load. Prior to upgrading this weekend my overnight use according to my smart meter was 200 - 250wh but since upgrading my night usage is 650 - 700wh. Nothing has changed in my house, only the firmware. At the end of the day yesterday I noticed the house had used 1.3kw and previous days were 400 - 600wh everyday apart from Sundays. I am going to keep an eye on it but if it continues I would rather go back to 3005.

I'm guessing you'd have to ask support to roll back for you or at least supply the file to do it manually. I wonder if other users on 3007 have noticed the same problem...would be very disappointing if so.

I have mentioned the issue to support. But with only 2 days of data it is not really enough. But in a weeks time if it is doing the same I will request a role back.

have been holding off moving to 3007 and will stay with 3005 if it is importing significantly more per @THALL

I will update again at the end of the week. I expect every morning I will see 3 times previous grid use based on the last 2 days. Shame really, it was working great. I only upgraded as I thought my second battery would come with the newer firmware anyway so thought I best keep up to date.

I’ve not dived too deep into the data but I would agree, performance is different on 3007. Seeing similar issues with ramp up and down speed but also with how much juice I have after the overnight load is covered. Not sure if the SOC is just more accurate or if capacity has also been affected. I’m on octopus agile at the minute and exports are generating welcomed credit. I’m not going to bother rolling back as it isn’t having a significant impact for me in my set up. I might feel different if it were the depths of winter though!

My EV is due in a week or 2 so I don't want to leave Go yet. Though will change to Intelligent late august.

THALL I got a second hand EV last month so I’m planning on swapping over to go towards the end of summer.

Only difference Ive seen is better balance across multi battery packs. Low cut off now 7% not 4, despite Portal saying 4

TheDragon (GivEnergy) I am having a second battery installed soon which is why I added the new firmware. But I do not want to run it if my grid usage is going to increase 4 fold. Last couple of months I have only used 20kw per month, but I am up to 7kw since installing the firmware sunday.

I have contacted support to request a rollback. From Sunday afternoon until this morning my home has sucked as much juice from the grid as the entirety of last month. Weather here has still been mostly sunny so something is off (for me at least) with this new firmware.

My setup is the AC3 with the 8.2kw battery. The AC3 is fed from 2 solar systems. So maybe my setup is a bit different but regardless I really want the 3005 firmware back.

If anyone from support see's this please help me. Happy to try a beta firmware to correct the issue or rollback to 3005 and leave it alone.

And this is why I'll never be updating to a new firmware for at least a month or two. The updates of the app are bad enough, but stuff like this ends up costing money and time ultimately. For a firmware that was in testing for quite a number of months and if it turns out this is the reason for your drain, then the QA process is sadly lacking.

I'd be very keen to see some comment from @Adam-Reynolds to know if they are aware of there being a problem with firmware 3007.

I am yet to hear back from support on the issue. Only been 2 days though, emailed 6am on the 5th noting the issue

THALL Maybe give them a call? I have two HY5s and had been on 3001 for both batteries since installation in January. A couple of weeks ago when the update button appeared, I updated both batteries a couple of days apart and both went to 3005 but the firmware update button was still available. I updated one and it went to 3007 after a recalibration cycle. I was really fortunate with the timings of the updates as they started in the day. I was able to dump the discharge to the EV and the charge came from PV initially and then from the other battery. The following day, I tried to update the second battery since it had discharged to about 12% charging the other one. After it had been doing nothing for a few hours, I phone support and they initiated a manual recalibration for me.

Speaking to Givenenergy, I got the impression that the recalibration could take place any time within a day or two after the update had been requested. I was a bit miffed that I wouldn't be able to control the timing of the cycle, but it's all good now.

Since the update, I haven't seen any real change in performance but accept that my plant is different. Also while I was speaking to Givenergy, they did comment that I must be the only one not having problems with inverters fighting each other. On the other hand, maybe they only get calls from customers experiencing inverter bad-behaviour whereas those of us who are lucky to well-behaved inverters don't speak out.

Tim I am not in a massive rush to rollback, I have offered to test any beta firmware to move forward with a fix rather than back. I would like some kind of fix in place before my ev arrives 😀 It is currently on a boat somewhere in the North Sea so got a week or 2 before it gets to the dealer.

Actually as no one else has noticed this the issue could be related to my different inverter firmware D0.534-A0.535 which was deployed to fix an issue where the monitoring showed I was generating 39KW's for extended periods 😀 Some bug to do with having dual solar systems feeding my AC3.

3007 has shown up some odd issues for me, the issue I had with 3005 hasn't gone away. Now the lower cut off is 7% and not 4. Which is weird, as the Inverter still has it as 4. I too would be happy to test a forward approach rather than back