Home Assistant OS does support NVMe drive
There is no hope if the data is governed by US law…
i don’t think there is any hope for our data stored anywhere these days
4 Likes
After going to 0.114.1 I’m getting problems with my only z-wave device, the Danalock v3 Blutooth / Z-Wave.
I haven’t switched to the new zwave system, still using the builtin from previous times, and I haven’t experiemented with the new z-wave integraiton.
It went from 58% battery before the upgrade to nothing now in HA, I’ve tried swapping batteries to a set I had lying around, it still says 0%, but asked directly via Bluetooth the lock is at 87%.
I can occaisonally lock or unlock it via the interface, but it doesn’t update the state of it properly.
I’ve tried healing the network, and the node, without any change in behaviour.
Just noticed this in the log:
2020-08-16 11:02:41.411 Info, NONCES: 0x98, 0xf3, 0x6a, 0xba, 0xe9, 0x06, 0xef, 0x37
2020-08-16 11:02:41.414 Info, NONCES: 0x34, 0x43, 0x7c, 0x50, 0x0f, 0x23, 0x6f, 0x6b
2020-08-16 11:02:41.414 Info, NONCES: 0x0d, 0xcd, 0x13, 0xe3, 0x4d, 0xa6, 0xd5, 0x81
2020-08-16 11:02:41.414 Info, NONCES: 0x9d, 0xb5, 0x6c, 0x90, 0x3f, 0xef, 0xec, 0xb8
2020-08-16 11:02:41.414 Info, NONCES: 0x38, 0x00, 0xd6, 0x9c, 0xed, 0x5c, 0xc6, 0x82
2020-08-16 11:02:41.414 Info, NONCES: 0x23, 0xed, 0x27, 0xdc, 0xa0, 0x76, 0xf5, 0xe1
2020-08-16 11:02:41.414 Info, NONCES: 0x10, 0xab, 0xae, 0xb3, 0x48, 0xca, 0x5a, 0x5c
2020-08-16 11:02:41.414 Info, NONCES: 0xcf, 0x82, 0xa4, 0xa9, 0x0b, 0x5c, 0x04, 0x22
2020-08-16 11:02:41.414 Info, Node006, Sending (Send) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x06, 0x0a, 0x98, 0x80, 0x38, 0x00, 0xd6, 0x9c, 0xed, 0x5c, 0xc6, 0x82, 0x05, 0x01, 0x6a:
2020-08-16 11:02:41.424 Detail, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-08-16 11:02:41.424 Detail, ZW_SEND_DATA delivered to Z-Wave stack
2020-08-16 11:02:41.447 Detail, Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x03, 0xe9
2020-08-16 11:02:41.447 Detail, ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-08-16 11:02:41.513 Detail, Node006, Received: 0x01, 0x23, 0x00, 0x04, 0x00, 0x06, 0x1d, 0x98, 0x81, 0x8e, 0x56, 0x8f, 0x71, 0x1f, 0x51, 0xce, 0xe8, 0xd2, 0x67, 0xbd, 0x68, 0xa9, 0x35, 0x53, 0x05, 0xb8, 0x70, 0x38, 0x49, 0x4f, 0xe4, 0xe5, 0xb2, 0x84, 0xe6, 0xd7, 0xce
2020-08-16 11:02:41.513 Info, Raw: 0x98, 0x81, 0x8e, 0x56, 0x8f, 0x71, 0x1f, 0x51, 0xce, 0xe8, 0xd2, 0x67, 0xbd, 0x68, 0xa9, 0x35, 0x53, 0x05, 0xb8, 0x70, 0x38, 0x49, 0x4f, 0xe4, 0xe5, 0xb2, 0x84, 0xe6, 0xd7, 0xce
2020-08-16 11:02:41.513 Detail, Node006, Decrypted Packet: 0x00, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x04, 0x00
2020-08-16 11:02:41.513 Detail,
2020-08-16 11:02:41.513 Info, Node006, Received Alarm report: type=0, level=0
2020-08-16 11:02:41.513 Detail, Node006, Refreshed Value: old value=0, new value=0, type=byte
2020-08-16 11:02:41.513 Detail, Node006, Changes to this value are not verified
2020-08-16 11:02:41.513 Detail, Node006, Refreshed Value: old value=0, new value=0, type=byte
2020-08-16 11:02:41.513 Detail, Node006, Changes to this value are not verified
2020-08-16 11:02:41.513 Detail, Node006, Notification: ValueChanged
2020-08-16 11:02:41.514 Detail, Node006, Notification: ValueChanged
2020-08-16 11:02:41.686 Detail, Node006, Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x06, 0x02, 0x98, 0x40, 0x2f
2020-08-16 11:02:41.687 Info, Node006, Received SecurityCmd_NonceGet from node 6
2020-08-16 11:02:41.687 Info, NONCES: 0x98, 0xf3, 0x6a, 0xba, 0xe9, 0x06, 0xef, 0x37
2020-08-16 11:02:41.687 Info, NONCES: 0x34, 0x43, 0x7c, 0x50, 0x0f, 0x23, 0x6f, 0x6b
2020-08-16 11:02:41.688 Info, NONCES: 0x0d, 0xcd, 0x13, 0xe3, 0x4d, 0xa6, 0xd5, 0x81
2020-08-16 11:02:41.692 Info, NONCES: 0x9d, 0xb5, 0x6c, 0x90, 0x3f, 0xef, 0xec, 0xb8
2020-08-16 11:02:41.692 Info, NONCES: 0x38, 0x00, 0xd6, 0x9c, 0xed, 0x5c, 0xc6, 0x82
2020-08-16 11:02:41.692 Info, NONCES: 0x4d, 0x9c, 0x89, 0xc1, 0x38, 0xaf, 0x5f, 0x88
2020-08-16 11:02:41.692 Info, NONCES: 0x10, 0xab, 0xae, 0xb3, 0x48, 0xca, 0x5a, 0x5c
2020-08-16 11:02:41.692 Info, NONCES: 0xcf, 0x82, 0xa4, 0xa9, 0x0b, 0x5c, 0x04, 0x22
2020-08-16 11:02:41.692 Info, Node006, Sending (Send) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x06, 0x0a, 0x98, 0x80, 0x4d, 0x9c, 0x89, 0xc1, 0x38, 0xaf, 0x5f, 0x88, 0x05, 0x01, 0x34:
2020-08-16 11:02:41.702 Detail, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-08-16 11:02:41.702 Detail, ZW_SEND_DATA delivered to Z-Wave stack
2020-08-16 11:02:41.725 Detail, Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x03, 0xe9
2020-08-16 11:02:41.725 Detail, ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-08-16 11:02:41.830 Detail, Node006, Received: 0x01, 0x21, 0x00, 0x04, 0x00, 0x06, 0x1b, 0x98, 0x81, 0x29, 0xe5, 0xbc, 0xc1, 0x2d, 0x3c, 0x92, 0xa5, 0xee, 0x48, 0xa0, 0x09, 0xe6, 0x63, 0x2b, 0x0a, 0x4d, 0xae, 0x7d, 0x46, 0x84, 0x83, 0x15, 0x5b, 0x0d, 0x7e
2020-08-16 11:02:41.830 Info, Raw: 0x98, 0x81, 0x29, 0xe5, 0xbc, 0xc1, 0x2d, 0x3c, 0x92, 0xa5, 0xee, 0x48, 0xa0, 0x09, 0xe6, 0x63, 0x2b, 0x0a, 0x4d, 0xae, 0x7d, 0x46, 0x84, 0x83, 0x15, 0x5b, 0x0d, 0x7e
2020-08-16 11:02:41.830 Detail, Node006, Decrypted Packet: 0x00, 0x62, 0x03, 0x00, 0x11, 0x02, 0xfe, 0xfe
2020-08-16 11:02:41.830 Detail,
2020-08-16 11:02:41.830 Info, Node006, Received DoorLock report: DoorLock is Unsecure
2020-08-16 11:02:41.830 Detail, Node006, Refreshed Value: old value=true, new value=false, type=bool
2020-08-16 11:02:41.830 Detail, Node006, Changes to this value are not verified
2020-08-16 11:02:41.830 Detail, Node006, Refreshed Value: old value=0, new value=0, type=list
2020-08-16 11:02:41.830 Detail, Node006, Changes to this value are not verified
2020-08-16 11:02:41.830 Detail, Node006, Notification: ValueChanged
2020-08-16 11:02:41.831 Detail, Node006, Notification: ValueChanged
It says DoorLock is unsecure ??? This has worked for YEARS and I’ve had the encryption key forever.
UPDATE:
I’ve rebooted the entire pve server and for now it reports the battery status correctly and will update the lock status. Now how do I see if it is ‘secure’?
UPDATE2:
Ok, the ‘secure’ refers to if it is locked or not, so nothing with the network security key. It seems to be ok again, strange problem that I’ve not seen before on the numerous updates performed over the last year.
disable your new battery entities from the integration or delete the battery entities that you had created manually
Thanks for the update, HA team! Dark mode is awesome!
One small suggestion from a newbie: could you add the ability to rename snapshots from the Supervisor tab UI? I am sure many of us may create a snapshot for a specific reason, prior to a specific update, to see how it affects the system. Sometimes, several snapshots are created on the same day. It would be really helpful if I could have them named in a self-explanatory way, someting like “Aug15_before_Zigbee2MQTT_Update_to_1.14.3”.
Unfortunately, that’s what many people think… 
The owner of the data must fullfill european laws, if your website is distributed inside the EU in the will to generate business/money. Meaning, as soon as you start to earn 0,01€/$ with a page, you are definitively bound to EU law for the pages, that will be displayed in the EU.
The second part would be, that the data is transferred out of the EU, so bound to laws regarding the safety of data. You are not allowed to move data to the US, since the safe haven agreement is no longer in place. If you move data to the US, you are legally bound to write your own data privacy agreement and present the customer with this agreement before he opts in to share his data. If it is possible (in any way) to restructure the data to one specific installation, you may need a double opt-in (the one with the email send…).
On all pages of HA there is a link to NabuCasa, so the first criteria is fullfilled, there is a money-making-interest (means you don’t need to actually make money, it is enough to try…) or at least the connection to a business (NC). Nobody will believe, that Paulus as the owner of NC gives away advertisement space on his “private” page (HA) for free. And even if he did so, the money-making-interest would be hard to deny, the combination between “private” and business pages is to present.
Next part, the data is going to the US (sentry is a US based company), so there needs to be a data privacy agreement in place. Don’t underestimate the effect Trump had on transatlantic relationships. After three and a half years, most judges (at least here in Germany) are very favourable to deny US companies the right to collect and use private data from european customers…
Don’t get me wrong, as I said, it’s none of my business, but I have seen these mistakes first hand, and they were really, really costly mistakes… It’s just to make you aware, that HomeAssistant has outgrown a private project, it is a business with the interest to earn money. Maybe it would be good idea, to meet with an attorney (EU and US law) for a business lunch! 
But I don’t want to spin this further here in this thread, were it doesn’t belong. If you want to @frenck, I’m happy to answer a PN, but as I said, I’m not an attorney!
Good story, but fortunately not correct.
Nevertheless, as said before, you don’t have to enable it.
If this is a concern for you, please do not turn it on.
Not at all, I have it enabled. I hope you are right, my understanding and experience is unfortunately another one. You were warned, don’t cry afterwards. 
It’s easy to opt out of the new telemetry feature, just don’t enable the toggle button (it’s disabled by default).
It’s more challenging to opt out of updater which is enabled by default. It’s one of many integrations that are combined into the default_config option. To opt out of updater, you have to remove default_config and replace it with all the integrations it represents (this is what I have done).
FWIW, there’s a Feature Request to allow default_config to support exclusions. Then you could easily indicate you don’t want updater but still include everything else automatically provided by default_config.
Alternatively, remove all data collection from updater and put it into a new integration that’s off by default (and not part of default_config).
1 Like
You’re right, but that’s not the point. The law is designed for cases, were the possibility is available. If you can turn something on, you need to have a privacy agreement. The customer must be able to read the rules and terms, before opting-in.
The updater component is exactly the same. Turned on or off doesn’t matter, the possibility alone is enough.
But hey, as I said, I’m not an attorney and I hope, my experiences from the past were wrong. Unfortunately these warnings are easily dismissible, but only until someone else wants to make money. I personally know, how to control my data and I take care of that for myself. So I can share my data, if I want to. 
1 Like
Battery levels don’t update on their own without modifying a flag in the cache XML.
I have the same issue.
Since I use YAML mode to configure my UI, I took a hint from one of the replies.
Config:
- type: weather-forecast
entity: weather.home
secondary_info_attribute: precipitation
Here is the state info:
temperature: 9
humidity: 84
pressure: 1024.8
wind_bearing: 16.7
wind_speed: 8.3
attribution: >-
Weather forecast from met.no, delivered by the Norwegian Meteorological
Institute.
forecast:
- datetime: '2020-08-17T12:00:00+02:00'
condition: partlycloudy
pressure: 1015.4
humidity: 62.1
wind_bearing: 331.3
temperature: 12.7
templow: 6.8
precipitation: 98.09999999999997
wind_speed: 31.7
wind_gust: null
- datetime: '2020-08-18T12:00:00+02:00'
condition: partlycloudy
pressure: 1027.1
humidity: 52.1
wind_bearing: 200.2
temperature: 12.5
templow: 5.4
precipitation: 1.4000000000000001
wind_speed: 25.9
wind_gust: null
- datetime: '2020-08-19T12:00:00+02:00'
condition: partlycloudy
pressure: 1029.1
humidity: 53.1
wind_bearing: 195.5
temperature: 14.3
templow: 8
precipitation: 0
wind_speed: 11.5
wind_gust: null
- datetime: '2020-08-20T12:00:00+02:00'
condition: rainy
pressure: 1025
humidity: 81.4
wind_bearing: 270.8
temperature: 14.3
templow: 11.2
precipitation: 2.2
wind_speed: 7.9
wind_gust: null
- datetime: '2020-08-21T12:00:00+02:00'
condition: partlycloudy
pressure: 1022.8
humidity: 47.9
wind_bearing: 349.8
temperature: 20.3
templow: 11.5
precipitation: 0
wind_speed: 7.9
wind_gust: null
friendly_name: Home
As you can see, there is a value for precipitation, but it doesn’t show now.
There is also no value for extrema in the state data – the default when secondary_info_attribute isn’t set explicitly. It’s a little strange that there’s a difference between what one sees when it automatically selects precipitation vs doing so explicitly.
Sorry, but running in the background and preventing hangup signal did not work for me, shell script stops after 60 seconds. Is this 60 sec timeout hardcoded or can i change the value?
For now i go back to V0.113.3
[homeassistant.components.shell_command] Timed out running command:nohup /config/scripts/led.sh {{aquarum}} {{action}} &, after: 60s
I didn’t post that fix. 
I posted that solution, and it worked for me when I tested it running a long running python script (I created one which runs for 5 minutes and it completed with no errors).
One difference I notice is that you aren’t redirecting the output, so try it like this:
nohup /config/scripts/led.sh {{aquarum}} {{action}} > /dev/null 2>&1 &
(you can replace /dev/null with the path to a file if you want the messages logged to a file)
If that doesn’t work, you may need to do it using 2 script files, the first one is called from the shell_command and simply runs the other in the background (this is how my script to update Home Assistant does it). Something like this should work:
Create a new file named led_background.sh in the same folder as led.sh with the following content:
#!/usr/bin/env sh
cd $(dirname $0)
nohup ./led.sh $1 $2 > /dev/null 2>&1 &
Make this executable, and then change your shell_command to /config/scripts/led_background.sh {{aquarum}} {{action}}
Thanks for your reply Steven.
only redirecting the output didn’t work i have tested this also. I will try it with a second starter script, but first for that i have to split my script cause i use its output also for some command_line sensors like the one below. This will make everything a ittle bit more complex. But maybe i will found another solution for my fadeing scenarios.
- platform: command_line
name: led_nanocube_status
scan_interval: 30
command: "/config/scripts/led.sh ip_led_nanocube statusall"
json_attributes:
- power
- brightness
- fadestatus
value_template: '{{ value_json.power }}'
How long does your shell command need to run to avoid it timing out?
after update to 0.114.1 my fritz box integrations are not working anymore
for fritz box as device tracker I get following errors:
Protokolldetails ( ERROR )
Logger: homeassistant.components.device_tracker
Source: components/fritz/device_tracker.py:47
Integration: Geräte-Tracker (documentation, issues)
First occurred: 23:10:55 (1 occurrences)
Last logged: 23:10:55
Error setting up platform legacy
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 159, in _new_conn
conn = connection.create_connection(
File "/usr/local/lib/python3.8/site-packages/urllib3/util/connection.py", line 84, in create_connection
raise err
File "/usr/local/lib/python3.8/site-packages/urllib3/util/connection.py", line 74, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen
httplib_response = self._make_request(
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 392, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.8/http/client.py", line 1240, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.8/http/client.py", line 1286, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.8/http/client.py", line 1235, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.8/http/client.py", line 1006, in _send_output
self.send(msg)
File "/usr/local/lib/python3.8/http/client.py", line 946, in send
self.connect()
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 187, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 171, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x65857628>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 726, in urlopen
retries = retries.increment(
File "/usr/local/lib/python3.8/site-packages/urllib3/util/retry.py", line 439, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.200.1', port=49000): Max retries exceeded with url: /igddesc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x65857628>: Failed to establish a new connection: [Errno 111] Connection refused'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/device_tracker/setup.py", line 63, in async_setup_legacy
scanner = await hass.async_add_job(
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/fritz/device_tracker.py", line 30, in get_scanner
scanner = FritzBoxScanner(config[DOMAIN])
File "/usr/src/homeassistant/homeassistant/components/fritz/device_tracker.py", line 47, in __init__
self.fritz_box = FritzHosts(
File "/usr/local/lib/python3.8/site-packages/fritzconnection/lib/fritzbase.py", line 21, in __init__
fc = FritzConnection(**kwargs)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/core/fritzconnection.py", line 109, in __init__
self.device_manager.add_description(source)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/core/devices.py", line 61, in add_description
root = get_xml_root(source, timeout=self.timeout, session=self.session)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/core/utils.py", line 56, in get_xml_root
source = get_content_from(source, timeout=timeout, session=session)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/core/utils.py", line 38, in get_content_from
with session.get(url) as response:
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 543, in get
return self.request('GET', url, **kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 530, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 643, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.200.1', port=49000): Max retries exceeded with url: /igddesc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x65857628>: Failed to establish a new connection: [Errno 111] Connection refused')
and for my fritz box netmonitor I get following errors:
Protokolldetails ( ERROR )
Logger: homeassistant.components.sensor
Source: components/fritzbox_netmonitor/sensor.py:53
Integration: Sensor (documentation, issues)
First occurred: 23:10:48 (1 occurrences)
Last logged: 23:10:48
Error while setting up fritzbox_netmonitor platform for sensor
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 159, in _new_conn
conn = connection.create_connection(
File "/usr/local/lib/python3.8/site-packages/urllib3/util/connection.py", line 84, in create_connection
raise err
File "/usr/local/lib/python3.8/site-packages/urllib3/util/connection.py", line 74, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 670, in urlopen
httplib_response = self._make_request(
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 392, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.8/http/client.py", line 1240, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.8/http/client.py", line 1286, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.8/http/client.py", line 1235, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.8/http/client.py", line 1006, in _send_output
self.send(msg)
File "/usr/local/lib/python3.8/http/client.py", line 946, in send
self.connect()
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 187, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 171, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x672a3328>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 726, in urlopen
retries = retries.increment(
File "/usr/local/lib/python3.8/site-packages/urllib3/util/retry.py", line 439, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.200.1', port=49000): Max retries exceeded with url: /igddesc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x672a3328>: Failed to establish a new connection: [Errno 111] Connection refused'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 184, in _async_setup_platform
await asyncio.shield(task)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/fritzbox_netmonitor/sensor.py", line 53, in setup_platform
fstatus = FritzStatus(address=host)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/lib/fritzstatus.py", line 24, in __init__
super().__init__(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/lib/fritzbase.py", line 21, in __init__
fc = FritzConnection(**kwargs)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/core/fritzconnection.py", line 109, in __init__
self.device_manager.add_description(source)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/core/devices.py", line 61, in add_description
root = get_xml_root(source, timeout=self.timeout, session=self.session)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/core/utils.py", line 56, in get_xml_root
source = get_content_from(source, timeout=timeout, session=session)
File "/usr/local/lib/python3.8/site-packages/fritzconnection/core/utils.py", line 38, in get_content_from
with session.get(url) as response:
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 543, in get
return self.request('GET', url, **kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 530, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 643, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.200.1', port=49000): Max retries exceeded with url: /igddesc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x672a3328>: Failed to establish a new connection: [Errno 111] Connection refused'))
anyone seeing the same issues?
I’ve since tested 114.1 on my test platform and it seems to be ok with the REST sensors. The problem on 114.0 was able to be recreated, so it was definitely there in 114.0