Open 00javad00 opened 3 years ago
I don't quite understand your question. A VEN can opt out of the Event by responding to the oadrDistributeEvent
by posting a oadrCreatedEvent
to the EiEvent
service. You only need EiOpt
for more complicated opt information.
What exactly do you need EiOpt
for that is not covered by oadrCreatedEvent
?
As you also mentioned oadrCreatedEvent
has to be used in reply to an EiEvent
service, but EiOpt
is separate service for indicating a temporary availability schedule to VTNs . This covers oadrCreateOpt
, oadrCreatedOpt
, oadrCancelOpt
, and oadrCanceledOpt
payloads, which are kind of availability reporting rather than an event response.
Are you using the EiOpt for a specific use case at the moment? I'd be interested to learn about it. Implementing EiOpt is not very high on my list, so if you'd like to contribute your own implementation, that would help.
To check the availability of VEN in participating in the different markets. Currently we planned to utilize this method for pre-assessing the availability of V2G chargers (it is a pilot project) regardless of having an event or not.
First at all congrats for this great effort, Then despite the fact that a handler is considered for
Event Optout
using theon_event_opt_out
function (undertest_event_distribution.py
package), but seems no verification test has been provided to this matter. According to PICS and OpenADR 2.0b Profile Specification, Section 7.2.2 (conformance rules 510); A VEN MUST be capable of utilizing the EiOpt service to further qualify the opt state of an event. It is appreciated if you could address this also by providing a best practice verification test function.