Lost connection to devices

[slocanlarry]

When I first loaded the BLSecurity plug-in and added devices, they appeared to work. After configuring the various inputs now the devices aren't connected to the Plug-ion, although they are valid devices in HS. I tried deleting and adding devices. I restarted the plug-in. I restarted the computer. I restored a previous back-up.

Any ideas? Do I have to start all over again?







Current Date/Time: 2/4/2018 10:03:59 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.368
Operating System: Microsoft Windows 10 Home - Work Station
System Uptime: 0 Days 22 Hours 10 Minutes 55 Seconds
IP Address: 192.168.1.111
Number of Devices: 415
Number of Events: 231
Available Threads: 800

Enabled Plug-Ins
3.0.0.29: ADIO-100
2.0.49.0: BLBackup
2.0.35.0: BLSecurity
1.0.3.0: BLShutdown
2.0.22.0: BLUPS
1.2.2.0: Device History
3.0.6.3: Insteon Thermostat
3.0.6.23: Insteon

[Blade]

Attach your hspi_BLSecurity.ini file zipped
It is in the config folder

[slocanlarry]

config file attached

thanks for prompt reply to my post...

[Blade]

I see lots of devices in there
Do this for me:

1. Disable BLSecurity
2. Edit the hspi_BLSecurity.ini file and change debugLevel=true
3. Save INI file
4. Re-enable BLSecurity

Once it is running for a minute, then go to the options page in the plugin and turn off debug logging

Attach the BLSecurity-Detailed.log zipped so I can see it
It is in the HS3 root folder

[slocanlarry]

log file attached

here's the log file - thanks

[Blade]

I see 23 devices getting loaded
Can you tell what you mean by the devices are not connected to the plugin

[slocanlarry]

The devices how up as legitimate devices in the plug-in. When I arm the system, they don't trigger an alarm when their status changes. When I use the mouse-hover option, they don't show current status - just blank.

I did get one device to arm and set off an alert - I had deleted then added it again as a value-triggered device. Do i need to do this for all devices that I load? It is an Insteon hidden door sensor with a value from 0 (closed) to 100 (open). It still does not display current status. It appears to be the only device that triggers an alert. I also use ADIO100 digital relay motion detector devices that I want to add. They all work fine in Homeseer.

thanks again for your help.

[Blade]

I would delete them and re-add them as value triggered and see how that goes

[mr.Magoo]

Bumping this thread as I'm having very similar issues.
Have tried to delete/add the sensors back in, did enable the detailed log but I think there might be an unit issue since it stop logging right around 10,000 bytes rather than MB
and it still logs the shutdown of the plugin but nothing else.

The plugin lists all units but I can't get it to trigger an alarm (no log in HS3 event log and debug log is cut short).

