To reduce the heap usage it is necessary to send the inverters one by one instead of a huge response. A simple call to `/api/livedata/status` returns just some very general information. If detailed inverter information are required the inverter serial number has to appended `?inv=<serial number>`. The websocket also returns only one inverter at a time. It as to be assembled at client side. |
||
|---|---|---|
| .. | ||
| .vscode | ||
| public | ||
| src | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| env.d.ts | ||
| index.html | ||
| package.json | ||
| README.md | ||
| tsconfig.config.json | ||
| tsconfig.json | ||
| vite.config.ts | ||
| yarn.lock | ||
OpenDTU web frontend
You can run the webapp locally with yarn dev. If you enter the IP of your ESP in the vite.config.ts beforehand, all api requests will even be proxied to the real ESP. Then you can develop the webapp as if it were running directly on the ESP. The yarn dev also supports hot reload, i.e. as soon as you save a vue file, it is automatically reloaded in the browser.
Project Setup
yarn install
Compile and Hot-Reload for Development
yarn dev
Type-Check, Compile and Minify for Production
yarn build
Lint with ESLint
yarn lint