Unable to select user 251

User avatar
durosity
Posts: 4810
Joined: Thu May 10, 2012 3:21 pm
Location: Newcastle Upon Tyne, Ye Ol' England.

Re: Unable to select user 251

Post by durosity »

Don’t suppose you’ve had a chance to have a look at this have you? (Just to pre-empt.. I’m not demanding anything.. I’m just curious.. in every sense of the word. ;) )
Computer says no.
howartp
Posts: 4559
Joined: Thu Jan 09, 2014 4:43 pm
Location: West Yorkshire, UK

Re: Unable to select user 251

Post by howartp »

Give 1.0.47 a go.
CliveS
Posts: 864
Joined: Sun Jan 10, 2016 5:31 am
Location: Medomsley, County Durham, UK

Re: Unable to select user 251

Post by CliveS »

howartp wrote:Give 1.0.47 a go.
Tried but get red on all existing items and Lock Manager does not show up in drop down menus
CliveS

Indigo 2024.2.1 : macOS Sequoia 15.6.1 : Mac Mini M2 : 8‑core CPU and 10‑core GPU : 8 GB : 256GB 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
User avatar
durosity
Posts: 4810
Joined: Thu May 10, 2012 3:21 pm
Location: Newcastle Upon Tyne, Ye Ol' England.

Re: Unable to select user 251

Post by durosity »

Alas same issue as Clive.. log results with debug on:

24 Nov 2017, 23:04:53
Reloading plugin "Z-Wave Lock Manager 1.0.47"
Starting plugin "Z-Wave Lock Manager 1.0.47" (pid 67578)
Z-Wave Lock Manager Error Events.xml has an error: mismatched tag: line 277, column 3
Z-Wave Lock Manager Error Events.xml is malformed
Stopping plugin "Z-Wave Lock Manager 1.0.47" (pid 67578)
Computer says no.
howartp
Posts: 4559
Joined: Thu Jan 09, 2014 4:43 pm
Location: West Yorkshire, UK

Re: Unable to select user 251

Post by howartp »

Sorry, I didn't actually test it before releasing. :)

v1.0.48 is tested to load ok, but I can't test 251.

Peter
CliveS
Posts: 864
Joined: Sun Jan 10, 2016 5:31 am
Location: Medomsley, County Durham, UK

Re: Unable to select user 251

Post by CliveS »

howartp wrote:Sorry, I didn't actually test it before releasing. :)

v1.0.48 is tested to load ok, but I can't test 251.

Peter
Peter,

It works fine, and all the options are their to use Master Code, but I did find one problem.

If I copy a trigger then it retains the ID of the trigger (i.e. user 30) and is greyed out but a new trigger puts 251 in its place and is also greyed out as the code specifies.
The errors "Z-Wave Error no nonce reply (055) for setLockValue (re-sending)" I think are my Gen5 Aeotec Stick unless anyone can throw any light on the error.

Code: Select all

25 Nov 2017, 14:44:32
   Stopping plugin Z-Wave Lock Manager (pid 693)
   Stopped plugin Z-Wave Lock Manager
   Upgrading plugin Z-Wave Lock Manager to newer version 1.0.48 (previous version moved to trash)
   Loading plugin "Z-Wave Lock Manager 1.0.48"
   Starting plugin "Z-Wave Lock Manager 1.0.48" (pid 67961)
   Started plugin "Z-Wave Lock Manager 1.0.48"
   Email Scanned                   from "[email protected]"; subject "Topic reply notification - "Unable to select user 251""

25 Nov 2017, 14:44:55
   Z-Wave                          received "055 - Front Door Keypad Lock" status update battery level 90%

25 Nov 2017, 14:45:21
   Z-Wave                          received "Front Door Keypad Lock" status update unlocked (manually)
   Z-Wave Lock Manager             Status: Door unlocked manually [Node: 55]
   Z-Wave                          received "Drive Front Door Motion Sensor" status update is on
   Z-Wave                          received "Front Door Keypad Lock" status update locked (manually)
   Z-Wave Lock Manager             Status: Door locked manually [Node: 55]
   Z-Wave                          received "Drive Front Door Motion Sensor" status update is on
   Z-Wave                          received "Front Door Keypad Lock" status update unlocked by user 251 (via keypad) 
   Z-Wave Lock Manager             Status: User 251 unlocked door [Node: 55]
   Z-Wave                          received "Front Door Keypad Lock" status update unlocked (manually)
   Z-Wave Lock Manager             Status: Door unlocked manually [Node: 55]
   Z-Wave                          received "Drive Front Door Motion Sensor" status update is off
   Z-Wave                          received "Front Door Keypad Lock" status update locked (manually)
   Z-Wave Lock Manager             Status: Door locked manually [Node: 55]

