homebridge-solaxcloud-api 2.1.2-beta.0 → 2.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +187 -187
- package/config.sample +14 -14
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,187 +1,187 @@
|
|
|
1
|
-
|
|
2
|
-
<table cellspacing="0" cellpadding="0">
|
|
3
|
-
<tr>
|
|
4
|
-
<td align="center"><img src="https://github.com/homebridge/branding/raw/master/logos/homebridge-wordmark-logo-vertical.png" width="150"></td>
|
|
5
|
-
<td align="center"><img src="https://www.solaxpower.com/wp-content/uploads/2020/03/weblogo5.png" width="300"></td>
|
|
6
|
-
<tr>
|
|
7
|
-
</table>
|
|
8
|
-
|
|
9
|
-
# Solax Cloud Plugin for Homebridge
|
|
10
|
-
|
|
11
|
-
  [](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
The Solax Cloud Plugin for [Homebridge](https://homebridge.io/) was created as a platform plugin to gather data exposed by Solax inverters to the cloud through the [Solax Cloud API](https://www.eu.solaxcloud.com/phoebus/resource/files/userGuide/Solax_API_for_End-user_V1.0.pdf).
|
|
15
|
-
|
|
16
|
-
Now with **support for multiple inverters**!
|
|
17
|
-
|
|
18
|
-
As HomeKit is still clueless about what a solar panel is, this plugin exposes a set of standard HomeKit accessories though Homebridge for each configured inverter that will allow interacting and automating your smart home based on the data made available from the Solax platform:
|
|
19
|
-
|
|
20
|
-
- **PV** (PV outlet with power consumption)
|
|
21
|
-
- **AC** (Inverter AC outlet with power and total energy consumptions)
|
|
22
|
-
- **To Grid** (Inverter to Grid outlet with power consumption)
|
|
23
|
-
- **To House** (Inverter to House outlet with power consumption)
|
|
24
|
-
- **From Grid** (Grid to House outlet with power consumption)
|
|
25
|
-
- **Update** (Motion sensor)
|
|
26
|
-
|
|
27
|
-
<img src="images/plugin-accessories-home.png" width="50%" height="50%">
|
|
28
|
-
|
|
29
|
-
Please note that additional accessories are created by default with smooth power consumption curves (by applying either a simple or exponential moving average to the power series). This prevents sporadic events like a cloud passing by to have an immediate affect on provided meters.
|
|
30
|
-
|
|
31
|
-
## Required information
|
|
32
|
-
|
|
33
|
-
For this plugin to work, two critical pieces of information are required from Solax Cloud:
|
|
34
|
-
|
|
35
|
-
- **Token ID**: Solax users can get inverter information through the granted tokenID. You need to obtain your tokenID on the API page of Solaxcloud.
|
|
36
|
-
- **SN**: Registration No (communication module SN) for each desired inverter.
|
|
37
|
-
|
|
38
|
-
## Installation
|
|
39
|
-
|
|
40
|
-
This plugin is supported under Homebridge. It is highly recommended that you use Homebridge Config UI X to install and configure this plugin.
|
|
41
|
-
|
|
42
|
-
### Manual Installation
|
|
43
|
-
|
|
44
|
-
Install this plugin using: `sudo npm install -g homebridge-solaxcloud-api`.
|
|
45
|
-
Edit `config.json` manually to add your Solax inverters. See below for instructions on that.
|
|
46
|
-
|
|
47
|
-
## Platform configuration
|
|
48
|
-
|
|
49
|
-
Minimal platform configuration is depicted by the example configuration file below:
|
|
50
|
-
|
|
51
|
-
```json
|
|
52
|
-
{
|
|
53
|
-
"platforms": [
|
|
54
|
-
{
|
|
55
|
-
"platform": "SolaxCloudAPI",
|
|
56
|
-
"tokenId": "20200722185111234567890",
|
|
57
|
-
"inverters": [
|
|
58
|
-
{
|
|
59
|
-
"name": "Solax",
|
|
60
|
-
"sn": "ABCDEFGHIJ"
|
|
61
|
-
}
|
|
62
|
-
],
|
|
63
|
-
}
|
|
64
|
-
]
|
|
65
|
-
}
|
|
66
|
-
```
|
|
67
|
-
Configuration parameters are described on the table below:
|
|
68
|
-
|
|
69
|
-
| **Parameter** | **Type** | **Description** | **Default** | **Mandatory?** |
|
|
70
|
-
| ------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------- | -------------:| :------------: |
|
|
71
|
-
| `platform` | string | Platform name (must be SolaxCloudAPI) | - | Y |
|
|
72
|
-
| `tokenId` | string | Users get information from Solax Cloud through the granted tokenID. Please obtain your tokenID on the API page of Solax Cloud | - | Y |
|
|
73
|
-
| `inverters` | array | Array of configured inverters as objects with `{ name: string, sn: string }`, where `name` is the inverter name, used as prefix for accessory naming and `sn` is the inverter registration no. (inverter module SN). | - | Y |
|
|
74
|
-
| `pollingFrequency` | number | Plugin data polling frequency from Solax Cloud (in seconds) | 300 | N |
|
|
75
|
-
| `smoothingMeters` | boolean | Whether to create additional meters by smoothing raw values from Solax Cloud | true | N |
|
|
76
|
-
| `smoothingMethod` | string | Statistical method to use for smoothing raw values from Solax Cloud (simple or exponential moving average - "sma" or "ema") | "sma" | N |
|
|
77
|
-
| `pureHomeApp` | boolean | Whether to create meters as standard accessories that can be used on the Home App (power will show as ambient light sensors) | false | N |
|
|
78
|
-
|
|
79
|
-
**NOTE:** The `pollingFrequency` parameter defaults to 300 seconds, since Solax inverters update cloud data every 5 minutes.
|
|
80
|
-
|
|
81
|
-
Configuration through the the use of [Homebridge UI](https://github.com/oznu/homebridge-config-ui-x) plugin is also available and recommended:
|
|
82
|
-
|
|
83
|
-
<img src="images/homebridge-ui.png" width="100%" height="100%">
|
|
84
|
-
|
|
85
|
-
## Non-standard characteristics
|
|
86
|
-
|
|
87
|
-
Non-standard accessory characteristics are available through the use of [Eve for HomeKit app](https://apps.apple.com/us/app/eve-for-homekit/id917695792) you may download from the App Store.
|
|
88
|
-
|
|
89
|
-
This will allow some non-standard characteristics to be visible along with its historical data (like power or total energy consumption), as depicted in the image below:
|
|
90
|
-
|
|
91
|
-
<img src="images/plugin-outlet-consumption.png" width="50%" height="50%">
|
|
92
|
-
|
|
93
|
-
If you want to rely solely on the native Home App, please enable the `pureHomeApp` config setting. In this case, power consumption on each meter will be exposed as an Ambient Light Sensor, as shown below (minimum value for an Ambient Light Sensor is 0.1 lux):
|
|
94
|
-
|
|
95
|
-
<img src="images/plugin-accessories-home-pure.png" width="50%" height="50%">
|
|
96
|
-
|
|
97
|
-
# Automation
|
|
98
|
-
|
|
99
|
-
Automation can be achieved with the help of the virtual **Update** motion sensor that was specifically tailored for this effect and which is available for each inverter. This motion sensor will be triggered whenever inverter data gets updated from the Solax Cloud API (according to what is defined on the `pollingFrequency` configuration setting).
|
|
100
|
-
|
|
101
|
-
<img src="images/plugin-accessories-eve.png" width="50%" height="50%">
|
|
102
|
-
|
|
103
|
-
Motion is detected by the **Update** motion sensor whenever there is newly fetched inverter data from Solax Cloud. Using this sensor as a trigger combined with power and energy data from the virtual outlets enumerated above forms the basic building blocks for defining an automation.
|
|
104
|
-
|
|
105
|
-
## Automation example
|
|
106
|
-
|
|
107
|
-
Since automations are probably going to be dependent on the non-standard **Consumption** characteristics from the virtual outlets, these must created by using the Eve App.
|
|
108
|
-
|
|
109
|
-
As an automation example, let's imagine we want to turn a pool heater pump on whenever the inverter AC power is greater than a specific figure (in Watt):
|
|
110
|
-
|
|
111
|
-
<table cellspacing="0" cellpadding="0">
|
|
112
|
-
<tr>
|
|
113
|
-
<td width="50%">1. Under Automation, select <b>Rules</b></td>
|
|
114
|
-
<td width="50%">2. Click <b>Next</b></td>
|
|
115
|
-
</tr>
|
|
116
|
-
<tr>
|
|
117
|
-
<td><img src="images/automation/automation_1.png"></td>
|
|
118
|
-
<td><img src="images/automation/automation_2.png"></td>
|
|
119
|
-
</tr>
|
|
120
|
-
<tr>
|
|
121
|
-
<td>3. Click <b>Add Trigger</b></td>
|
|
122
|
-
<td>4. Select <b>Motion</b> as trigger type</td>
|
|
123
|
-
</tr>
|
|
124
|
-
<tr>
|
|
125
|
-
<td><img src="images/automation/automation_3.png"></td>
|
|
126
|
-
<td><img src="images/automation/automation_4.png"></td>
|
|
127
|
-
</tr>
|
|
128
|
-
<tr>
|
|
129
|
-
<td>5. Select the Solax <b>Update</b> motion detector and set <b>Motion</b> as trigger</td>
|
|
130
|
-
<td>6. Click <b>Next</b></td>
|
|
131
|
-
</tr>
|
|
132
|
-
<tr>
|
|
133
|
-
<td><img src="images/automation/automation_5.png"></td>
|
|
134
|
-
<td><img src="images/automation/automation_6.png"></td>
|
|
135
|
-
</tr>
|
|
136
|
-
<tr>
|
|
137
|
-
<td>7. Select <b>Add Value Condition</b></td>
|
|
138
|
-
<td>8. Choose <b>Inverter AC Consumption</b> as characteristic and elect <b>>=</b> a desired value</b></td>
|
|
139
|
-
</tr>
|
|
140
|
-
<tr>
|
|
141
|
-
<td><img src="images/automation/automation_7.png"></td>
|
|
142
|
-
<td><img src="images/automation/automation_8.png"></td>
|
|
143
|
-
</tr>
|
|
144
|
-
<tr>
|
|
145
|
-
<td>9. Click <b>Next</b></td>
|
|
146
|
-
<td>10. If no scene exists, click <b>Add Scene</b></td>
|
|
147
|
-
</tr>
|
|
148
|
-
<tr>
|
|
149
|
-
<td><img src="images/automation/automation_9.png"></td>
|
|
150
|
-
<td><img src="images/automation/automation_10.png"></td>
|
|
151
|
-
</tr>
|
|
152
|
-
<tr>
|
|
153
|
-
<td>11. Click <b>Add Actions</b></td>
|
|
154
|
-
<td>12. Select the accessory to be controlled (in this case <b>Garden Pool Outlet</b> will be turned <b>ON</b>)</td>
|
|
155
|
-
</tr>
|
|
156
|
-
<tr>
|
|
157
|
-
<td><img src="images/automation/automation_11.png"></td>
|
|
158
|
-
<td><img src="images/automation/automation_12.png"></td>
|
|
159
|
-
</tr>
|
|
160
|
-
<tr>
|
|
161
|
-
<td>13. Click <b>Next</b></td>
|
|
162
|
-
<td>14. Name your scene and click <b>Done</b></td>
|
|
163
|
-
</tr>
|
|
164
|
-
<tr>
|
|
165
|
-
<td><img src="images/automation/automation_13.png"></td>
|
|
166
|
-
<td><img src="images/automation/automation_14.png"></td>
|
|
167
|
-
</tr>
|
|
168
|
-
<tr>
|
|
169
|
-
<td>15. Click <b>Next</b></td>
|
|
170
|
-
<td>16. Name your rule and click <b>Done</b></td>
|
|
171
|
-
</tr>
|
|
172
|
-
<tr>
|
|
173
|
-
<td><img src="images/automation/automation_15.png"></td>
|
|
174
|
-
<td><img src="images/automation/automation_16.png"></td>
|
|
175
|
-
</tr>
|
|
176
|
-
</table>
|
|
177
|
-
|
|
178
|
-
# TO DO
|
|
179
|
-
|
|
180
|
-
Next planned plugin releases should include:
|
|
181
|
-
|
|
182
|
-
- [X] **Inverter AC** to include Yield Energy
|
|
183
|
-
- [X] Consumption history through the [fakegato-history](https://github.com/simont77/fakegato-history) module
|
|
184
|
-
- [x] Enable support for "pure" Home App accessories (power meters will be exposed as Ambient Light sensors)
|
|
185
|
-
- [x] Add "smooth" accessories for power meters (compensating for sporadic scenarios like cloud a passing)
|
|
186
|
-
- [x] Support for multiple inverters
|
|
187
|
-
- [ ] Accessories for battery state and consumptions (work in progress)
|
|
1
|
+
|
|
2
|
+
<table cellspacing="0" cellpadding="0">
|
|
3
|
+
<tr>
|
|
4
|
+
<td align="center"><img src="https://github.com/homebridge/branding/raw/master/logos/homebridge-wordmark-logo-vertical.png" width="150"></td>
|
|
5
|
+
<td align="center"><img src="https://www.solaxpower.com/wp-content/uploads/2020/03/weblogo5.png" width="300"></td>
|
|
6
|
+
<tr>
|
|
7
|
+
</table>
|
|
8
|
+
|
|
9
|
+
# Solax Cloud Plugin for Homebridge
|
|
10
|
+
|
|
11
|
+
  [](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)
|
|
12
|
+
|
|
13
|
+
|
|
14
|
+
The Solax Cloud Plugin for [Homebridge](https://homebridge.io/) was created as a platform plugin to gather data exposed by Solax inverters to the cloud through the [Solax Cloud API](https://www.eu.solaxcloud.com/phoebus/resource/files/userGuide/Solax_API_for_End-user_V1.0.pdf).
|
|
15
|
+
|
|
16
|
+
Now with **support for multiple inverters**!
|
|
17
|
+
|
|
18
|
+
As HomeKit is still clueless about what a solar panel is, this plugin exposes a set of standard HomeKit accessories though Homebridge for each configured inverter that will allow interacting and automating your smart home based on the data made available from the Solax platform:
|
|
19
|
+
|
|
20
|
+
- **PV** (PV outlet with power consumption)
|
|
21
|
+
- **AC** (Inverter AC outlet with power and total energy consumptions)
|
|
22
|
+
- **To Grid** (Inverter to Grid outlet with power consumption)
|
|
23
|
+
- **To House** (Inverter to House outlet with power consumption)
|
|
24
|
+
- **From Grid** (Grid to House outlet with power consumption)
|
|
25
|
+
- **Update** (Motion sensor)
|
|
26
|
+
|
|
27
|
+
<img src="images/plugin-accessories-home.png" width="50%" height="50%">
|
|
28
|
+
|
|
29
|
+
Please note that additional accessories are created by default with smooth power consumption curves (by applying either a simple or exponential moving average to the power series). This prevents sporadic events like a cloud passing by to have an immediate affect on provided meters.
|
|
30
|
+
|
|
31
|
+
## Required information
|
|
32
|
+
|
|
33
|
+
For this plugin to work, two critical pieces of information are required from Solax Cloud:
|
|
34
|
+
|
|
35
|
+
- **Token ID**: Solax users can get inverter information through the granted tokenID. You need to obtain your tokenID on the API page of Solaxcloud.
|
|
36
|
+
- **SN**: Registration No (communication module SN) for each desired inverter.
|
|
37
|
+
|
|
38
|
+
## Installation
|
|
39
|
+
|
|
40
|
+
This plugin is supported under Homebridge. It is highly recommended that you use Homebridge Config UI X to install and configure this plugin.
|
|
41
|
+
|
|
42
|
+
### Manual Installation
|
|
43
|
+
|
|
44
|
+
Install this plugin using: `sudo npm install -g homebridge-solaxcloud-api`.
|
|
45
|
+
Edit `config.json` manually to add your Solax inverters. See below for instructions on that.
|
|
46
|
+
|
|
47
|
+
## Platform configuration
|
|
48
|
+
|
|
49
|
+
Minimal platform configuration is depicted by the example configuration file below:
|
|
50
|
+
|
|
51
|
+
```json
|
|
52
|
+
{
|
|
53
|
+
"platforms": [
|
|
54
|
+
{
|
|
55
|
+
"platform": "SolaxCloudAPI",
|
|
56
|
+
"tokenId": "20200722185111234567890",
|
|
57
|
+
"inverters": [
|
|
58
|
+
{
|
|
59
|
+
"name": "Solax",
|
|
60
|
+
"sn": "ABCDEFGHIJ"
|
|
61
|
+
}
|
|
62
|
+
],
|
|
63
|
+
}
|
|
64
|
+
]
|
|
65
|
+
}
|
|
66
|
+
```
|
|
67
|
+
Configuration parameters are described on the table below:
|
|
68
|
+
|
|
69
|
+
| **Parameter** | **Type** | **Description** | **Default** | **Mandatory?** |
|
|
70
|
+
| ------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------- | -------------:| :------------: |
|
|
71
|
+
| `platform` | string | Platform name (must be SolaxCloudAPI) | - | Y |
|
|
72
|
+
| `tokenId` | string | Users get information from Solax Cloud through the granted tokenID. Please obtain your tokenID on the API page of Solax Cloud | - | Y |
|
|
73
|
+
| `inverters` | array | Array of configured inverters as objects with `{ name: string, sn: string }`, where `name` is the inverter name, used as prefix for accessory naming and `sn` is the inverter registration no. (inverter module SN). | - | Y |
|
|
74
|
+
| `pollingFrequency` | number | Plugin data polling frequency from Solax Cloud (in seconds) | 300 | N |
|
|
75
|
+
| `smoothingMeters` | boolean | Whether to create additional meters by smoothing raw values from Solax Cloud | true | N |
|
|
76
|
+
| `smoothingMethod` | string | Statistical method to use for smoothing raw values from Solax Cloud (simple or exponential moving average - "sma" or "ema") | "sma" | N |
|
|
77
|
+
| `pureHomeApp` | boolean | Whether to create meters as standard accessories that can be used on the Home App (power will show as ambient light sensors) | false | N |
|
|
78
|
+
|
|
79
|
+
**NOTE:** The `pollingFrequency` parameter defaults to 300 seconds, since Solax inverters update cloud data every 5 minutes.
|
|
80
|
+
|
|
81
|
+
Configuration through the the use of [Homebridge UI](https://github.com/oznu/homebridge-config-ui-x) plugin is also available and recommended:
|
|
82
|
+
|
|
83
|
+
<img src="images/homebridge-ui.png" width="100%" height="100%">
|
|
84
|
+
|
|
85
|
+
## Non-standard characteristics
|
|
86
|
+
|
|
87
|
+
Non-standard accessory characteristics are available through the use of [Eve for HomeKit app](https://apps.apple.com/us/app/eve-for-homekit/id917695792) you may download from the App Store.
|
|
88
|
+
|
|
89
|
+
This will allow some non-standard characteristics to be visible along with its historical data (like power or total energy consumption), as depicted in the image below:
|
|
90
|
+
|
|
91
|
+
<img src="images/plugin-outlet-consumption.png" width="50%" height="50%">
|
|
92
|
+
|
|
93
|
+
If you want to rely solely on the native Home App, please enable the `pureHomeApp` config setting. In this case, power consumption on each meter will be exposed as an Ambient Light Sensor, as shown below (minimum value for an Ambient Light Sensor is 0.1 lux):
|
|
94
|
+
|
|
95
|
+
<img src="images/plugin-accessories-home-pure.png" width="50%" height="50%">
|
|
96
|
+
|
|
97
|
+
# Automation
|
|
98
|
+
|
|
99
|
+
Automation can be achieved with the help of the virtual **Update** motion sensor that was specifically tailored for this effect and which is available for each inverter. This motion sensor will be triggered whenever inverter data gets updated from the Solax Cloud API (according to what is defined on the `pollingFrequency` configuration setting).
|
|
100
|
+
|
|
101
|
+
<img src="images/plugin-accessories-eve.png" width="50%" height="50%">
|
|
102
|
+
|
|
103
|
+
Motion is detected by the **Update** motion sensor whenever there is newly fetched inverter data from Solax Cloud. Using this sensor as a trigger combined with power and energy data from the virtual outlets enumerated above forms the basic building blocks for defining an automation.
|
|
104
|
+
|
|
105
|
+
## Automation example
|
|
106
|
+
|
|
107
|
+
Since automations are probably going to be dependent on the non-standard **Consumption** characteristics from the virtual outlets, these must created by using the Eve App.
|
|
108
|
+
|
|
109
|
+
As an automation example, let's imagine we want to turn a pool heater pump on whenever the inverter AC power is greater than a specific figure (in Watt):
|
|
110
|
+
|
|
111
|
+
<table cellspacing="0" cellpadding="0">
|
|
112
|
+
<tr>
|
|
113
|
+
<td width="50%">1. Under Automation, select <b>Rules</b></td>
|
|
114
|
+
<td width="50%">2. Click <b>Next</b></td>
|
|
115
|
+
</tr>
|
|
116
|
+
<tr>
|
|
117
|
+
<td><img src="images/automation/automation_1.png"></td>
|
|
118
|
+
<td><img src="images/automation/automation_2.png"></td>
|
|
119
|
+
</tr>
|
|
120
|
+
<tr>
|
|
121
|
+
<td>3. Click <b>Add Trigger</b></td>
|
|
122
|
+
<td>4. Select <b>Motion</b> as trigger type</td>
|
|
123
|
+
</tr>
|
|
124
|
+
<tr>
|
|
125
|
+
<td><img src="images/automation/automation_3.png"></td>
|
|
126
|
+
<td><img src="images/automation/automation_4.png"></td>
|
|
127
|
+
</tr>
|
|
128
|
+
<tr>
|
|
129
|
+
<td>5. Select the Solax <b>Update</b> motion detector and set <b>Motion</b> as trigger</td>
|
|
130
|
+
<td>6. Click <b>Next</b></td>
|
|
131
|
+
</tr>
|
|
132
|
+
<tr>
|
|
133
|
+
<td><img src="images/automation/automation_5.png"></td>
|
|
134
|
+
<td><img src="images/automation/automation_6.png"></td>
|
|
135
|
+
</tr>
|
|
136
|
+
<tr>
|
|
137
|
+
<td>7. Select <b>Add Value Condition</b></td>
|
|
138
|
+
<td>8. Choose <b>Inverter AC Consumption</b> as characteristic and elect <b>>=</b> a desired value</b></td>
|
|
139
|
+
</tr>
|
|
140
|
+
<tr>
|
|
141
|
+
<td><img src="images/automation/automation_7.png"></td>
|
|
142
|
+
<td><img src="images/automation/automation_8.png"></td>
|
|
143
|
+
</tr>
|
|
144
|
+
<tr>
|
|
145
|
+
<td>9. Click <b>Next</b></td>
|
|
146
|
+
<td>10. If no scene exists, click <b>Add Scene</b></td>
|
|
147
|
+
</tr>
|
|
148
|
+
<tr>
|
|
149
|
+
<td><img src="images/automation/automation_9.png"></td>
|
|
150
|
+
<td><img src="images/automation/automation_10.png"></td>
|
|
151
|
+
</tr>
|
|
152
|
+
<tr>
|
|
153
|
+
<td>11. Click <b>Add Actions</b></td>
|
|
154
|
+
<td>12. Select the accessory to be controlled (in this case <b>Garden Pool Outlet</b> will be turned <b>ON</b>)</td>
|
|
155
|
+
</tr>
|
|
156
|
+
<tr>
|
|
157
|
+
<td><img src="images/automation/automation_11.png"></td>
|
|
158
|
+
<td><img src="images/automation/automation_12.png"></td>
|
|
159
|
+
</tr>
|
|
160
|
+
<tr>
|
|
161
|
+
<td>13. Click <b>Next</b></td>
|
|
162
|
+
<td>14. Name your scene and click <b>Done</b></td>
|
|
163
|
+
</tr>
|
|
164
|
+
<tr>
|
|
165
|
+
<td><img src="images/automation/automation_13.png"></td>
|
|
166
|
+
<td><img src="images/automation/automation_14.png"></td>
|
|
167
|
+
</tr>
|
|
168
|
+
<tr>
|
|
169
|
+
<td>15. Click <b>Next</b></td>
|
|
170
|
+
<td>16. Name your rule and click <b>Done</b></td>
|
|
171
|
+
</tr>
|
|
172
|
+
<tr>
|
|
173
|
+
<td><img src="images/automation/automation_15.png"></td>
|
|
174
|
+
<td><img src="images/automation/automation_16.png"></td>
|
|
175
|
+
</tr>
|
|
176
|
+
</table>
|
|
177
|
+
|
|
178
|
+
# TO DO
|
|
179
|
+
|
|
180
|
+
Next planned plugin releases should include:
|
|
181
|
+
|
|
182
|
+
- [X] **Inverter AC** to include Yield Energy
|
|
183
|
+
- [X] Consumption history through the [fakegato-history](https://github.com/simont77/fakegato-history) module
|
|
184
|
+
- [x] Enable support for "pure" Home App accessories (power meters will be exposed as Ambient Light sensors)
|
|
185
|
+
- [x] Add "smooth" accessories for power meters (compensating for sporadic scenarios like cloud a passing)
|
|
186
|
+
- [x] Support for multiple inverters
|
|
187
|
+
- [ ] Accessories for battery state and consumptions (work in progress)
|
package/config.sample
CHANGED
|
@@ -1,15 +1,15 @@
|
|
|
1
|
-
{
|
|
2
|
-
"platforms": [
|
|
3
|
-
{
|
|
4
|
-
"platform": "SolaxCloudAPI",
|
|
5
|
-
"tokenId": "20200722185111234567890",
|
|
6
|
-
inverters: [
|
|
7
|
-
{
|
|
8
|
-
"name": "My Solax",
|
|
9
|
-
"sn": "ABCDEFGHIJ"
|
|
10
|
-
}
|
|
11
|
-
],
|
|
12
|
-
"pollingFrequency": 300
|
|
13
|
-
}
|
|
14
|
-
]
|
|
1
|
+
{
|
|
2
|
+
"platforms": [
|
|
3
|
+
{
|
|
4
|
+
"platform": "SolaxCloudAPI",
|
|
5
|
+
"tokenId": "20200722185111234567890",
|
|
6
|
+
inverters: [
|
|
7
|
+
{
|
|
8
|
+
"name": "My Solax",
|
|
9
|
+
"sn": "ABCDEFGHIJ"
|
|
10
|
+
}
|
|
11
|
+
],
|
|
12
|
+
"pollingFrequency": 300
|
|
13
|
+
}
|
|
14
|
+
]
|
|
15
15
|
}
|
package/package.json
CHANGED
|
@@ -2,8 +2,8 @@
|
|
|
2
2
|
"private": false,
|
|
3
3
|
"displayName": "Homebridge Solax Cloud API",
|
|
4
4
|
"name": "homebridge-solaxcloud-api",
|
|
5
|
-
"version": "2.1.2
|
|
6
|
-
"description": "Integrates solar production info using public Solax Cloud API into
|
|
5
|
+
"version": "2.1.2",
|
|
6
|
+
"description": "Integrates solar production info using public Solax Cloud API into Homebridge accessories.",
|
|
7
7
|
"license": "Apache-2.0",
|
|
8
8
|
"repository": {
|
|
9
9
|
"type": "git",
|