--- title: "myPV" description: "myPV is a Marketplace integration for Home Assistant. It has 546 installs sharing analytics, works locally and was last updated September 16, 2026." canonical: "https://vulpo.app/integrations/marketplace/dneprojects-mypv" url: "https://vulpo.app/integrations/marketplace/dneprojects-mypv.md" last-updated: "2026-10-22" version: "1.4" --- # myPV > myPV is a Marketplace integration for Home Assistant. It has 546 installs sharing analytics, works locally and was last updated September 16, 2026. myPV is a custom integration that connects Home Assistant to myPV heating devices over the local network. It adds sensors, binary sensors, numbers, switches, buttons, a select for control type, and firmware update entities. Heating power can be set through a number entity, and the device's own PID controller can regulate from a grid power reading that automations write repeatedly. A boost mode follows a weekly schedule to hold a minimum temperature, and it can be started or stopped with buttons. Energy consumption entities report use per day, per month and in total, and an action resets them. Devices are found automatically on the same subnet, with manual entry of the IP address in the UI as a fallback. Automatic summary of the README and code of dneprojects/mypv. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=dneprojects&repository=mypv&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=dneprojects&repository=mypv&category=integration) ## Supports - **Works locally**: Talks to your devices on your own network. No vendor cloud in between. - **Found by itself**: Home Assistant spots it on the network and offers to add it. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Connect to myPV device - **IP address** ### myPV authentication - **Password** Also asked when signing in again. Texts from the code of [dneprojects/mypv](https://github.com/dneprojects/mypv). ## Entities - **Binary sensors**: Alarm relais, Block active, Boost relais, Night flag, Out 2, Out 3, Relais, Schicht, wp\_flag - **Buttons**: Start Boost, Stop Boost - **Numbers**: Boost Min Temperature, Control Value Timeout, PID Power, PID Power AC9, PID Power AC9s, PID Power ELWA-2, Power, Power AC9, Power AC9s, Power ELWA-2, Target Grid Power, Target Temperature - **Selects**: Control type - **Sensors**: Encryption, Acthor 9 Power Unit Update State, Acthor 9s, Boost Power, Control source, Control state, Control Unit Fw Version, Control Unit Update State, Current L1, Current L2, Current L3, Date, and 112 more - **Switches**: Enable Boost Mode, Enable Device, Enable HTTP - **Updates**: Co-controller Firmware, Control Unit Firmware, Power Unit Firmware, Power Unit Firmware Acthor 9 ## From the README > - Automatic discovery of devices. > - The integration is written to support multiple devices. Meanwhile, it has beeny tested with ELWA, ELWA 2, AC-THOR 1, AC-THOR 9s, and SOLTHOR-DC. For multiple devices, please use the configuration… > - It offers binary sensors and sensors for all data points provided by the myPV devices. > - The heating power can be set manually by an input number between 0 and 3000 W (3600 W for ELWA 2, 9000 W for AC THOR 9s). This will turn on the heater for a predefined time period… > - Alternatively, the device's own PID controller can do the regulating. The PID power value is not a setpoint but a measurement: it is the power at the grid connection point, positive for surplus and… > - In order to enable both control entities, the control type has to be set to "html" via web or cloud setup. Otherwise, only sensor data points will be exposed as Home Assistant entities. The Boost… > - Three energy consumption entities show the amount of spent energy per day, per month, or total. By means of an action called mypv.reset\_energy\_sensor each one of these cumulated values can be reset… From the README of [dneprojects/mypv](https://github.com/dneprojects/mypv#readme), [Apache License 2.0](https://spdx.org/licenses/Apache-2.0.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Energy](https://vulpo.app/integrations/category/energy.md), Solar and batteries - Number: 546 installs sharing analytics; 50 GitHub stars - Connection: Works locally - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v1.7.7, last updated September 16, 2026 - Domain: `mypv` - Source: - Issues: In Vulpo: Quick Toggle card, Button card, Select card, Chart card, Apple Watch, Control Center Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/dneprojects-mypv --- - HTML version of this page: https://vulpo.app/integrations/marketplace/dneprojects-mypv - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml