"history" is broken since first of March

[algorithmixx]

It seems that Growatt have changed something in their API TWO DAYS AGO

As soon as I set historyLast=true or historyAll=true I get an error.

Here is an excerpt from the API DEBIG LOG

2025-03-02T16:52:24.750Z growatt:api getHistory: type tlxh sn: FMP0E3J019 startDate: 2025-02-17T00:00:00.000Z endDate:
2025-03-02T16:52:24.183Z start: 0 allDatasets: false
2025-03-02T16:52:24.750Z growatt:api getHistory: params URLSearchParams {
'tlxSn' => 'FMP0E3J019',
'startDate' => '2025-02-17',
'endDate' => '2025-03-02',
'start' => '0' }
2025-03-02T16:52:24.838Z growatt:api getHistory reject
2025-03-02T16:52:24.838Z growatt:api getPlantDeviceData getHistory tlxh err: Error: The server sent an unexpected
response, a fatal error has occurred
at C:\xampp\htdocs\growatt\node_modules\growatt\lib\growatt.js:499:24
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2025-03-02T16:52:24.839Z growatt:api getAllPlantDeviceData getPlantDeviceData tlxh err: Error: The server sent an
unexpected response, a fatal error has occurred
at C:\xampp\htdocs\growatt\node_modules\growatt\lib\growatt.js:499:24
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2025-03-02T16:52:24.839Z growatt:api getAllPlantData getAllPlantDeviceData err: Error: The server sent an unexpected
response, a fatal error has occurred
at C:\xampp\htdocs\growatt\node_modules\growatt\lib\growatt.js:499:24
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2025-03-02T16:52:24.842Z growatt:api getDevicesByPlantList: plantId: 10032567 currPage: 1
2025-03-02T16:52:24.845Z growatt:api logout:

Contact me at [email protected] if you need more details.

Thanks for the great work!

Gero

[PLCHome]

Thanks for the analysis. I'm on vacation until March 17th. I can take a look at it after that.

[algorithmixx]

Thanks for the quick response. It would really bei nice if you could look after it when you are back. I am afraid it would cost me a lot of effort to understand why it fails and how to fix it. Kind regards, and enjoy your holiday! Gero PLCHome ***@***.***> schrieb am So., 2. März 2025, 20:19:

…

Thanks for the analysis. I'm on vacation until March 17th. I can take a look at it after that. — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALBUS7JW7C2SQNXR3GH3N532SNKS7AVCNFSM6AAAAABYFN6ZZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJSHA3DMNZTG4> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: PLCHome]*PLCHome* left a comment (PLCHome/growatt#33) <#33 (comment)> Thanks for the analysis. I'm on vacation until March 17th. I can take a look at it after that. — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALBUS7JW7C2SQNXR3GH3N532SNKS7AVCNFSM6AAAAABYFN6ZZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJSHA3DMNZTG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>