Lock Manager Time Update Bug

Posted on
Tue Jul 11, 2017 2:06 pm
CliveS offline
Posts: 414
Joined: Jan 10, 2016
Location: Medomsley, County Durham, UK

Lock Manager Time Update Bug

Just noticed that the RTC is failing since the 1.0.37 update (quick to spot these things I am not!!!)

All logs up to then show

2017-05-31 00:00:00.070 Application Created new log file (Indigo Server version 7.0.3)
2017-05-31 00:00:00.070 Schedule Front Door Lock Time Set
2017-05-31 00:00:01.728 Z-Wave Lock Manager Setting lock time to 31/5/2017 0:0:1 (UK format DD/MM/YYYY HH:MM:SS)
2017-05-31 00:00:02.085 Z-Wave sent "Front Door Keypad Lock" raw command [xx xx xx xx xx xx 00 00 01]

I updated the plugin

2017-05-31 07:58:57.543 Application Stopping plugin Z-Wave Lock Manager (pid 458)
2017-05-31 07:58:58.671 Application Stopped plugin Z-Wave Lock Manager
2017-05-31 07:58:58.671 Application Upgrading plugin Z-Wave Lock Manager to newer version 1.0.37 (previous version moved to trash)
2017-05-31 07:58:58.729 Application Loading plugin "Z-Wave Lock Manager 1.0.37"
2017-05-31 07:58:58.731 Application Starting plugin "Z-Wave Lock Manager 1.0.37" (pid 2952)
2017-05-31 07:58:59.163 Application Started plugin "Z-Wave Lock Manager 1.0.37"
2017-05-31 08:00:00.525 Z-Wave received "055 - Front Door Keypad Lock" status update battery level 90%
2017-05-31 08:08:16.569 Schedule Front Door Lock Time Set
2017-05-31 08:08:16.572 Z-Wave Lock Manager Setting lock time to 31/5/2017 8:8:16 (UK format DD/MM/YYYY HH:MM:SS)
2017-05-31 08:08:16.627 Z-Wave Lock Manager Error Error in plugin execution ExecuteAction:

Traceback (most recent call last):
File "plugin.py", line 189, in setRTC
InvalidParameter: could not find module/node for action

2017-05-31 08:10:06.607 Action Group Front Door Lock Wrong Code Set Limit & Timeout
2017-05-31 08:10:06.609 Z-Wave Lock Manager Setting incorrect code limit to 3 attempts with 60 second timeout:
2017-05-31 08:10:06.629 Z-Wave Lock Manager Error Error in plugin execution ExecuteAction:

Traceback (most recent call last):
File "plugin.py", line 224, in setWrongLimit
InvalidParameter: could not find module/node for action

Further updates cured the setWrongLimit problem and I thought no more about it but it seems the setRTC is still not happy.

CliveS

CliveS

Indigo 7.4.0 : MacOS High Sierra 10.13.6 : Mac mini Server (Mid 2011) : 2 GHz Core i7. : 8 GB. : 2 x 256GB Samsung EVO SSD
----------------------------------------------------------------------------------
The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer

Posted on
Tue Jul 11, 2017 3:26 pm
howartp offline
Posts: 3667
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Lock Manager Time Update Bug

Can you post current logs showing the error as those line numbers don't match up with the v1.0.42 codebase so I can't debug it.

Peter

Posted on
Tue Jul 11, 2017 4:05 pm
CliveS offline
Posts: 414
Joined: Jan 10, 2016
Location: Medomsley, County Durham, UK

Re: Lock Manager Time Update Bug

Peter,

11 Jul 2017, 23:01:36
Z-Wave received "En Suite Floor Heating Thermostat" heat setpoint is 15.0 °C
Disabling plugin "Z-Wave Lock Manager 1.0.42"
Stopping plugin "Z-Wave Lock Manager 1.0.42" (pid 19236)
Stopped plugin "Z-Wave Lock Manager 1.0.42"
Enabling plugin "Z-Wave Lock Manager 1.0.42"
Starting plugin "Z-Wave Lock Manager 1.0.42" (pid 64757)
Started plugin "Z-Wave Lock Manager 1.0.42"

11 Jul 2017, 23:02:14
Schedule Front Door Lock Time Set
Z-Wave Lock Manager Setting lock time to 11/7/2017 23:2:14 (UK format DD/MM/YYYY HH:MM:SS)
Z-Wave Lock Manager Error Error in plugin execution ExecuteAction:

Traceback (most recent call last):
File "plugin.py", line 200, in setRTC
InvalidParameter: could not find module/node for action

CliveS

CliveS

Indigo 7.4.0 : MacOS High Sierra 10.13.6 : Mac mini Server (Mid 2011) : 2 GHz Core i7. : 8 GB. : 2 x 256GB Samsung EVO SSD
----------------------------------------------------------------------------------
The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer

Posted on
Sat Jul 22, 2017 4:54 am
howartp offline
Posts: 3667
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Lock Manager Time Update Bug

Fixed in 1.0.43 released this morning.

Peter

Posted on
Sat Jul 22, 2017 5:56 am
CliveS offline
Posts: 414
Joined: Jan 10, 2016
Location: Medomsley, County Durham, UK

Re: Lock Manager Time Update Bug

howartp wrote:
Fixed in 1.0.43 released this morning.


Thank you Peter, as you say, Fixed.

CliveS

CliveS

Indigo 7.4.0 : MacOS High Sierra 10.13.6 : Mac mini Server (Mid 2011) : 2 GHz Core i7. : 8 GB. : 2 x 256GB Samsung EVO SSD
----------------------------------------------------------------------------------
The best way to get the right answer on the Internet is not to ask a question, it's to post the wrong answer

Posted on
Sun Jul 23, 2017 6:50 pm
durosity offline
User avatar
Posts: 3810
Joined: May 10, 2012
Location: Newcastle Upon Tyne, Ye Ol' England.

Re: Lock Manager Time Update Bug

(ignore - posted in wrong part of forum)
Last edited by durosity on Sun Jul 23, 2017 7:31 pm, edited 1 time in total.

Computer says no.

Posted on
Sun Jul 23, 2017 7:06 pm
roquej offline
User avatar
Posts: 323
Joined: Jan 04, 2015

Re: Lock Manager Time Update Bug

howartp wrote:
Can you post current logs showing the error as those line numbers don't match up with the v1.0.42 codebase so I can't debug it.

Peter


Peter - the error logs i last posted were after upgrading to .43. Sorry, but not sure what you mean.

JP

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 1 guest

cron