Custom Component: IoTaWatt Energy Monitor integration

crzykidd · January 2, 2022, 5:39am

That seems weird, either way I got the HACS version installed and working. Much better. Just something about having the entities tied to the device in the UI makes it easier to find stuff

crzykidd · January 3, 2022, 1:14am

Couple things.

It would be nice if the device name was picked up from iotawatt. It would also be nice if the device name was in the entity name. So sensor.iotawatt_heatpump instead of just sensory.heatpump.

Also what is the difference between the _wh counter and the _wh_Accumuleted counter? These look to be both accumulative from what I can tell.

Is there a good way to convert the counters to kWh vs Wh?

Awesome addition! Thanks,

jyavenard · January 3, 2022, 3:22am

It used to be like that. The HA dev team didn’t approve it and we had to remove it.

Create a template sensor and divide by 1000

crzykidd · January 3, 2022, 3:42am

That is weird, and since I have iotawatt already setup I can’t easily rename the existing items.

Thanks got a template sensor setup.

jyavenard · January 3, 2022, 4:31am

The _Wh sensors are reading the energy value starting from the 1st January of the year.
They aren’t suitable for calculating export/import value

The _accumulated ones are the energy value read since the iotawatt sensors were first setup.
They never reset

TasR · January 16, 2022, 10:42am

Does anyone know if there is a way to reduce the polling interval for one or more IotaWatt measurements (IotaWatt inputs or outputs)? I would like to setup an HA automation that is triggered by a certain power level on an IotaWatt sensor, but for this use case (in my shed, turn on the power to the dust extractor when the saw starts) to be effective, HA would need to see the power change in less than a few seconds rather than wait 30 seconds or more.

Using Core IotaWata integration

OzGav · January 16, 2022, 11:23am

Don’t think it is possible at the moment Refresh Rate · Issue #3 · gtdiehl/iotawatt_ha · GitHub

hagak · January 16, 2022, 12:55pm

Since iotawatt publishes to mqtt, you could use NodeRed to monitor the same MQTT and trigger your automation within NodeRed.

NEVERMIND - Ignore above not sure why i was thinking iotawatt published to MQTT. Have not had my coffee yet.

jyavenard · January 17, 2022, 2:11am

You’ll have to modify the iotawatt integration ; and change that line:

github.com

home-assistant/core/blob/a657d34c920a0a649e8eae628194291361366aca/homeassistant/components/iotawatt/coordinator.py#L32


      
          
          api: Iotawatt | None = None
          
          def __init__(self, hass: HomeAssistant, entry: ConfigEntry) -> None:
              """Initialize IotaWattUpdater object."""
              self.entry = entry
              super().__init__(
                  hass=hass,
                  logger=_LOGGER,
                  name=entry.title,
                  update_interval=timedelta(seconds=30),
              )
          
              self._last_run: datetime | None = None
          
          def update_last_run(self, last_run: datetime) -> None:
              """Notify coordinator of a sensor last update time."""
              # We want to fetch the data from the iotawatt since HA was last shutdown.
              # We retrieve from the sensor last updated.
              # This method is called from each sensor upon their state being restored.
              if self._last_run is None or last_run > self._last_run:

You will get quite a bit of warnings when running as the _accumulated sensors store data in block of 30s and it will complain that it’s been queried too often ; but all the other sensors will be updated as expected.

amosyuen · January 23, 2022, 10:05am

I’ve created a pull request Add config option to iotawatt for scan_interval by amosyuen · Pull Request #64755 · home-assistant/core · GitHub to add an option to customize the update interval.

jyavenard · January 23, 2022, 10:11am

You will need to change the interval set for the update interval when querying the interval too:

github.com

home-assistant/core/blob/a657d34c920a0a649e8eae628194291361366aca/homeassistant/components/iotawatt/coordinator.py#L65

    
      
              try:
                  is_authenticated = await api.connect()
              except CONNECTION_ERRORS as err:
                  raise UpdateFailed("Connection failed") from err
          
          
    if not is_authenticated:
                  raise UpdateFailed("Authentication error")
          
          
    self.api = api
          
          