8/27/2019 9:13:50 PM : v - **************** Debug Logging ENABLED at 8/27/2019 9:13:50 PM ****************
8/27/2019 9:13:50 PM : v - **************** Debug Log size limit --> 10000 MB
8/27/2019 9:13:50 PM : v - InitIO started
8/27/2019 9:13:50 PM : v - Linux() started
8/27/2019 9:13:50 PM : v - Linux(): isLinux --> False
8/27/2019 9:13:50 PM : v - Linux() finished
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: pluginVersion --> 2.0.42.0
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: homeseerAppPath --> D:\Program Files (x86)\HomeSeer HS3
8/27/2019 9:13:50 PM : v2.0.42.0 - Cleanup_Old_Help_Folder() started
8/27/2019 9:13:50 PM : v2.0.42.0 - Linux() started
8/27/2019 9:13:50 PM : v2.0.42.0 - Linux(): isLinux --> False
8/27/2019 9:13:50 PM : v2.0.42.0 - Linux() finished
8/27/2019 9:13:50 PM : v2.0.42.0 - Cleanup_Old_Help_Folder(): fullHelpFolder --> D:\Program Files (x86)\HomeSeer HS3\html\Help\BLSecurity
8/27/2019 9:13:50 PM : v2.0.42.0 - Cleanup_Old_Help_Folder(): folder DOES NOT exist, no action!
8/27/2019 9:13:50 PM : v2.0.42.0 - Cleanup_Old_Help_Folder() finished
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: supportForumUrl --> http://forums.homeseer.com/forumdisplay.php?f=1033
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: debugLevel --> true
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: databasePath --> D:\Program Files (x86)\HomeSeer HS3\Data\BLSecurity\BLSecurity.s3db
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: logToDatabase --> true
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: daysToKeepSecurityLogs --> 14
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: maintainDevicesSortOption --> name
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: enableHomeseerLogMessages --> true
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: helpFolder --> /BLHelp/
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: includeFloorForDevices --> false
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: securityMode --> Armed
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: delayBeforeEnteringArmedOrPerimeterMode --> 30
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: eventToTriggerForArmedAlert --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: eventToTriggerForPerimeterAlert --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: eventToTriggerForSleepAlert --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: eventToTriggerForPanicAlert --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: numberOfMinutesToResetAlertStatus --> 5
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: panelInterfaceRefreshRate --> 60
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: interfaceMaintainDevicesLinkEnabled --> true
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: interfaceOptionLinkEnabled --> true
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: interfaceReportsLinkEnabled --> true
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: warnSecurityDevicesInAlertWhenArming --> false
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armingTimeout --> 5
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: speakingEnabled --> true
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: speakDeviceLocations --> true
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: backgroundImageFile --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: countdownTimerDeviceCode --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: emailFromAddress --> alerts@blsecurity.com
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertWaveFile --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertWaveFileMessage --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertEmailAddresses --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertLightsToTurnOn --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertLightsAreInsteon --> false
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertPhoneNumbers --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertWaveFileRepeatSeconds --> 30
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertWaveFileDuration --> 5
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertPhoneResetAlertEnabled --> false
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: armedAlertPhoneResetAlertWaitTimeoutSeconds --> 8
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertWaveFile --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertWaveFileMessage --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertEmailAddresses --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertLightsToTurnOn --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertLightsAreInsteon --> false
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertPhoneNumbers --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertWaveFileRepeatSeconds --> 30
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertWaveFileDuration --> 5
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertPhoneResetAlertEnabled --> false
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: perimeterAlertPhoneResetAlertWaitTimeoutSeconds --> 8
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertWaveFile --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertWaveFileMessage --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertEmailAddresses --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertLightsToTurnOn --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertLightsAreInsteon --> false
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertPhoneNumbers --> 
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertWaveFileRepeatSeconds --> 30
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertWaveFileDuration --> 5
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertPhoneResetAlertEnabled --> false
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: sleepAlertPhoneResetAlertWaitTimeoutSeconds --> 8
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: remoteMappingPanic --> Panic
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: remoteMappingArmAwayMin --> Arm
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: remoteMappingArmAwayMax --> Arm
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: remoteMappingArmHomeMin --> Perimeter
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: remoteMappingArmHomeMax --> Perimeter
8/27/2019 9:13:50 PM : v2.0.42.0 - InitIO: remoteMappingDisarm --> Disarm
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices() started
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Exterior Home Security (code: Q2, address: CEE37CA2-007-Q2, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement Custom RGB 2 (code: Q42, address: E7817EE4-036-Q42, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement kW Hours 1 (code: Q43, address: E7817EE4-036-Q43, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement Watts 1 (code: Q44, address: E7817EE4-036-Q44, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement Volts 1 (code: Q45, address: E7817EE4-036-Q45, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement Amperes 1 (code: Q46, address: E7817EE4-036-Q46, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Living Room Leviton Switch (code: , address: E7817EE4-037, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Living Room Leviton Switch (code: , address: E7817EE4-038, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Living Room SWITCH - Power Plug TV (code: , address: E7817EE4-042, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Exterior Motion Sensor (code: Q3, address: CEE37CA2-007-Q3, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Living Room Switch - TV (DO NOT TURN OFF) (code: Q47, address: E7817EE4-042-Q47, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement SWITCH - Command Center (code: , address: E7817EE4-044, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement kW Hours (code: Q48, address: E7817EE4-044-Q48, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement Watts (code: Q49, address: E7817EE4-044-Q49, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement Volts - Command Center (code: Q50, address: E7817EE4-044-Q50, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement Amperes (code: Q51, address: E7817EE4-044-Q51, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Basement Switch - Command Center (DO NOT TURN OFF) (code: Q52, address: E7817EE4-044-Q52, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Exterior Temperature (code: Q4, address: CEE37CA2-007-Q4, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Exterior Luminance (code: Q5, address: CEE37CA2-007-Q5, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Living Room TV - kW Hours (code: Q53, address: E7817EE4-042-Q53, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Living Room TV - Watts (code: Q54, address: E7817EE4-042-Q54, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Living Room TV - Volts (code: Q55, address: E7817EE4-042-Q55, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Living Room TV - Amperes (code: Q56, address: E7817EE4-042-Q56, interface: Z-Wave)
8/27/2019 9:13:50 PM : v2.0.42.0 - Find_Create_Devices(): processing device --> Master Bathroom Switch (code: Q57, address: CEE37CA2-027-Q57, interface: Z-Wave)
8/27/2019 9:17:36 PM : v2.0.42.0 - **************** Debug Logging DISABLED at 8/27/2019 9:17:36 PM ****************

[Blade]

Make sure u have done this and make sure u are running the newest build

https://forums.homeseer.com/forum/3r...-debug-logging

[mr.Magoo]

Doh!

Thanks Blade, I was looking in every bls*.ini/cfg file I could find for that setting but didn't know / realize it was in a common file.

So I got things going (kind of), not sure what was wrong ended up wiping the install and re-installing it.

BUT - now I'm back to square one where I was a while back that the first trigger gets ignored.... (see separate thread)

https://forums.homeseer.com/forum/se...eset-to-normal

[Blade]

OK delete the BLSecurity-Detailed.log file int he HS3 root folder (if it exists)
Then turn on debug logging and capture the issue with the trigger being ignored
Once captured, turn off debug logging and attach the BLSecurity-Detailed.log zipped
Make sure to tell me what device you were testing with

[mr.Magoo]

PM Sent with the log and screenshot.

[Blade]

Try out 2.0.43 in the beta section of the HS3 updater