You can see in the attached image the control panel is not populating.
I've removed and re-added the device.
The Real-Time Log produces a mono application exception
Can someone point me in the right direction?
Current Date/Time: 5/15/2019 4:48:05 PM
HomeSeer Version: HS3 Standard Edition 3.0.0.531
Linux version: Linux HomeTrollerSELv3 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:56:17 UTC 2014 i686 i686 i686 GNU/Linux System Uptime: 0 Days 20 Hours 15 Minutes 50 Seconds
IP Address: 10.30.1.101
Number of Devices: 184
Number of Events: 4
Available Threads: 199
HSTouch Enabled: True
Event Threads: 1
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Enabled Plug-Ins
2.0.11.0: BLEditor
3.0.25.0: BLLock
3.0.1.252: Z-Wave
I've removed and re-added the device.
Add Node started...
Activate the 'Add to Network' function on the device...
A new node is being added...
Adding a new SLAVE NODE...
DONE - Add Node Operation is Complete.
Done. Node 60 Added.
Reloading (importing) node information...
Synchronizing node information with HomeSeer and creating new device(s) as necessary...
Synchronize nodes finished. Number of device nodes to be created/added = 1
Adding using S0 Security, Negotiating or Verifying SECURITY SCHEME for node 60
Z-Wave Security Scheme and Key Exchange was successful for node 60, now waiting for the device to finish storing information before proceeding...
Getting SECURITY class information for node 60
Z-Wave manufacturer information for node 60, ID: 297=129H (Assa Abloy), Type: 32772=8004H, ID: 1536=600H
Node: 60 Supports Class(es): ZWAVEPLUS_INFO_V2, MANUFACTURER_SPECIFIC, SECURITY, DEVICE_RESET_LOCALLY, POWERLEVEL, VERSION
Node: 60 Supports Secure Class(es): BATTERY, DOOR_LOCK_V2, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, ALARM_V2, CONFIGURATION_V3, USER_CODE, TIME, TIME_PARAMETERS, DOOR_LOCK_LOGGING, SCHEDULE_ENTRY_LOCK_V2, FIRMWARE_UPDATE_MD
Node 60 is Z-Wave version: Lib: 4.24 App: 1.77
Node 60 is a Z-Wave Plus node. Retrieving ZWPlus Info...
Node 60 Supports 2 Notification Types: Access_Control Power_Management
Access_Control Supports Events: Manual Lock Operation(1), Manual Unlock Operation(2), RF Lock Operation(3), RF Unlock Operation(4), Keypad Lock Operation(5), Keypad Unlock Operation(6), Auto Lock Locked Operation(9), Lock Jammed(11), All User Codes Deleted(12), Single User Code Deleted(13), New User Code Added(14), New User Code Not Added due to Duplicate Code(15), Keypad Temporarily Disabled(16), New Program Code Entered Unique Code for Lock Configuration(18)
Power_Management Supports Events: Power Applied(1), Replace Battery Soon(10), Replace Battery Now(11)
All associations for node 60 have been retrieved successfully, it supports associations on these groups: 1.
Root Node Device Node 60 Z-Wave Assa Abloy Entry Control was created for node 60 on network E08CA6B3
Zwave SmartStick+: Adding association for Z-Wave device Node 60 Z-Wave Assa Abloy Entry Control (Node 60, Group 1) to HomeSeer
Enabling Lock status for Assa Abloy (Yale) device Node 60 Z-Wave Assa Abloy Entry Control (60)
5 out of 6 Child devices of node 60 were created successfully.
Finished.
Activate the 'Add to Network' function on the device...
A new node is being added...
Adding a new SLAVE NODE...
DONE - Add Node Operation is Complete.
Done. Node 60 Added.
Reloading (importing) node information...
Synchronizing node information with HomeSeer and creating new device(s) as necessary...
Synchronize nodes finished. Number of device nodes to be created/added = 1
Adding using S0 Security, Negotiating or Verifying SECURITY SCHEME for node 60
Z-Wave Security Scheme and Key Exchange was successful for node 60, now waiting for the device to finish storing information before proceeding...
Getting SECURITY class information for node 60
Z-Wave manufacturer information for node 60, ID: 297=129H (Assa Abloy), Type: 32772=8004H, ID: 1536=600H
Node: 60 Supports Class(es): ZWAVEPLUS_INFO_V2, MANUFACTURER_SPECIFIC, SECURITY, DEVICE_RESET_LOCALLY, POWERLEVEL, VERSION
Node: 60 Supports Secure Class(es): BATTERY, DOOR_LOCK_V2, ASSOCIATION, ASSOCIATION_GRP_INFO_V2, ALARM_V2, CONFIGURATION_V3, USER_CODE, TIME, TIME_PARAMETERS, DOOR_LOCK_LOGGING, SCHEDULE_ENTRY_LOCK_V2, FIRMWARE_UPDATE_MD
Node 60 is Z-Wave version: Lib: 4.24 App: 1.77
Node 60 is a Z-Wave Plus node. Retrieving ZWPlus Info...
Node 60 Supports 2 Notification Types: Access_Control Power_Management
Access_Control Supports Events: Manual Lock Operation(1), Manual Unlock Operation(2), RF Lock Operation(3), RF Unlock Operation(4), Keypad Lock Operation(5), Keypad Unlock Operation(6), Auto Lock Locked Operation(9), Lock Jammed(11), All User Codes Deleted(12), Single User Code Deleted(13), New User Code Added(14), New User Code Not Added due to Duplicate Code(15), Keypad Temporarily Disabled(16), New Program Code Entered Unique Code for Lock Configuration(18)
Power_Management Supports Events: Power Applied(1), Replace Battery Soon(10), Replace Battery Now(11)
All associations for node 60 have been retrieved successfully, it supports associations on these groups: 1.
Root Node Device Node 60 Z-Wave Assa Abloy Entry Control was created for node 60 on network E08CA6B3
Zwave SmartStick+: Adding association for Z-Wave device Node 60 Z-Wave Assa Abloy Entry Control (Node 60, Group 1) to HomeSeer
Enabling Lock status for Assa Abloy (Yale) device Node 60 Z-Wave Assa Abloy Entry Control (60)
5 out of 6 Child devices of node 60 were created successfully.
Finished.
Application Exception System.Web.Compilation.CompilationException
error VBNC30248: CHANGEME
Description: Error compiling a resource required to service this request. Review your source file and modify it to fix this error.
Details: error VBNC30248: CHANGEME
Error origin: Compiler
Error source file: ~/Global.asax
Exception stack trace:
at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath, System.CodeDom.Compiler.CompilerParameters options) [0x00312] in <3ec20b6a386e451c9090db8d308c8dfe>:0 at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath) [0x00008] in <3ec20b6a386e451c9090db8d308c8dfe>:0 at System.Web.Compilation.BuildManager.GenerateAssembly (System.Web.Compilation.AssemblyBuilder abuilder, System.Web.Compilation.BuildProviderGroup group, System.Web.VirtualPath vp, System.Boolean debug) [0x00202] in <3ec20b6a386e451c9090db8d308c8dfe>:0 at System.Web.Compilation.BuildManager.BuildInner (System.Web.VirtualPath vp, System.Boolean debug) [0x00106] in <3ec20b6a386e451c9090db8d308c8dfe>:0
Version Information: 5.20.1.19 (tarball Thu Apr 11 09:14:25 UTC 2019); ASP.NET Version: 4.0.30319.42000
error VBNC30248: CHANGEME
Description: Error compiling a resource required to service this request. Review your source file and modify it to fix this error.
Details: error VBNC30248: CHANGEME
Error origin: Compiler
Error source file: ~/Global.asax
Exception stack trace:
at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath, System.CodeDom.Compiler.CompilerParameters options) [0x00312] in <3ec20b6a386e451c9090db8d308c8dfe>:0 at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath) [0x00008] in <3ec20b6a386e451c9090db8d308c8dfe>:0 at System.Web.Compilation.BuildManager.GenerateAssembly (System.Web.Compilation.AssemblyBuilder abuilder, System.Web.Compilation.BuildProviderGroup group, System.Web.VirtualPath vp, System.Boolean debug) [0x00202] in <3ec20b6a386e451c9090db8d308c8dfe>:0 at System.Web.Compilation.BuildManager.BuildInner (System.Web.VirtualPath vp, System.Boolean debug) [0x00106] in <3ec20b6a386e451c9090db8d308c8dfe>:0
Version Information: 5.20.1.19 (tarball Thu Apr 11 09:14:25 UTC 2019); ASP.NET Version: 4.0.30319.42000
Can someone point me in the right direction?
Current Date/Time: 5/15/2019 4:48:05 PM
HomeSeer Version: HS3 Standard Edition 3.0.0.531
Linux version: Linux HomeTrollerSELv3 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:56:17 UTC 2014 i686 i686 i686 GNU/Linux System Uptime: 0 Days 20 Hours 15 Minutes 50 Seconds
IP Address: 10.30.1.101
Number of Devices: 184
Number of Events: 4
Available Threads: 199
HSTouch Enabled: True
Event Threads: 1
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Enabled Plug-Ins
2.0.11.0: BLEditor
3.0.25.0: BLLock
3.0.1.252: Z-Wave
Comment