await self.api.update(lastUpdate=self._last_run)
          self._last_run = None
          return self.api.getSensors()

from there:

github.com

gtdiehl/iotawattpy/blob/c7584058676aaebcbc95e8d0f647ba76c8de37c8/iotawattpy/iotawatt.py#L72

    
      
              else:
                  results.raise_for_status()
          
          
"""Returns an array of Sensor objects"""
          
          
def getSensors(self):
              return self._sensors
          
          
"""Retrieves sensor data and updates the Sensor objects"""
          
          
async def update(self, timespan=30, lastUpdate=None):
              if not self._getMACFlag:
                  await self.connect()
                  self._getMACFlag = True
              await self._refreshSensors(timespan, lastUpdate)
          
          
"""Retrieve the last update time"""
          
          
def getLastUpdateTime(self):
              return self._lastUpdateTime

set timespan=number_seconds

amosyuen · January 23, 2022, 10:42am

Abandoned the PR as per comment from frenck. We should be using a periodic automation that calls homeassistant.update_entity on one of the entities and disable polling on the integration. I’ve verified that this works.

TasR · January 25, 2022, 10:57am

I have tried this, with update_entity called every 5 seconds, but the logs show the automation only being triggered approximately every 30 seconds or so anyway. Is there a trick to getting it to actually run more frequently?

grantc · January 30, 2022, 8:07am

Hi - been getting this logged error for some time now and it does not appear to be a common problem.

Any clues would be appreciated. Connectivity errors maybe?

2022-01-30 14:21:48 ERROR (MainThread) [homeassistant.components.iotawatt.coordinator] Unexpected error fetching 192.168.2.162 data: 'NoneType' object has no attribute 'text'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/components/iotawatt/coordinator.py", line 65, in _async_update_data
    await self.api.update(lastUpdate=self._last_run)
  File "/usr/local/lib/python3.9/site-packages/iotawattpy/iotawatt.py", line 76, in update
    await self._refreshSensors(timespan, lastUpdate)
  File "/usr/local/lib/python3.9/site-packages/iotawattpy/iotawatt.py", line 161, in _refreshSensors
    query = query.text
AttributeError: 'NoneType' object has no attribute 'text'

OzGav · January 30, 2022, 10:11am

There has been an open issue on GitHub about this for some time…… AttributeError: 'NoneType' object has no attribute 'text' · Issue #6 · gtdiehl/iotawattpy · GitHub

jyavenard · January 31, 2022, 6:09am

that’s just a waning log.
The _accumulated sensor measures the data by a block of 30s at a minimum, so it’s easier to query the new data accumulated from the last read.

There’s a warning if you call the update too often as there would be nothing to read.

For now edit iotawatt.py in your python folder and remove those lines:

github.com

gtdiehl/iotawattpy/blob/c7584058676aaebcbc95e8d0f647ba76c8de37c8/iotawattpy/iotawatt.py#L292-L294


      
          LOGGER.warning(
              "Nothing to query, update() called too soon, must wait {timespan}"
          )

Or maybe better, drop the log level to not include warning but info only

TasR · February 2, 2022, 2:13am

I still get that error all the time. It doesn’t seem to have an impact that I know of, but it is mildly annoying to see all the time.

TasR · February 2, 2022, 2:14am

Thanks, I will look to see if can make that edit, though not sure I can when using HASSIO?

jyavenard · February 2, 2022, 3:06am

You may be able to change the log level in the configuration.yaml
I think that will be enough

hume-github · February 6, 2022, 10:30pm

So what’s the procedure to recover when the iotawatt readings go negative? I had the iotawatt set up, and the energy dashboard accumulating data, and it was great. But we just finished a 47h power outage thanks to an ice storm, and when HA came back up it was reporting that I’d used -880 kWh today.

I tried deleting all grid and individual devices from the energy dashboard and adding them back in, hoping it would reset the “now” value… but no, they come back in with the massive negative values.

Am I going to need to delete the integration (default HA, nothing shows up in HACS) and add it back in to recover?