Principles

Customer experience

• Any customer should be able to grant and choose their assets to quickly onboard via your customer-facing app.

• Like some open source smart home apps, your customer can see that their assets are connected to HanchuESS and same assets details which included work mode, battery state, operation, or other relevant information in the client's customer-facing app.

• Customer perferrence should by synced between 3rd parties and HanchuESS if specified.

• Customer could manually local operate their assets, which means is prior to any platform, he/she could suspend their assets anytime.

Control process

• We received commands with periods of battery work mode from your platform.

• If the device is inverter, we expose various power set collection such as battery power, grid power to control import or export when we are instructing it to do so.

• Once start/processing/finished within command periods, we notify your subscription immediately.

• We will push the telemetry of customer assets in round robin to help you monitor performance, and also ensure that it is following our instructions.

Technical notes

• We will need to receive 2xx http response to any events we send to a subscription. Should a percentage of these events fail to send a 2xx http response HanchuESS Connect will mark the subscription as inactive until it is reactivated.

• You will need to reactivate subscription by hanchuess:subscription:test event if offline, otherwise we will not push any data to you.

• Take telemetry from the device to understand its operation into consideration, we will push the telemetry values through HTTP requests at frequency of every 1 to 5 minutes.

• Any control events that are sent to be actioned between a window of immediately to 5 minutes depending on our hardware limitations.