EnergyHub Control Status when active on FCR

[nsimb]

Feature request

Hi and thanks for all the work with this.
Just wanted to check if it's possible to update the control status when FCR markets.
Or keep the response in someplace so automations can know that it's no idea to try to change the configuration.

Background, I Am currently testing out FCR market with a retailer/balance with ferroamp to use the battery on FCR market. When that happens ferroamp will disable the MQTT commands and take over the control. When the activation is ended on FCR they will release the battery back to MQTT handling with the status it had when they did take control. this is how it is supposed to work at least according to the support.

Since there is no way today to know when they are active and not it ends up that my automation tries to act and it's no point
Tested a bit during an activation of what was returned, and it's a nak.
request:

{
"transId": "04029caa-1abb-11ef-b292-94c691186b60",
"cmd": {
"name": "discharge",
"arg": 0
}
}

response:
{
"status": "nak",
"transId": "..............................",
"msg": "failed to execute command: "ext-api-set (): Ongoing" taint present, which does not allow setting ["ext-api-set: Ongoing"] (All non-tolerations are: ["ext-api-set: Ongoing","battery-maintenance-regular: Ongoing","battery-maintenance-critical: Ongoing","fcr-event: Ongoing"])"
}

I have not yet found anything other in the mqtt packages so far that that is usable sadly

Let me know if I can help out in any way

[argoyle]

I actually have exactly the same problem when sending charge and discharge commands after being upgraded to 5.7.2 and I'm not even in any FCR project. 😳 I'll try to get in touch with Ferroamp regarding this and see if there is anything we might see and do via MQTT. Or has @danielolsson100 already been in contact with them regarding this perhaps?

[danielolsson100]

I sent an RFC to Ferroamp regarding a FCR/remote control flag in the MQTT data so we can know when the battery is managed by Ferroamp cloud in any way.
But there has been no more respons than "we will send it to the developers".

[nsimb]

Hade the same discussion with the support on an earlier firmware 5.5.0-FCR.1, they fixed my problem in next beta release. Did then bring up that it would be good with state in integration when they take control. Will reach out to them again and ask if something is in the roadmap. Did hear that more retail company’s is on the way into FCR with Ferroamp so the demand for the development should increase.

[argoyle]

Also sent a ticket to support now. Asking both about the failure to send commands as well as additional information in the MQTT API.