Guys just check on DSM/Synology integrations and saw that its now support uptime. Wondering is this for 115 or 116? because on my 115 I have not seen this feature? Thanks…
For the Vera users out there this release will cause all your devices to reimport with default names in duplication to the existing ones.
From what I can tell the unique id in HA storage for the Vera component changed to allow for multiple hubs. It used to be the device number but now it includes a hub id and device id.
I took the “nuke and pave” method by removing the integration, re-adding it and renaming the new entities to match the old names. I was having issues deleting the old integration entities and with HA preventing the use of the existing entity ids.
1 Like
I’ve been meaning to update to Hyperion NG… thanks for the nudge!
It only took almost all day to get it working again. (Hyperion-NG I mean, not the integration with HA) Oh well. 
Any idea why RAM metrics of supervisor do not match the sensor.memory_use_percent?
The former says Core RAM 15% and Supervisor RAM 5.5% while the latter says 40%.
Hi
I was looking for the secondary info and thought I would get it with the LEDs but doesnt seem I have.
Have I missed something ?
Thanks Martyn
now this is new behavior… initially usage went down, but since 4 am look what happens:
accompanied with endless issues in the log:
2020-10-08 04:13:24 ERROR (Recorder) [homeassistant.components.recorder] Error executing query: Instance <States at 0xad86c580> is not present in this Session
2020-10-08 04:13:24 ERROR (Recorder) [homeassistant.components.recorder] Error saving events: Instance <States at 0xad86c580> is not present in this Session
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/recorder/__init__.py", line 442, in _commit_event_session_or_retry
self._commit_event_session()
File "/usr/src/homeassistant/homeassistant/components/recorder/__init__.py", line 497, in _commit_event_session
self.event_session.expunge(dbstate)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 1854, in expunge
raise sa_exc.InvalidRequestError(
sqlalchemy.exc.InvalidRequestError: Instance <States at 0xad86c580> is not present in this Session
anyone with a hint how to solve this?
Oh, WTH!!!. Without the posssibility to hide the header most of my smaller displays are worthless.
When will MCP23017 I/O Expander integration be fixed ?
As of 0.115.0 it does not work and 0.116.0 did not fix it 
Here is github issue related to this: https://github.com/home-assistant/core/issues/40192
1 Like
Yes it is the same behavior on RPI3+ venv core install
It happened when database purge was taken place (somewhere about 4:00 AM) .
Did not roll dice any further and reverted to stable 0.115.6 
And not only CPU usage went up… RAM was eaten up as in 0.116 betas…
Best, JR
Thanks, already saw that but could not link it to my problem- need more coffee it seems
Hi, after this upgrade, logbook no longer working and got error in log 
2020-10-08 09:46:02 ERROR (Recorder) [homeassistant.components.recorder] Error saving events: (sqlite3.IntegrityError) UNIQUE constraint failed: events.event_id
[SQL: INSERT INTO events (event_id, event_type, event_data, origin, time_fired, created, context_id, context_user_id, context_parent_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)]
[parameters: ((2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 07:45:01.778246', '2020-10-08 07:45:02.313078', '2c1cf36a093a11ebb0a95bdf141d567b', None, None), (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 07:44:31.708647', '2020-10-08 07:44:32.225946', '1a30ab86093a11ebade6f39fa10ffd89', None, None), (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 07:44:01.837387', '2020-10-08 07:44:03.418719', '0862b309093a11ebb47a0dc8de6d89be', None, None), (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 07:43:31.369963', '2020-10-08 07:43:32.470243', 'f639b779093911ebb14e1b8e33b37505', None, None), (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 07:43:01.435675', '2020-10-08 07:43:02.798523', 'e462219d093911eba635e98de1f6f51a', None, None), (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 07:42:31.361601', '2020-10-08 07:42:32.225285', 'd2752b49093911ebbc7655cb5615dba5', None, None), (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 07:42:01.402016', '2020-10-08 07:42:02.797142', 'c099b8d6093911ebb71f671d2762dfe0', None, None), (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 07:41:31.355102', '2020-10-08 07:41:33.110167', 'aeb0e6be093911eb88205d413e5b1c52', None, None) ... displaying 10 of 606 total bound parameter sets ... (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 02:13:58.363361', '2020-10-08 02:13:59.010282', 'ec985fe1090b11eb98159f4ddf293b96', None, None), (2218486, 'state_changed', '{}', 'LOCAL', '2020-10-08 02:13:28.367851', '2020-10-08 02:13:29.010333', 'dab76c02090b11eb8a9b3dbb77efcf83', None, None))]
(Background on this error at: http://sqlalche.me/e/13/gkpj)
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1256, in _execute_context
self.dialect.do_executemany(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 590, in do_executemany
cursor.executemany(statement, parameters)
sqlite3.IntegrityError: UNIQUE constraint failed: events.event_id
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/recorder/__init__.py", line 442, in _commit_event_session_or_retry
self._commit_event_session()
File "/usr/src/homeassistant/homeassistant/components/recorder/__init__.py", line 493, in _commit_event_session
self.event_session.flush()
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 2523, in flush
self._flush(objects)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 2664, in _flush
transaction.rollback(_capture_exception=True)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__
compat.raise_(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_
raise exception
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 2624, in _flush
flush_context.execute()
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/unitofwork.py", line 419, in execute
n.execute_aggregate(self, set_)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/unitofwork.py", line 521, in execute_aggregate
self.execute(uow)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/unitofwork.py", line 586, in execute
persistence.save_obj(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/persistence.py", line 239, in save_obj
_emit_insert_statements(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/orm/persistence.py", line 1083, in _emit_insert_statements
c = cached_connections[connection].execute(statement, multiparams)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1011, in execute
return meth(self, multiparams, params)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection
return connection._execute_clauseelement(self, multiparams, params)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement
ret = self._execute_context(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context
self._handle_dbapi_exception(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception
util.raise_(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_
raise exception
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1256, in _execute_context
self.dialect.do_executemany(
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 590, in do_executemany
cursor.executemany(statement, parameters)
sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) UNIQUE constraint failed: events.event_id
1 Like
Anyone tried to get te MQTT tag scanner to work? I tried the example given on the MQTT Tag Scanner page but I’m not getting any resutls yet
Someone have problems with MQTT all my devices ar gone.Rollback to 115.6 and MQTT working
The same errors appear in my log.
Error saving events 5272 times
Error executing query: 5272 times
since yesterday evening at 22:26 o’clock when I installed 0.116.0
Upgrading to 116 caused all my Vera entities to be rediscovered and recreated - that’s a breaking change. I’ve since rolled back to 115
There is a recorder problem in 0.116.0. Appears to be solved and will be released in 0.116.1.
For now, I have rolled back to 0.115.6.
Just for info - I just installed 116.0 and got this:
For me it is not working along with other custom cards (ie Weather Card)
I’ll give that a try Tim. I’ve already rolled back to my 0.115.6 snapshot. I’ll delete Vera, upgrade to 0.116.0 and see what happens.
Update: I deleted the Vera integration, then updated to 0.116.0 and then re-added the Vera integration. I had 3 entities to repair (switches that I class as lights) all I had to do was delete the switch_ part of the description and all was good. Much better than having to deal with a duplicate of every Vera entity.
Thanks for the tip Tim
1 Like