So after an hour of customization, dashboard updates and creating template sensors to deal with the fact that the core integration outputs can’t be edited I’m left with this error that can not be fixed:
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:744
integration: Sensor (documentation, issues)
First occurred: 19:13:23 (5 occurrences)
Last logged: 19:13:23
Platform iotawatt does not generate unique IDs. ID A848FAF1BD3C-input-1-WattHours already exists - ignoring sensor.grid_wh
Platform iotawatt does not generate unique IDs. ID A848FAF1BD3C-input-2-WattHours already exists - ignoring sensor.solar_energy
Platform iotawatt does not generate unique IDs. ID A848FAF1BD3C-input-5-WattHours already exists - ignoring sensor.upstairs_hp_energy
Platform iotawatt does not generate unique IDs. ID A848FAF1BD3C-input-6-WattHours already exists - ignoring sensor.downstairs_hp_energy
Platform iotawatt does not generate unique IDs. ID A848FAF1BD3C-input-7-WattHours already exists - ignoring sensor.stove_energy
Not even by editing the core entity registry.
And performing a power outage test produces this mess:
If you create calculated sensors in the IoTaWatt (called “outputs”) they will not show up as entities on the IoTaWatt device page. They are still available as entities in home assistant though. You can see them in Developer Tools → States or the Devices & Services Entities tab. The reason for this is that the entities do not have a unique id. This does not stop you using them in the energy dashboard or anywhere else in Home Assistant (e.g. automations). There is a 3rd part integration that does list the outputs on the IoTaWatt device page but it has other issues - like not resetting exactly at midnight which messes up the energy dashboard. I found no good way to fix this. So just use the core integration and know to find your outputs in the entities list.
If you have a power outage the energy sensors will glitch and cause massive energy spikes in the Energy dashboard. You can not fix this with template sensors. The only solution is to use a small DC UPS so that the IoTaWatt is always powered. e.g. this: https://www.wagneronline.com.au/5v-9v-12v-38-5wh-dc-in-line-mini-ups/power-12vdc/power-lighting/ups5912-101087/1007502/pd/ will keep the IoTaWatt powered for more than a day without mains power. If you have a power outage longer than this you have bigger problems to worry about.
There is an ESP32 IoTaWatt in development. Good progress is being made but there is no release date information or even a guarantee this will ever become a commercial product. You can read about it here: ESP32 version 0.3 - Bob's Blog - IoTaWatt User Community
Since switching to the core integration and using the DC UPS I have been very happy with my IoTaWatt. It agrees with my billing information to better than 2%.
New IOTAWatt user here. Got it all configured in the IOTAWatt web application, but cant seem to get HA to find it in the new integration. Tried putting in the IOTAWatt host name and/or IP manually but get a “Failed to Connect” message in HA. Any advice on how to get the integration working? Thanks
Thanks Tom for the quick reply. Unfortuntately not picking it up. router clearly sees IotaWatt, provides the IP, I place it in the URL string through the integration prompt in HA, and “Failed to Connect”. Looking into other routes like proxmox VM or LXC for EmonCMS.
Nothing out of the ordinary. Standard network. No VLANs setup. All on same wireless network (HA hosted on Proxmox, device is hardwired). On the HA side I’m running HA Core 2024.7.1, Supervisor 2024.06.2, Operating System12.4.
Thanks, somehow got it working. Tried multiple times with just the IP. Reset HA. Tried again and it took. Not sure. Now to figure out the best way to display data. Thanks Tom!
I’m looking into home energy monitoring and was considering iotawatt until finding the integration to HA. Would you still not recommend it vs other solutions?