lindehoff wrote:
DrLaban wrote:I get this error after the update. The unit which is the siren startet to report these errors. All other devices seems to be OK.
Unable to update device state on server. Device: Kjøkken - Temp - Verisure, Reason: 'ascii' codec can't encode character u'\xf8' in position 2: ordinal not in range(128)
Error IllegalParameterError -- device value type for state key sensorValue must be real
Did you change anything with the character set in the new release? I deleted the Device called "Kjøkken - Temp - Verisure" and created a new called "Kitchen - Temp - Verisure".
Seems OK now. Didn't have this problem in the previous version. It could be the Norwegian character Ø that is causing the problem.
lindehoff wrote:DrLaban wrote:I get this error after the update. The unit which is the siren startet to report these errors. All other devices seems to be OK.
Unable to update device state on server. Device: Kjøkken - Temp - Verisure, Reason: 'ascii' codec can't encode character u'\xf8' in position 2: ordinal not in range(128)
Error IllegalParameterError -- device value type for state key sensorValue must be real
Did you change anything with the character set in the new release? I deleted the Device called "Kjøkken - Temp - Verisure" and created a new called "Kitchen - Temp - Verisure".
Seems OK now. Didn't have this problem in the previous version. It could be the Norwegian character Ø that is causing the problem.
I've added it as a bug, #10, and look in to it as soon as I can.
Did it work before the update?
DrLaban wrote:Did it work before the update?
DrLaban wrote:I notice that this error was introduced in the latest version too
27 Nov 2015 11:40:03
Verisure Error invalid syntax (<string>, line 34), trying to relogging in
27 Nov 2015 11:47:13
Verisure Error invalid syntax (<string>, line 34), trying to relogging in
27 Nov 2015 14:06:45
Verisure Error invalid syntax (<string>, line 34), trying to relogging in
Happend a couple of times last night and three times today.
DrLaban wrote:Just downloaded the latest version (0.2.5) and installed it but it states that it is 0.2.0 inside Indigo.
Reloading plugin "Verisure 0.2.5"
Stopping plugin "Verisure 0.2.5" (pid 88239)
Verisure Debug shutdown called
Z-Wave received "Ventilation unit" energy total to 330.316 kWh
Stopped plugin "Verisure 0.2.5"
Starting plugin "Verisure 0.2.5" (pid 88249)
Started plugin "Verisure 0.2.5"
Verisure Debug startup called
Verisure Debug Debug is set to: True
Verisure Debug Checking status for all Verisure Devices
Verisure Error Error in plugin execution runConcurrentThread:
Traceback (most recent call last):
File "plugin.py", line 91, in runConcurrentThread
File "plugin.py", line 155, in _refreshAlarmStatesFromVerisure
File "plugin.py", line 159, in _updateDevUI
File "plugin.py", line 214, in secSinceLastUpdate
File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/_strptime.py", line 325, in _strptime
<type 'exceptions.ValueError'>: time data '' does not match format '%Y-%m-%d %H:%M:%S'
Verisure Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
Disabling plugin "Verisure 0.2.5"
Stopping plugin "Verisure 0.2.5" (pid 88249)
Verisure Debug shutdown called
Users browsing this forum: No registered users and 27 guests