pergola.fabio
great job, like always!
great job, like always!
Is there any custom component or anything that will take a list of all the components that I’m running, and compare it to the changelog, and then only show me the parts of the changelog that matter to my installation? These changelogs just seem to get longer and longer, and I would like to be able to see which changes matter to me.
1 reply
Just installed this, but my PyChromecast did not update to 2.5.2 as described in the release notes; it remains at 2.1.0.
It updated when I pip’d it manually though.
Split out speedtest into a component and a sensor platform (@rohankapoorcom- #20527) (speedtestdotnet docs) (sensor.speedtest docs) (sensor.speedtestdotnet docs) (breaking change) (new-platform)
All of these link to same page and also page is only about the speedtestdonet as platform, no ‘sensor’ info. I don’t know how to fix what I’m running currently 
as I want it to be as usual sensor.
In a way, yes.
If you are running HassIO, you can (and should) run the " Check Home Assistant configuration" addon BEFORE upgrading versions.
This addon will check check whether your configuration files are valid against the new version of Home Assistant before you actually update your Home Assistant installation. This add-on will help you avoid errors due to breaking changes, resulting in a smooth update.
It caught a bunch of changes to MQTT switches, sensors, and lights for me in the 0.87 update.
Note, this is not the same as the “Check Config” button. That checks your config against the version you are running. The addon I’m talking about here checks your config against the latest version, before you upgrade to it.
https://www.home-assistant.io/addons/check_config/
2 replies
I just ran the Check Home Assistant Configuration addon and I get this
You are using pip version 18.0, however version 19.0.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
But If I run the command in hassio console pip does not exist, only pip3 exists.
Then I get
Failed config
General Errors:
- Platform not found: media_player.alexa
In media_player.yaml I have
- platform: alexa
email: !secret alexa_user
password: !secret alexa_pwd
url: amazon.it
What should I check?
When I do hassio ha check I get no error!!
Thanks
4 replies
Just remove it from the sensors section and add speedtestdotnet: in your configuration.yaml. After that, the sensor seems to be working ok.
This is one of those situations where ‘read the documentation’ would not be a helpful suggestion! After reading it, the word “opaque” came to mind. 
This component is a meta-component and configures a default set of components for Home Assistant to load. The components that will be loaded can be found here.
I sorta get it (a component that manages a default set of other components) but I don’t understand how it automatically keeps that ‘default set’ of components up to date. For example, it’ll automatically update that default set to 0.89 … even if everything else remains at 0.88? That can’t be right.
Don’t worry about the pip version. That’s managed by Home-Assistant and they’ll upgrade it when necessary.
As for the Alexa media player, is that a custom component you installed? I believe it is, and if so, since it’s not official the config checker probably thinks it’s not supported.
This Breaking Change affects a few components:
Deprecate conf_update_interval (@rohankapoorcom - #20924) (breaking change) (beta fix)
It scraps update_interval in favor of the more widely used scan_interval. If you’re using components configured with the option update_interval you’re probably affected by this change.
Basically, it will auto add new core components to your HA install.
For instance, person: is a brand new core component. If you want to start using it after you upgrade, you will have to add it to your config to activate it. To make this easier for future new core components, they have added default_config:. If you add that, then new core components will automatically be added to your install as they become available. Saving you the hassle of tracking the new releases and adding them by hand as they’re released.
ah, that makes sense 
Thanks for everyones hard work!
What is the deal with the new “person” component?
How is it different than using a group of devicer_trackers?
Right now for everyone in household I have a group composed each of a device_tracker.ping and device_tracker.bt If atleast one is ‘home’ then the group.person_one is ‘home’. It works flawlessly for tracking, sensor, stats, automations, etc.
I’d prefer to keep things simple by just using core-level components, unless this offers some new advantage.
1 reply
Right now? Probably not much, other than that it can be linked to a user account.
However, in the future, with multiple user accounts with individual permission levels and device trackers tied to them, the new area’s component with the ability to have a “person” in an “area”, etc, there will likely be many differences.
With the initial introduction of this component there is not much difference, but it might make sense to migrate to it where possible so when more advanced features are added the transition is smoother.
1 reply
Maybe I am off base with this question, but if I want to keep a separate file for persons named (ex.) person.yaml , (splitting my configurations) I would have normally made a reference in my configuration.yaml file like this: “person: !include include/person.yaml”
If I add default_config: instead, will this not cause a conflict by seeing 2 entries named “person:” in my configuration.yaml? One for the default_config: and one that has the include statement.
I would really like to use default_config so that I am always up to date on the new components, but I have to say that I love splitting my configuration to keep it easy to locate.
So I installed this component and it totally hosed the machine. When I started it, about 5 minutes later HA stopped responding. So I SSH into it, and that took like a solid minute just to get in, after that, running hassio help causes an out of memory error. I had to restart the computer. Not sure why that happened.
1 reply
CustomUI seems to be broken since the update. Things like this
cover.garage_door:
friendly_name: Porte du garage
device_class: garage_door
alternative_friendly_names:
- Porte de garage
templates:
icon_color: >
if (state === ‘closed’) {
return ‘#34a853’;
} else {
return ‘#ea4335’;
}
does not work anymore. I mean the icon does not change its color. It’s always its default blue color.
Someone else noticed that ?
I’ve seen a couple of other threads in which custom_components are beginning to give warnings that they need the directories to be restructured or they will soon fail.
It’s fairly easy enough to make the switch (unless you have a ton of them, I guess…) but when/where was this change announced?
the good news is you can switch to the new file structure now to beat the rush and your stuff will still work. the bad news is it also breaks the custom resource tracker card once you switch to the new folder structure unless the dev catches that change and updates their code. 
EDIT: I just re-read the post and saw this:
That’s a pretty nonchalant statement for something that could end up breaking a significant portion of peoples set ups in the near future.
3 replies
Hi all,
I’m receiving the following error when updating HASSOS to 0.88.
Any ideas?
19-02-21 00:18:22 INFO (SyncWorker_6) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-64-homeassistant tag 0.88.0. 19-02-21 00:18:25 ERROR (SyncWorker_6) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-64-homeassistant:0.88.0 -> 500 Server Error: Internal Server Error (“readlink /mnt/data/docker/overlay2/l: invalid argument”). 19-02-21 00:18:25 WARNING (MainThread) [hassio.homeassistant] Home Assistant is already running!
Not normally one to complain but ZHA seems completely broken now with 0.88. I had to revert back to 0.87.1 to have it working again.
Entities in the ZHA dashboard have lost all their names, which makes it darn near impossible to know what device you’re looking at there without guessing and drilling down.#21242
Half of the device stops working but not all of it. I.e. the ZHA and Temp Sensor still works but the Binary Sensor doesn’t? #21243
Parts of the ZHA device that were shown as entities are no longer present. 21245
CoolMasterNet sounds like a very cool component, but it does not look like I can buy one as a home automation enthusiast since I can only get a quote. It’s more for integrators and installers. Oh, well. But hey! It’s nice having Ethernet! No need for Wi-Fi, which is nice! 
I would try rebooting your pi.
It will add all default options like discovery etc, person, there is a list.
If they follow the link provided it tells them what to do. HA cant be responsible for all the custom components otherwise it would never move forward.
The warning now, will give the dev o that component time to change or the end user time to inform the dev of that custom component the time to change it
Only if they ignore basic instructions… so you’re right… lots of people’s configs will break…
1 reply
Not that people are exactly expected to read these things, but there’s a system architecture discussion section of the Home-Assistant Github page. That’s where the discussions about these things take place, with this particular change being discussed as early as mid-december:
As a side note, it’s a nice repo to read through to get an idea of where this who project is headed, such as knowing about areas and persons long before any PRs were made to add code for those features lol.
1 reply
@frenck 0.88 seems to be breaking the adb addon, the addon itself runs fine and i’m not getting any errors, but i’m getting an error that media_player.androidtv is not a valid platform, do i need to update androidtv.py file?
The Great Migration blog post indicates:
… if you want to override a built-in component/platform with a custom version, you will need to copy over all component and platform files , not just the one you want to load.
Currently, I use modified versions of MQTT HVAC (climate) and MQTT Alarm Panel (alarm). That’s just two files copied into:
/custom_components/climate
/custom_components/alarm_control_panel
If all I now need to do is move those two files into:
/custom_components/mqtt
then that’s easy-peasy!
On the other hand, the blog post seems to suggest I will need to copy not just those two files but everything related to MQTT into /custom_components/mqtt.
if you want to override a built-in component/platform with a custom version, you will need to copy over all component and platform files , not just the one you want to load.
Is not implemented yet in 0.88. Issue is linked at the bottom of the blog post, which leads to the PR here: Prevent partial custom component overlays by balloob · Pull Request #21070 · home-assistant/core · GitHub
Yep, that’s what I’m doing now, namely overriding (altering) the stock MQTT climate and alarm_control_panel with custom versions.
Based on Paulus’ reply, it would appear I won’t need to copy over the whole kit and kaboodle for 0.88 … but it’s definitely on the roadmap.
There appears to be some sort of disconnect between the desire that HA will move toward making things dirt simple for the non-technical person to be able to set up and run a HA install. Those people that the HA “official” developers are specifically courting with all of the GUI based configuration and editing expect to be able to set their installs up with all of the “flashy new” stuff that community based developers are setting up.
Then in some small corner of a major release blog post there is literally just 19 words devoted to letting the developers and/or the non-tech users know that if they don’t make a change to their set up then after a future update their set up will stop working. How many people actually look at their logs to notice a warning when everything is actually working. Most newer people don’t even know that a home-assistant.log file even exists let alone where to find it.
Does anyone really expect the people that HA is trying to bring in will actually visit a link specifically aimed at developers?
Then when someone points out the fact that it’s a pretty major change to just gloss over like it was then suddenly there are people insinuating that it’s those non-technical people’s responsibility to be able to somehow know what broke and how to fix it. Or for the “dev” who only ever makes a single component or two to realize that their component will suddenly stop working and that they should have just known with the sparse information given that they needed to update their code and the install instructions.
No HA can’t be responsible for all the custom components but the life blood of HA is the custom components and custom cards that are created by community members so you would think that HA would at least make it a bit easier to do their thing.
Or you’re going to start hearing a bunch more frustrations from people who get things set up the way they want then things just randomly start breaking and then you blame them for not understanding “simple instructions”.
I’m not saying that HA shouldn’t move forward but there needs to be a better system in place to let people know about stuff as big as this.
It’s either for non-tech savvy people or it’s not.
1 reply
Really was searching for something like “person” component!
Thank you.
And about themes. Can not find that in docs. Can we now round cards and change background-image from themes?
I understand what you are saying… really do. However it’s a fact that people do not read the release notes even… If you start seeing an issue, surely you would at least do that and also check the logs… it’s not like any of this is hidden. Fortunately the disasterous roll out of 0.86 where the entity id’s totally broke everything and HA wouldn’t even start was rolled back and I don’t think they are likely to break things again without warning.
For my part, I saw that some of my components and custon-cards were going to be affected (from b0) and I contacted the developers of those cards and components to give them a heads up. Love to know what your better solution is. I don’t think it’s up to the main HA devs to be hand holding everyone who writes custom components. I don’t know what the best solution is but taking a pro-active approach as a user seems like a good idea to me anyway.
1 reply
Which was exactly the point in my post about this subject.
Maybe a better approach would be to make more system posts to the forum with things broken up into more easily digestible pieces when there is a major change to functionality.
Cramming all the information into a major release post every two weeks that then gets inundated with so much information isn’t the most effective way to communicate these things. Or at the very least not bury it deep in the post so it’s ridiculously easy to miss.
1 reply
Won’t make the slightest difference. People won’t read multiples either if they don’t read even one… All the major breaking changes are in a small section at the top.
I’ve got to say I must lead a charmed life, but another painless upgrade (crossed fingers).
Love the ReRo approach, although I’d rather stick to yaml files than all this gui bulldust. One of the reasons I came to HA in the first place was that it was configurable from text files. But maybe that is because I have been using linux since the mid 90s.
1 reply
Same here. even easier when i can test with a beta though before taking plunge to latest.
I’m 50/50 on the yaml /gui. Somethingsare just easier to use the gui.
I have questions about the warnings displayed in ui notifications panel.
Warnings give us the info that some properties are available and must be removed. But I have warnings about properties that are referenced in documentation. An example is the max-age property of sensor.statistics
So my question is : what information is the right one ? The warning or the documentation itself ?
Thanks a lot
yes, i am seeing warnings too, that in my opinion are correct? i dont get it,
see here :
1 reply
I get this:
Log Details (WARNING)
Thu Feb 21 2019 10:03:59 GMT+0100 (Midden-Europese standaardtijd)
Your configuration contains extra keys that the platform does not support.
Please remove [device].
Your configuration contains extra keys that the platform does not support.
Please remove [icon].
But i cant find it in my config… How can i find it?
1 reply
Just remember, sometimes the log throws up errors that have nothing to do with the actual error… the error could be somewhere else entirely. This has happened to me many times… It says invalid key on blah line but then you find somewhere else is actually what triggered the error…
I would check the breaking changes in the release notes for ANY platform/component you use. If necessary, start commenting stuff out and see if that fixes it.
Yeah i’ve got one with linenumber, already fixed that. But this is inpossible to find!
Is the log EVENT_LISTENING saved somewhere? It scrolls very fast, need to read it slowly
Hi
just moved to 0.88 and besides trying to understand if all custom_components are working, I’m testing the new person component.
I’ve defined like this
- name: me
id: me2345
device_trackers:
- device_tracker.192_168_1_86_xx_xx_xx_xx
- device_tracker.192_168_1_71_xx_xx_xx_xx
- device_tracker.ab12cd34ef56
The first two are Google Home Bluetooth location and the third is based on nmap
Now I’ve disabled my Wifi and BT and after a while person.me went from home to not_home.
Perfect.
Now I just enabled BT and one of the two GH BT tracker become home and the other two remain not_home.
But person.me is still not_home.
What is the rule to get person home or not_home based on all the device_tracker?
Why in the entity attribute I see only one device_tracker:
editable: false
id: me2345
source: device_tracker.ab12cd34ef56
friendly_name: Me
Thanks
1 reply
Got it thanks, somehow wasn’t showing earlier but after screen refresh it appeared
The samsungtv component give me a Config Warning due to the mac address in the config file
- platform: samsungtv
name: Samsung TV
host: samsung-tv.home.lan
mac: XX:XX:XX:XX:XX:XX
But the documentation still say that mac is a valid configuration entry (and required for power on) : https://www.home-assistant.io/components/media_player.samsungtv/
1 reply
mac addresses were dropped a couple of versions ago. Documentation needs updating.
No they weren’t. It was only the vendor look up. https://github.com/home-assistant/home-assistant/pull/13788 sorry.
I had the same behavior twice. My Pi 3 B just became unresponsive for 4+ hours each attempt so I have sworn that add-on off.
Answer it myself. So it is the NibeUplink custom component that creates this errors. Component itself works fine so I will start investigate what causes this errors
same problem, with last update, alexa stopped working:
No state available for media_player.echo_plus
{
“type”: “media-control”,
“entity”: “media_player.echo_plus”
}
New error with 88.0:
Error doing job: SSL error errno:1 reason: KRB5_S_INIT
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/local/lib/python3.7/ssl.py", line 767, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2605)
I’m not using HTTPS or SSL in my configuration that I know of.
Also locked out of Firefox UI with this error:
2019-02-21 08:51:20 ERROR (MainThread) [homeassistant.components.http.data_validator] Data does not match schema: required key not provided @ data['client_id']
Edge lets me in.
1 reply
Hi,
I have notice ENIGMA stopped working. I have custom_components\media_player\enigma.py with latest version. The error log looks like this:
Blockquote rror loading custom_components.media_player.enigma. Make sure all dependencies are installed
Traceback (most recent call last): File “/usr/src/app/homeassistant/loader.py”, line 147, in _load_file module = importlib.import_module(path) File “/usr/local/lib/python3.7/importlib/init.py”, line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File “<frozen importlib._bootstrap>”, line 1006, in _gcd_import File “<frozen importlib._bootstrap>”, line 983, in _find_and_load File “<frozen importlib._bootstrap>”, line 967, in _find_and_load_unlocked File “<frozen importlib._bootstrap>”, line 677, in _load_unlocked File “<frozen importlib._bootstrap_external>”, line 728, in exec_module File “<frozen importlib._bootstrap>”, line 219, in _call_with_frames_removed File “/config/custom_components/media_player/enigma.py”, line 26, in <module> from custom_components.enigma import _LOGGER, DOMAIN as ENIGMA_DOMAIN ModuleNotFoundError: No module named ‘custom_components.enigma’
Service homeassistant/restart called.
Blockquote
For now person simply pick up the latest updated device_tracker's state as its state. I am sure it will get improvement in next release or two.
For anyone else with this issue:
This was an error in the component code.
It looks like a pull request was just merged to fix it, FYI.
Perfect, thanks for the link!
thanks - I had restarted 3 times but it seems an extra one has helped thanks
there was a breaking change to velux
Looks like Eufy is no longer working with 0.88 @mjg59
2019-02-22 07:41:31 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform ring is taking over 10 seconds.
2019-02-22 07:41:50 ERROR (MainThread) [homeassistant.components.switch] Error while setting up platform eufy
Traceback (most recent call last):
File "/home/rob/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
return fut.result()
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/home/rob/homeassistant/lib/python3.6/site-packages/homeassistant/components/eufy/switch.py", line 15, in setup_platform
add_entities([EufySwitch(discovery_info)], True)
File "/home/rob/homeassistant/lib/python3.6/site-packages/homeassistant/components/eufy/switch.py", line 31, in __init__
self._switch.connect()
File "/home/rob/homeassistant/lib/python3.6/site-packages/lakeside/__init__.py", line 229, in connect
return device.connect(self)
Lakeside AES compatibility issue with Crypto?
File "/home/rob/homeassistant/lib/python3.6/site-packages/lakeside/__init__.py", line 73, in send_packet
cipher = AES.new(bytes(key), AES.MODE_CBC, bytes(iv))
File "/home/rob/homeassistant/lib/python3.6/site-packages/Crypto/Cipher/AES.py", line 202, in new
The recommended value (and the default, if not specified) is **16**.
File "/home/rob/homeassistant/lib/python3.6/site-packages/Crypto/Cipher/__init__.py", line 55, in _create_cipher
File "/home/rob/homeassistant/lib/python3.6/site-packages/Crypto/Cipher/_mode_cbc.py", line 251, in _create_cbc_cipher
else:
File "/home/rob/homeassistant/lib/python3.6/site-packages/Crypto/Cipher/_mode_cbc.py", line 94, in __init__
RecursionError: maximum recursion depth exceededyes i see this: the point I am making is that the link to documentation has not been updated accordingly by my understanding.
It is not mentioned KLF200 needs to be upgrade to 2-series firmware, link to “cover.velux docs” is the same of “velux docs”…etc…
Hi
I’m using Samsung WiFi Kit(cassette air conditioner)
and i can control it via ST APP.
but HA-ST components cant load it.
can you help me?
Hi there,
I seem to be having a Russound issue. When I upgrade to version 88 I loose access to my zones. This is the error I get
Error while setting up platform russound_rio
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py”, line 128, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.7/asyncio/tasks.py”, line 416, in wait_for
return fut.result()
File “/usr/local/lib/python3.7/site-packages/homeassistant/components/media_player/russound_rio.py”, line 39, in async_setup_platform
from russound_rio import Russound
File “/usr/local/lib/python3.7/site-packages/russound_rio/init.py”, line 1, in
from .rio import (
File “/usr/local/lib/python3.7/site-packages/russound_rio/rio.py”, line 8
from asyncio import async as ensure_future
^
SyntaxError: invalid syntax
I am now on 0.88.0 and getting an error with Whois component. Is anyone else getting this error?
Fri Feb 22 2019 11:51:02 GMT-0500 (Eastern Standard Time)
Error while setting up platform whois
Traceback (most recent call last):
File "/usr/local/lib/python3.7/sre_parse.py", line 1021, in parse_template
this = chr(ESCAPES[this][1])
KeyError: '\\s'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/components/sensor/whois.py", line 40, in setup_platform
from pythonwhois import get_whois
File "/usr/local/lib/python3.7/site-packages/pythonwhois/__init__.py", line 1, in <module>
from . import net, parse
File "/usr/local/lib/python3.7/site-packages/pythonwhois/parse.py", line 363, in <module>
registrant_regexes = [preprocess_regex(regex) for regex in registrant_regexes]
File "/usr/local/lib/python3.7/site-packages/pythonwhois/parse.py", line 363, in <listcomp>
registrant_regexes = [preprocess_regex(regex) for regex in registrant_regexes]
File "/usr/local/lib/python3.7/site-packages/pythonwhois/parse.py", line 205, in preprocess_regex
regex = re.sub(r"\\s\*\(\?P<([^>]+)>\.\+\)", r"\s*(?P<\1>\S.*)", regex)
File "/usr/local/lib/python3.7/re.py", line 192, in sub
return _compile(pattern, flags).sub(repl, string, count)
File "/usr/local/lib/python3.7/re.py", line 309, in _subx
template = _compile_repl(template, pattern)
File "/usr/local/lib/python3.7/re.py", line 300, in _compile_repl
return sre_parse.parse_template(repl, pattern)
File "/usr/local/lib/python3.7/sre_parse.py", line 1024, in parse_template
raise s.error('bad escape %s' % this, len(this))
re.error: bad escape \s at position 0Apparently there’s an updated version available. See this post:
Ill echo what a few other posts have said. ZHA is completely broke with this release. Most of my lights stopped updating, my logs are full of errors, and the network is extremely unstable.
.88.1 is not available for docker yet so lets hope it fixes these issues.
Here are some example logs from a fresh start of Hass:
2019-02-22 11:30:22 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py”, line 238, in request
raise DeliveryError(“Message send failure %s” % (v[0], ))
zigpy.exceptions.DeliveryError: Message send failure EmberStatus.MAX_MESSAGE_LIMIT_REACHED
2019-02-22 11:30:23 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=5 command=1 args=[[]]
2019-02-22 11:30:23 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=6 command=1 args=[[]]
2019-02-22 11:30:24 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=2 command=1 args=[[]]
2019-02-22 11:30:24 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=5 command=1 args=[[]]
2019-02-22 11:30:24 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=6 command=1 args=[[]]
2019-02-22 11:30:24 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=7 command=1 args=[[]]
2019-02-22 11:30:25 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=5 command=1 args=[[]]
2019-02-22 11:30:25 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=6 command=1 args=[[]]
2019-02-22 11:30:25 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=7 command=1 args=[[]]
2019-02-22 11:30:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=5 command=1 args=[[]]
2019-02-22 11:30:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=6 command=1 args=[[]]
2019-02-22 11:30:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=31 command=1 args=[[]]
2019-02-22 11:30:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=7 command=1 args=[[]]
2019-02-22 11:30:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=32 command=1 args=[[]]
2019-02-22 11:30:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=5 command=1 args=[[]]
2019-02-22 11:30:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=6 command=1 args=[[]]
2019-02-22 11:30:26 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=7 command=1 args=[[]]
2019-02-22 11:30:28 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=31 command=1 args=[[]]
2019-02-22 11:30:28 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=32 command=1 args=[[]]
2019-02-22 11:30:28 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=33 command=1 args=[[]]
2019-02-22 11:30:28 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=34 command=1 args=[[]]
2019-02-22 11:30:30 WARNING (MainThread) [homeassistant.components.camera] Setup of platform ring is taking over 10 seconds.
2019-02-22 11:30:53 WARNING (MainThread) [bellows.zigbee.application] Unexpected response TSN=37 command=1 args=[[]]
Yes.
(Amongst plenty of other utterly indecipherable rubbish and messages that is impossible to tie down to anything I can actually identify or do anything about:
"platform": "mqtt_json" is deprecated, replace with "schema":"json"
and
Your configuration contains extra keys that the platform does not support.
Please remove [flash]."
for example. What platform? Nowhere can I find “flash” in any of my files. )
Hi 0.88.1 still has the ssl/KRB5_s_INIT issue
2019-02-23 08:10:49 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: KRB5_S_INIT
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/local/lib/python3.7/ssl.py", line 767, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2605)
2019-02-23 08:11:21 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: KRB5_S_INIT
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/local/lib/python3.7/ssl.py", line 767, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2605)Thank you. I will revert back until they fix that. Thanks for that information
look at any of your mqtt components, this one has been around for a number of releases so you need to change the mqtt configs
Whats up with the docker releases? For the past 1-2 months all of the 86.1, 87.1 and 88.1 etc is not updated before days after relase? The main release is ok with a few hours behind but the 0.1 releases are not updatet before days later. If we have a bug that is fixed in the 0.1 release its a long wait
I’m getting this extra keys warning for the iTach remote component but my configuration matches the example configuration and does not contain any unsupported keys:
Your configuration contains extra keys that the platform does not support.
Please remove [name]. (See /config/remotes.yaml, line 0).
My remotes.yaml config:
- platform: itach
name: Cinema
host: 10.1.1.19
devices:
- name: Cinema Amp
modaddr: 1
connaddr: 1
commands:
- name: "ON"
data: "0000 006A 0000 0024 0154 00B3 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0600 0154 0055 0016 0F18"
- name: "OFF"
data: "0000 006A 0000 0026 015D 00B5 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0042 0016 0016 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0042 0016 0042 0016 060B 015D 0056 0016 0EA3 015D 0055 0016 00B5"
- name: "Dolby" # Dolby DSP
data: "0000 006A 0000 0026 0154 00B4 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0016 0016 0600 0154 0055 0016 0E7D 0154 0055 0016 0F18"
etc…
Example config from here: https://www.home-assistant.io/components/remote.itach/
# Example configuration.yaml entry
remote:
- platform: itach
name: Living Room
host: itach023fdc
devices:
- name: TV
connaddr: 2
commands:
- name: "ON"
data: "0000 006D 0000 0022 00AC 00AC 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0689"
I’ll open an issue.
Edit: or maybe I wont: https://github.com/home-assistant/home-assistant/issues/21300
Docs just need updating.
Any one else getting periodic crashes?
Assistant
Loaded: loaded (/etc/systemd/system/[email protected]; enabled;
Active: failed (Result: signal) since Fri 2019-02-22 18:39:39 GMT; 6h ago
Process: 26248 ExecStart=/home/rob/homeassistant/bin/hass -c /home/rob/.ho
Main PID: 26248 (code=killed, signal=KILL)
Feb 22 18:39:12 squeezeserver hass[26248]:
Feb 22 18:39:13 squeezeserver hass[26248]: [158B blob data]
Feb 22 18:39:15 squeezeserver hass[26248]: % Total % Received % Xferd
Feb 22 18:39:15 squeezeserver hass[26248]:
Feb 22 18:39:15 squeezeserver hass[26248]: [158B blob data]
Feb 22 18:39:21 squeezeserver hass[26248]: % Total % Received % Xferd
Feb 22 18:39:21 squeezeserver hass[26248]:
Feb 22 18:39:21 squeezeserver hass[26248]: [158B blob data]
Feb 22 18:39:39 squeezeserver systemd[1]: [email protected]: Main p
Feb 22 18:39:39 squeezeserver systemd[1]: [email protected]: Failed
I get these warnings in my log 2019-02-21 22:30:00 WARNING (MainThread) [homeassistant.helpers.service] Not passing an entity ID to a service to target all entities is deprecated. Update your call to lock.lock to be instead: entity_id: all 2019-02-21 22:30:00 WARNING (MainThread) [homeassistant.helpers.service] Not passing an entity ID to a service to target all entities is deprecated. Update your call to light.turn_off to be instead: entity_id: all 2019-02-21 22:30:00 WARNING (MainThread) [homeassistant.helpers.service] Not passing an entity ID to a service to target all entities is deprecated. Update your call to switch.turn_off to be instead: entity_id: all
so I do as it says and add the entity_id: all and it breaks my script so I remove it and live with the warning as my script works the way I want it to
so I understand why people get fustrated when they decide to break something that is working as the so called fix breaks it
1 reply
It’s a warning for now but expect it to break the component in the future so I suggest you work out how to fix it… ie fix your script to work with it.
See for example here Not passing an entity ID to a service to target all entities is deprecated. Use instead: entity_id: "all"
1 reply