2021.8.0: Feel the energy ⚡️

Hi,
When configuring the energy dashboard for my fronius, I can only get this one entity to show up:
Energy total Fronius Inverter 1 http://192.1xx.xxx.xxx

How do I get my other sensors to show in the drop down dialog?

I’m running the latest SW, and HACS Fronius already and they are working great.
Thanks in advance
regards

I have also been having issues with the HomeKit integration. Last working version was core-2021.7.4

I am using LocalTuya and Lightgroups - all of which work in 2021.7.4 fine.

Symptoms:

  • Additional devices in HomeKit relating to brightness and color temp. (none of which appear to be filter-able in the Plug-in).
  • Unexpected initial colour and brightness for the existing (original) light group objects in HomeKit.
  • When a lightgroup is activated, the linked devices are also activated but the behaviour does not seem to be entirely predictable / reliable.
  • Seems to only be affecting my light groups

Interim fix is to rollback.

From the #integrations#homekit discord channel - others are also experiencing this issue.

If you are using the built-in Fronius integration you need to add the meter sensor_type (assuming you have a Fronius Smart Meter). A meter at the feed-in point will provide import/export as sensors that include “consumed” and “produced”.

If you are using HACS Fronius I’m not sure how to get the meter information for the energy dashboard.

Why TP-link consumption appear negative while other stay positive

Would be great to view the whole month in noe tab, and also with the cost

Do you have separate sensors for generation and export or have you used the same sensor.

When you look at the TPLink sensor in HA does it come in with a “-” at the beginning in the state.

Three separate sensors.
“consumed” and “produced” from the smart meter for import/export. “generation” from the inverter. All part of the Fronius integration.

It looks like there may be a bug somewhere as the export sum changes in the recorder database even though the sensor state remains the same.

MariaDB [homeassistant]> select sm.statistic_id, s.start, s.state, s.sum FROM statistics_meta sm, statistics s WHERE s.metadata_id=sm.id AND s.metadata_id=11 AND s.start>='2021-08-09 07:00:00';
+------------------------------------------------------------------+----------------------------+---------+--------+
| statistic_id                                                     | start                      | state   | sum    |
+------------------------------------------------------------------+----------------------------+---------+--------+
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 07:00:00.000000 | 22004.9 | 18.831 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 08:00:00.000000 | 22005.2 | 19.095 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 09:00:00.000000 | 22005.2 | 19.059 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 10:00:00.000000 | 22005.2 | 19.023 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 11:00:00.000000 | 22005.2 | 18.987 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 12:00:00.000000 | 22005.2 | 18.951 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 13:00:00.000000 | 22005.2 | 18.915 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 14:00:00.000000 | 22005.2 | 18.879 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 15:00:00.000000 | 22005.2 | 18.843 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 16:00:00.000000 | 22005.2 | 18.807 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 17:00:00.000000 | 22005.2 | 18.771 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 18:00:00.000000 | 22005.2 | 18.735 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 19:00:00.000000 | 22005.2 | 18.699 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 20:00:00.000000 | 22005.2 | 18.663 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 21:00:00.000000 | 22005.2 | 18.627 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 22:00:00.000000 | 22005.2 | 18.591 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-09 23:00:00.000000 | 22005.2 | 18.555 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-10 00:00:00.000000 | 22005.2 | 18.519 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-10 01:00:00.000000 | 22005.2 | 18.483 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-10 02:00:00.000000 | 22005.4 | 18.635 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-10 03:00:00.000000 | 22005.5 | 18.768 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-10 04:00:00.000000 | 22005.8 | 19.046 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-10 05:00:00.000000 | 22005.8 | 19.087 |
| sensor.energy_real_produced_fronius_meter_0_http_192_168_xxx_xxx | 2021-08-10 06:00:00.000000 | 22005.9 | 19.184 |
+------------------------------------------------------------------+----------------------------+---------+--------+
24 rows in set (0.001 sec)

(database times are UTC, dashboard is in local time - UTC+8)

No that is the weird part, i was thinking it was by the use of the word “consumption”

so i try to recreate that with templates

i even define

      state_class: measurement
      device_class: energy

but those stay on the positive side

the only difference is that now TP-LINK sensors are created by Nabu-casa Dev’s

This issue was resolved in version 2021.8.5.

there still something strange with those graphs

image
if i click on the last one i got the data of the top one

image

i wonder where that -1.63 comming from

It seems cost sensors are reset to zero everytime you restart Home Assistant. I cannot imagine this is desired behaviour?

Peak:

Off-peak:

Trying to upgrade to 2021.8.5 from 2021.8.4
Using HA Core & Python 3.9.1, don’t use Nabu Casa
Home Assistant eventually times out and not usable.
Restore to 2021.8.4, works fine.

Seeing tons of error messages like this:

2021-08-10 09:43:41 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.9/site-packages/aiohttp/web_protocol.py”, line 422, in _handle_request
resp = await self._request_handler(request)
File “/srv/homeassistant/lib/python3.9/site-packages/aiohttp/web_app.py”, line 499, in _handle
resp = await handler(request)
File “/srv/homeassistant/lib/python3.9/site-packages/aiohttp/web_middlewares.py”, line 119, in impl
return await handler(request)
File “/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/security_filter.py”, line 60, in security_filter_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.9/site-packages/homeassistant/components/http/forwarded.py”, line 77, in forwarded_middleware
if remote is not None and remote.is_cloud_request.get():
AttributeError: module ‘hass_nabucasa.remote’ has no attribute ‘is_cloud_request’

Any ideas how to correct?

3 Likes

I have exactly the same problem after an attempt to upgrade to 2021.8.5. Also had to downgrade back.

I like the new gauges with the needles very much! :slight_smile:
They give the chart a more professional aspect!

Anyone with the Aeotec Siren 6: which entities should I be seeing? It took a very long time and more than a few included efforts to get only 1 siren entity and nothing else.

Besides that, lifting the siren to have it make noise, the entity stays off……

Not good I would think

Nice work team!!! @rdfurman I am having trouble with a broken change on the HoneyWell new standard Integration. I have an automation that monitors the real-time price and the consumption on the Grid to automatically put my Thermostat in “Away” mode which will move my Temp from 72F to 88F to save energy and make sure. I use these two calls in my AppDeamon Automation to toggle between cooling. This was working until the latest HA 21.8.

self.call_service("climate/set_preset_mode", entity_id=THERMOSTAT, preset_mode="none")
self.call_service("climate/set_preset_mode", entity_id=THERMOSTAT, preset_mode="away")

The error in my HomeAssistant is the following

File “/usr/src/homeassistant/homeassistant/components/climate/init.py”, line 486, in async_set_preset_mode
await self.hass.async_add_executor_job(self.set_preset_mode, preset_mode)
File “/usr/local/lib/python3.9/concurrent/futures/thread.py”, line 52, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/honeywell/climate.py”, line 372, in set_preset_mode
self._turn_away_mode_on()
File “/usr/src/homeassistant/homeassistant/components/honeywell/climate.py”, line 349, in _turn_away_mode_on
setattr(
File “/usr/local/lib/python3.9/site-packages/somecomfort/client.py”, line 183, in setpoint_cool
if temp > upper or temp < lower:
TypeError: ‘>’ not supported between instances of ‘NoneType’ and ‘int’

Any ideas?

Like most of the time, another restart after update fixed this for me.

2 Likes

LOL, since it wasn’t coming back I didn’t think of the usual trick!
Thanks

How can I change the reported cost (price) to be local currency and not $ USD ?
Is there a setting somewhere?