Last night it has failed as well

22:30-00:00 charge and hold accepted but not actioned
00:00-05:30 charge and hols accepted and not actioned.
In both cases the Inverter is idle, on hold at 6% charge.

What I do see is that the hold command for the first period was sent to the Inverter 17 seconds AFTER the charge instruction for the start of the second period had been sent. But that does not explain why the Inverter did not action the first charge period successfully.

    Further - in its current state - it is ignoring Quick Schedule charging - you can send the command and it accepts it but does nothing.
    I have GiVTCP running on HA but this has no automations set - it is normally purely used for monitoring. If I try to force charge from HA this also fails to action an actual state change to charge even though it shows as actioned.

    SO - I have gone back to the portal. The Discharge Rate was set at 0% (which logically it should be as the Inverter is commanded to HOLD). If I alter that manually to 100% - ie allow full discharge - then the Inverter starts to CHARGE as a period is active.

    SO - maybe HOLD means exactly that - dont CHARGE OR DISCHARGE. If that is the case the HOLD command needs to be revoked before any charge schedule is sent ???

    Is that a clue?

    RB63 If you go to My Inverter, then select top right hand menu, the little cog with Remote Settings (or similar) and then at then when you scroll to the bottom, you should see logs there.

    RB63 Yeah, some weird overlapping issue going on for your scenario, we'll do some more digging.

    RB63 Looks like there was an issue where the charge window hold overwrote the charge instruction 00:00-5:30. We've applied a fix for this scenario, which will be available in the next 10 mins.

    Yes but it did not charge 23:30 to 00:00 either..

    As I say - if ALLOW FULL DISCHARGE is at ZERO it appears to not allow CHARGE to take place. Maybe this needs to be reset to 100% for the duration of the charge periods as well.

      RB63 Instruction for 22:30-00:00 seems to have been sent and received OK.

      Including the charge rate = 2600.

      Discharge rate should have no bearing on AC charging, we would see far more issues across our Giv users if that was the case (and would be a Giv bug).

      That may be so but it was only when manually I altered Allow Full Discharge on the portal from 0 to 100% (05:40:11 in the log) did the Inverter start to CHARGE (there was an active session at the time set off at 05:35:35).
      This all relates to HOLD - if I dont hold then it all works as it should.

        Also note that the Battery state was 5% at the start of the 22:30 to 00:00 charge instruction and it was 6% at the end when the next session was started (the 1% difference is because we have a wind turbine connected to Bat 2 in the chain) so you can see that no charge was sent to the batteries..

        Ditto all these yesterday - charge commanded and no charge happened as you can see by the Bat %

        RB63 The question is, if indeed the discharge rate being 0 is the reason your inverter is not charging, it sounds like a Giv bug, and should WW work around those?

        Can you mimic the scenario reliably via the Giv app/portal at all? Giv may otherwise just say "Ah, that's WW...", whereas if you can reliably reproduce the scenario just with Giv app, they're more likely to take it seriously.

        If you can, it would be worth querying with GivEnergy if this is expected behaviour, although they may just ask you to update firmware?

        Firmware is as far as I am aware current a D0.449-A0.449

        It should be easy enough to test this out further - watch this space...

        well if I trigger timed charge from the portal it appears to work irrespective of the Discharge % ( tried 0/7/51/100%)

        Equally with HOLD turned off on WW it is accepting a 20 min charge OK.
        But it is also accepting WW 20 min charge if Discharge is set to 0% now.

        So I dont know what to make of it really. There must be something on the forward timeframes that is upsetting it maybe or some change of command type being sent. Not clear at all. Sorry.

          RB63 Thanks for digging into it a bit more.

          OK, let's keep an eye on any Hold windows you got coming up, thanks again.

          OK - so we have been chargind until 4pm. Then asked to discharge at Full Export rate 4-8pm
          Command sent from WW OK
          Inverter sat at zero discharge....
          This has happened before as well.

          Manually set Force Discharge for 3 hours in HA and it is discharging at full rate as it should.

          You are sending something weird at 16:01:55 if you look

          WHY???

            RB63 That's simply WW 'disabling' the charge slot that has just passed, by setting AC start and endtime back to 00:00-00:00.

            You can see from the commands sent at 15:59, we disabled Eco mode, Set Discharge power to 2600 and Discharge start and end time 16:00-19:57.

            AC charge and end time being set should have no bearing on this.

            But what I do notice is that you set Discharge period 2, whereas we set discharge period 1. We exclusively use DIscharge period 1 and the Enable DC Discharge flag.

            Is there another setting where you have disabled Discharge period 1 perhaps?

            I just went into HA to turn on Force Discharge manually for 180 mins- seems they may use Period 2 then on the GivTCP.
            That to some extent is irrelevant as the reason i did it was because the WW command did not result in the discharge starting.
            I only us HA to monitor as I said before - there are no automations or links to other actions set up.

              This is what HA is seeing currently
              :

              If you look at the RAW log - see the extra entry at 15:59:28 from WW setting Discharge Power to 50W....