0.112: Making things faster; Logbook & History

[tom_l]

Thanks. Is there any reason the logic for recorder includes/excludes is different from the history or logbook integrations logic for includes/excludes?

It seems to be implemented more logically for the recorder.

[bdraco (J. Nick Koston)]

They are using two different data sets: logbook displays events, history displays states. Since events don’t have an entity_id (except the state in a state_changed event) and we filter by domain/entity_id we assign events to a domain to ensure filtering is possible.

[tom_l]

Ok but I wasn’t concerned with the difference between the logbook and history logic, it’s both of them compared to the logic used for the recorder.

I can use includes and excludes for the recorder, no problem. Works quite logically. Exclude a domain, include some entities. Include a domain, exclude some entities, or a mix of both.

I can only use one of excludes or includes for the history or logbook or unintended things happen. Like nothing at all appearing if I use globs, or whole domains not being included even though I have not specified any excludes for that domain.

[megatrooooon]

Till now, my hass.io doesn’t see the new update 0.112.5

[tom_l]

That’s because there isn’t one unless you are running home assistant core.

0.112: Making things faster; Logbook & History

It is being pulled. We have changes standing by for 0.113, which aren’t compatible with the builds for 0.112.5. We have decided the risk for fixing this now is to high for a patch release. As a result 0.112.5 will only be available for people using the Home Assistant Core installation method.

[maxym]

I found recorder filtering awkward too.
I had to exclude about 30 entities and to leave a few untouched. I though I can use glob but then spent more time inspecting actual behaviour than putting those 30 entitiies manually.

It seems

• there is no option to exclude ‘all’ from particular category defined by exclude globs and include a few of them back
• looks like using two stars in globs doesn’t work
• logic of filtering is so complex that it’s very hard to predict final behaviour. This one with conjuction of need of restarting HA to apply the changes makes this feature effectively useless.

here is the original post (obviously without response of actuall developers responsible for this feature): Recorder - exclude selection

I hope v0.113 will bring significant improvements

BTW why not to use regexp matching?

[chickenandporn (Allan Clark)]

• Entities that originate from MQTT will now become “unavailable” when the integration
  is not connected to the MQTT broker. Thanks [@elupus]

Unavailable entities seem to be un-deletable. How do we delete entities from a source that isn’t coming back?

[elupus (Joakim Plate)]

Hmm. Why am I credited with that.

[nickrout]

Just good luck I suppose

[chri5tian (Chris Tian)]

After updating from 0.111.4 last night, my Lovelace tabs have all gone:

Restoring from backup to 0.111.4 brought them back. Is there anything I could do to get them back in 0.112 or am I stuck with 0.111 now?

[chickenandporn (Allan Clark)]

Hmm. Why am I credited with that.

…its the release notes in HA, section “Other Noteworthy Changes”
0.112: Making things faster; Logbook & History - Home Assistant.

I… uh… hope you did some python coding around that time?

[elupus (Joakim Plate)]

Yup, but not in relation to mqtt

[francisp (Francis)]

Using custom header ?

[chri5tian (Chris Tian)]

Yes, I am.

[francisp (Francis)]

That is the problem. Upgrade custom header before upgrading to 0.112.x

[chri5tian (Chris Tian)]

Thanks, I’ve done it, so far so good. Keeping an eye on it.

[jag100 (John Giddings)]

Hi all.

I have a problem with Node Red and RFXCom and I’m not sure if its related to the 0.112 update.

I updated to 0.112 a few weeks ago and everything was running fine until I restarted my Intel NUC and now none of my flows run and the log for Node-Red shows:

19 Jul 22:35:24 - [warn] ------------------------------------------------------

19 Jul 22:35:24 - [warn] [node-red-contrib-rfxcom/rfxcom] Error: Cannot find module ‘@serialport/bindings’

Require stack:

• /opt/node_modules/serialport/lib/index.js
• /opt/node_modules/rfxcom/lib/rfxcom.js
• /opt/node_modules/rfxcom/lib/index.js
• /opt/node_modules/rfxcom/index.js
• /opt/node_modules/node-red-contrib-rfxcom/rfxcom.js
• /opt/node_modules/@node-red/registry/lib/loader.js
• /opt/node_modules/@node-red/registry/lib/index.js
• /opt/node_modules/@node-red/runtime/lib/nodes/index.js
• /opt/node_modules/@node-red/runtime/lib/index.js
• /opt/node_modules/node-red/lib/red.js
• /opt/node_modules/node-red/red.js
  19 Jul 22:35:24 - [warn] ------------------------------------------------------
  19 Jul 22:35:24 - [info] Settings file : /etc/node-red/config.js
  19 Jul 22:35:24 - [info] Context store : ‘default’ [module=memory]
  19 Jul 22:35:24 - [info] User directory : /config/node-red/
  19 Jul 22:35:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
  19 Jul 22:35:24 - [info] Flows file : /config/node-red/flows.json
  19 Jul 22:35:24 - [info] Server now running at http://127.0.0.1:46836/
  19 Jul 22:35:24 - [info] Waiting for missing types to be registered:
  19 Jul 22:35:24 - [info] - rfxtrx-port
  19 Jul 22:35:24 - [info] - rfx-detector-in
  19 Jul 22:35:24 - [info] - rfx-doorbell-in
  19 Jul 22:35:24 - [info] - rfx-sensor
  19 Jul 22:35:24 - [info] - rfx-lights-in
  19 Jul 22:35:24 - [info] - rfx-blinds-in
  19 Jul 22:35:24 - [info] - rfx-meter

I have posted a question about this here, but not had a reply.

Node-red-contrib-rfxcom stopped working

Hi all Is anybody else experiencing the same problem as me? If not, I assume its something unique to my environment. On the Github link I provided earlier, someone has now worked around the issue by using an old version of node-red-contrib-rfxcom and manually intalling serialport, but I dont think they are running Home Assistant and I dont know how to apply the same configuration. Thanks in advance for any help.

In a related post on GitHub (which I have mentioned in the link above), someone has manually installing some dependencies like “serialport”, “node-rfxcom” and “node-red-contrib-rfxcom”, but they aren’t running Home Assistant, they are running Node Red on Docker and I don’t know how to do the same in HA. I’ve tried in specifying different parameters in the NodeRed config and nothing works so far.

I depend on Node Red for most of my automations, not having it running is significantly degrading my platform.

Before I restore some old snapshots and downgrade to a previous version of Home Assistant, is anybody else getting this issue or have any suggestions on how I can get running again.

I tried restoring just the Node Red Add-on from a Snapshot, but that hasn’t worked which makes me think it’s something in my environment.

Thanks in advance

[bkprath (Brian)]

I’m running HA 0.112.4 supervised install on ubuntu 18.04, odroid N2 hardware. I notice 0.112.5 is out, however it doesn’t show as an update option in the GUI. I tried doing the following at the command prompt:
ha core update --version “0.112.5”

I get the following error message in the logs:

20-07-20 00:22:42 ERROR (SyncWorker_1) [supervisor.docker.interface] Can’t install homeassistant/odroid-n2-homeassistant:0.112.5 -> 404 Client Error: Not Found (“manifest for homeassistant/odroid-n2-homeassistant:0.112.5 not found: manifest unknown: manifest unknown”)

Any thoughts on why this release isn’t available for my install?

[DavidFW1960 (David)]

It was withdrawn as posted everywhere…

[Styx (Florian)]

Just for the records: It seemed to be some obscure problem with the database. I deleted the database - and the problem until now didn’t occur again.