Page 1 of 1

Evohome - error on initial update

Posted: Saturday 15 August 2015 15:12
by joenevd
I tried installing the evohome client by following the instructions on:
http://www.domoticz.com/wiki/Evohome

At the step "Create the initial Domoticz hardware device and zones make sure Python and the evohome-client are installed before running this", I receive an error and nothing is being created.

pi@raspberrypi ~/evohome-client $ /home/pi/evohome-client/evo-update.sh init
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/late ... ormwarning.
InsecurePlatformWarning
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/late ... ormwarning.
InsecurePlatformWarning
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/late ... ormwarning.
InsecurePlatformWarning
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/late ... ormwarning.
InsecurePlatformWarning
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/late ... ormwarning.
InsecurePlatformWarning
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/late ... ormwarning.
InsecurePlatformWarning
Traceback (most recent call last):
File "/home/pi/evohome-client/evo-update.sh", line 52, in <module>
r=requests.get("http://%s:%s/json.htm?type=command&param=addhardware&htype=40&port=1&name=%s&enabled=true&datatimeout=0" % (evoconfig.url,evoconfig.port,hwname))
File "/usr/local/lib/python2.7/dist-packages/requests/api.py", line 69, in get
return request('get', url, params=params, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/api.py", line 50, in request
response = session.request(method=method, url=url, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 465, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 573, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/requests/adapters.py", line 415, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', error(111, 'Connection refused'))

Does anyone know what I need to do to solve this?

Re: Evohome - error on initial update

Posted: Sunday 23 August 2015 8:25
by Crazy2
Since yesterday i'm having following problems with the script.

Traceback (most recent call last):
File "evo-update.py", line 56, in <module>
hwl=json.loads(r.text)
File "/usr/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 365, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 383, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

running evohome with the gateway

Problem solved. Changed raspberry to static ip and script didnt connect to 127.0.0.1 anymore

Re: Evohome - error on initial update

Posted: Sunday 23 August 2015 11:22
by Dlanor
joenevd wrote: /usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/late ... ormwarning.
InsecurePlatformWarning
I have the same problem but no solution.

Re: Evohome - error on initial update

Posted: Monday 24 August 2015 0:44
by Crazy2

Code: Select all

sudo pip install requests==2.5.3
fixed it for me

Re: Evohome - error on initial update

Posted: Saturday 12 September 2015 18:16
by joenevd
That solved the warnings, thank you!
Now I am able to retrieve the temperatures every minute.

When I want to change some settings, nothing happends. Does someone know why and how I can solve this?

Re: Evohome - error on initial update

Posted: Tuesday 06 September 2016 20:45
by Lebo2d9
I had the same problem as Crasy2
Crazy2 wrote:Post by Crazy2 ยป Sunday 23 August 2015 8:25
Since yesterday i'm having following problems with the script.

Traceback (most recent call last):
File "evo-update.py", line 56, in <module>
hwl=json.loads(r.text)
File "/usr/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 365,
I realised me that I was using "Website protection" after adding "127.0.0.*" to the local networks the problem was solved.

Kind regards
Koen

Re: Evohome - error on initial update

Posted: Friday 02 December 2016 8:40
by Kerel
Thanks :). You don't seem to think about that setting, when reading the error thrown by the evoclient :).