Thx. Did you switch to Mosquitto broker?
Yes I did. Postponed it for a year but took me 5 minutes. I created with Mosquitto a user homeassistant and password hello so all devices could automatically connect
1 Like
I am running Home Assistant Supervised on RPI , I upgraded to 0.112 and seem to have lost somethings on the Developer Tools tab, It no longer shows me the version I am running… So I really can’t verify what version I am now running.
The Supervisor>System >System log has an entry
20-07-02 16:57:57 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.112.0
… Also I lost the logs screen on the Developer Tools tab.
Hello,
I have a Toon Acceptance account is it possible to add this device to Home Assistant.
It work until 0.111.4.
With kind regards,
Peter Noé
Hello,
after upgrading to 112, I can’t connect to webos tv.
this same error occurs on wake on lan:
Logger: homeassistant.components.websocket_api.http.connection.140000588709328
Source: components/wake_on_lan/__init__.py:46
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 14:37:04 (2 occurrences)
Last logged: 14:37:13
an integer is required (got type NoneType)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 130, in handle_call_service
connection.context(msg),
File "/usr/src/homeassistant/homeassistant/core.py", line 1260, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1295, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 209, in handle_service
self._platforms.values(), func, call, required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 454, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 595, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 485, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 713, in async_toggle
await self.async_turn_on()
File "/usr/src/homeassistant/homeassistant/components/webostv/media_player.py", line 331, in async_turn_on
await self._on_script.async_run()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 831, in async_run
await run.async_run()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 555, in async_run
await self._async_run()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 572, in _async_run
await self._async_step(log_exceptions=not propagate_exceptions)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 153, in _async_step
self, f"_async_{cv.determine_script_action(self._action)}_step"
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 656, in _async_call_service_step
*self._prep_call_service_step(), blocking=True, context=self._context
File "/usr/src/homeassistant/homeassistant/core.py", line 1260, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1295, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/components/wake_on_lan/__init__.py", line 46, in send_magic_packet
port=broadcast_port,
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/wakeonlan.py", line 79, in send_magic_packet
sock.connect((ip, port))
TypeError: an integer is required (got type NoneType)
Create a new user for MQTT via the Configuration → Users (manage users) . Note: This name cannot be
homeassistantoraddon, those are reserved usernames.
see home-assistant/hassio-addons/blob/master/mosquitto
Anyway, I’m back running again. Thanks again!
Read the update notes. The log has moved from developer tools to configuration.
Thanks, I didn’t read the notes… my issues all solved.
My entire setup is messed up.
When I try and open the “supervisor” panel, I get “unable to load the panel source: /api/hassio/app/entrypoint.js”
All other panels just load forever and say “error occurred”.
I had the update run overnight, so it had more than 6hrs to update…
I cannot access ssh or smb…
Any suggestions?
install 0.111.4
Yes, same issue.
I have 2 Xiaomi Air Purifiers 3H and 2H both were working before the update and now only the 2H is working.
I’ve been experiencing issues with the recorder after upgrading to 112. I’m running MariaDB on my NAS, Home Assistant on RPI.
When I remove the recorder integration from configuration.yaml, it works ok (obviously not on the external db as I want it)
here’s a sequence of the log.
2020-07-02 20:52:42 WARNING (Recorder) [homeassistant.components.recorder.migration] Database is about to upgrade. Schema version: 7
2020-07-02 20:52:42 INFO (Recorder) [homeassistant.components.recorder.migration] Upgrading recorder db schema to version 8
2020-07-02 20:52:42 WARNING (Recorder) [homeassistant.components.recorder.migration] Adding columns context_parent_id to table events. Note: this can take several minutes on large databases and slow computers. Please be patient!
2020-07-02 20:52:42 INFO (Recorder) [homeassistant.components.recorder.migration] Unable to use quick column add. Adding 1 by 1.
2020-07-02 20:52:42 WARNING (Recorder) [homeassistant.components.recorder.migration] Column context_parent_id already exists on events, continuing
2020-07-02 20:52:42 WARNING (Recorder) [homeassistant.components.recorder.migration] Adding columns old_state_id to table states. Note: this can take several minutes on large databases and slow computers. Please be patient!
2020-07-02 20:52:42 INFO (Recorder) [homeassistant.components.recorder.migration] Unable to use quick column add. Adding 1 by 1.
2020-07-02 20:52:42 WARNING (Recorder) [homeassistant.components.recorder.migration] Column old_state_id already exists on states, continuing
2020-07-02 20:52:42 WARNING (Recorder) [homeassistant.components.recorder.migration] Adding index `ix_events_context_parent_id` to database. Note: this can take several minutes on large databases and slow computers. Please be patient!
2020-07-02 20:52:42 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (MySQLdb._exceptions.OperationalError) (1061, "Duplicate key name 'ix_events_context_parent_id'")
[SQL: CREATE INDEX ix_events_context_parent_id ON events (context_parent_id)]
(Background on this error at: http://sqlalche.me/e/e3q8)
2020-07-02 20:52:42 ERROR (Recorder) [homeassistant.components.recorder] Error during connection setup: (MySQLdb._exceptions.OperationalError) (1061, "Duplicate key name 'ix_events_context_parent_id'")
[SQL: CREATE INDEX ix_events_context_parent_id ON events (context_parent_id)]
(Background on this error at: http://sqlalche.me/e/e3q8) (retrying in 3 seconds)
Help appreciated!
Same Issue over here
Yep im having this issue using the switch.
Yep, mine broke too, issue is in wakeonlan integration if you had previously set the broadcast_address see GitHub Issue Temp work around to fix is pushed up is to set broadcast_port as well, 9 is the default port in the python lib they are using so i just stuck that in there.
1 Like
Can I check whether there is still a cost for the Smappee API? I know it was previously in the Smappee Integration notes but that doesn’t seem to be the case since this update release? Is this updated integration now using the local API’s?
Assuming it’s using the Smappee cloud API, it would be a shame as the device has a very good local REST API and MQTT, not to mention the ‘local first’ ethos of Home Assistant.
Any help appreciated 
From the doc it uses the cloud API which require a monthly fee…
1 Like
Completely blown away by the latest updates !!! 
Loads faster, my camera’s show almost instant when I load the page and till now I always had to reload once or twice to get all 4 camera’s showing the live stream. Now it is instant, literally within 1 second all camera’s show, in browser and in IOS app. So far no issue.
Big thanks to all the contributors to this awesome project!
That would involve a 24x the server load.