25 Nov 2017, 14:50:55
   Z-Wave                          sent "Front Door Keypad Lock" unlock

25 Nov 2017, 14:51:14
   Z-Wave Error                    no nonce reply (055) for setLockValue (re-sending)
   Z-Wave Error                    no nonce reply (055) for setLockValue (re-sending)
   Z-Wave                          sent "Front Door Keypad Lock" lock
   Z-Wave Error                    no nonce reply (055) for setLockValue (re-sending)
   Z-Wave Error                    no nonce reply (055) for setLockValue (re-sending)

25 Nov 2017, 14:52:11
   Z-Wave                          sent "Front Door Keypad Lock" lock
   Z-Wave                          received "Front Door Keypad Lock" status update locked (via controller)
   Z-Wave Lock Manager             Status: Door locked by Indigo [Node: 55]

25 Nov 2017, 14:52:27
   Z-Wave                          sent "Front Door Keypad Lock" unlock
   Z-Wave                          received "Front Door Keypad Lock" status update unlocked (via controller)
   Z-Wave Lock Manager             Status: Door unlocked by Indigo [Node: 55]

25 Nov 2017, 14:52:59
   Z-Wave                          received "Front Door Keypad Lock" status update locked (via timer)
   Z-Wave Lock Manager             Status: Door re-locked automatically [Node: 55]
   Z-Wave                          sent "Front Door Keypad Lock" lock
   Z-Wave                          sent "Front Door Keypad Lock" lock
   Z-Wave                          received "Front Door Keypad Lock" status update locked (via controller)
   Z-Wave Lock Manager             Status: Door locked by Indigo [Node: 55]
CliveS

Indigo 2024.2.1 : macOS Sequoia 15.6.1 : Mac Mini M2 : 8‑core CPU and 10‑core GPU : 8 GB : 256GB 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
User avatar
durosity
Posts: 4810
Joined: Thu May 10, 2012 3:21 pm
Location: Newcastle Upon Tyne, Ye Ol' England.

Re: Unable to select user 251

Post by durosity »

Yeah I’m getting the same, but seems to work fine with brand new triggers I previously setup so I’m happy!
Computer says no.
User avatar
durosity
Posts: 4810
Joined: Thu May 10, 2012 3:21 pm
Location: Newcastle Upon Tyne, Ye Ol' England.

Re: Unable to select user 251

Post by durosity »

So I’ve noticed occasionally that the plugin doesn’t fire the trigger its supposed to. Here’s the log from the most recent incident:

DSC Alarm Entry Delay. (Partition 1 'House')
DSC Alarm Alarm Zone 'Hall - Front Door Sensor' Opened.
Z-Wave Lock Manager Debug Node ID 38 (Hex 38) found in lockIDs
Z-Wave received "Hall - Front Door Lock" status update unlocked by user 251 (via keypad)
Z-Wave Lock Manager Debug Node ID 38 (Hex 38) found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 26 04 71 05 13 FB FF
Z-Wave Lock Manager Status: User 251 unlocked door [Node: 38]
Z-Wave Lock Manager Debug triggerEvent called: unlockedByMasterCode
Z-Wave Lock Manager Debug ---
Z-Wave Lock Manager Debug dNodeID: #38#
Z-Wave Lock Manager Debug eventNode: #38#
Z-Wave Lock Manager Debug dUserNo: #251#
Z-Wave Lock Manager Debug userNo: #251#
Z-Wave Lock Manager Debug Executing trigger
Z-Wave Lock Manager Debug Updating state: lockState
Z-Wave Lock Manager Debug -----
Z-Wave Lock Manager Debug Node ID 38 (Hex 38) found in lockIDs
Trigger Motion: Hall - Motion Detected (Turn On Ambient Lights)
Z-Wave Lock Manager Debug Node ID 38 (Hex 38) found in lockIDs
Z-Wave received "Hall - Front Door Lock" status update locked (via timer)
Z-Wave Lock Manager Debug Node ID 38 (Hex 38) found in lockIDs
Z-Wave Lock Manager Debug Raw: 01 0A 00 04 00 26 04 71 05 1B 01 FF
Z-Wave Lock Manager Status: Door re-locked automatically [Node: 38]
Z-Wave Lock Manager Debug triggerEvent called: relockedAuto
Z-Wave Lock Manager Debug Updating state: lockState
Z-Wave Lock Manager Debug -----
Z-Wave Lock Manager Debug Node ID 38 (Hex 38) found in lockIDs

Now in there usually there’d be something about the trigger “Door: Front Door Unlocked By Mike” in there but intermittently it just doesn’t seem to fire. It’s not the trigger itself as its conditions are set to always run. Any ideas on what could be stopping it from the above? (FYI It does it for all users, not just the master one)
Computer says no.
Post Reply

Return to “ZWave Lock Manager”