PLEG Next Gen UI

Aaron · June 3, 2016, 3:36pm

Hi Richard,
Will PLEG NG take the user’s current PLEG devices and ‘upgrade’ it automatically?

Also, any ETA on a Beta? I’m still on UI5 and not really looking forward to what seem to be still buggy UI7… but the new PLEG might make me change my mind.

thanks!

RichardTSchaefer · June 3, 2016, 4:28pm

I was planning on releasing at the same time as the next UI7 release.

There are currently some serious problems in the current UI7 for a few users (device state not being saved correctly).
It does not effect everyone, and it effects more than just PLEG. They promised a fix to a broken API to make saving data more reliable.

At this time the only thing that is not backwards compatible are comments … and I will likely fix that before I release.

Aaron · June 4, 2016, 2:24pm

Gotcha

Feature Request if I may…

In my old Homeseer days we had a plugin that would allow us to create a memory stack - allowing us to store & view state conditions and easily recall them.

Hoping you would implement something similar. This would be very helpful when trying to create code where you want to do something for a period of time, then revert back to the last state easily.

ACTIONs could look something like this…

AddToStack → Stack_SecurityConditions / Top … adds Condition’s name to top of stack
DeleteFromStack → Stack_SecurityConditions / Top … remove the last item on the stack, do not run it
DeleteFromStack → Stack_SecurityConditions / … remove item in stack, do not run it
ExecuteFromStack → Stack_SecurityConditions / Top … run the last item entered (top) in the stack, do not remove it
ExecuteDeleteFromStack → Stack_SecurityConditions / Top … run top item in the stack, then delete it from stack
ExecuteDeleteFromStack → Stack_SecurityConditions / … run item named , then delete it and all items above it in stack

INPUTs…
ReadFromStack → Stack_SecurityConditions / Top … read the name of the last (top) item in stack
ReadFromStack → Stack_SecurityConditions / All … read entire list of names in stack into array or delimited list, or maybe to even populate things like MultiSwitch or Selector plugins

erkme73 · June 10, 2016, 5:38pm

Over the last few days my edge has been restarting every few minutes. Vera alerts only announces a few per day but the logs are showing it way more frequently. I asked Veratech support to log in, and they just reported that PLEG is causing it. What do I do now? They suggested uninstalling it. But that’s like saying get rid of the engine in your car…

Richard, Im helpless with interpreting the logs. Whats a good, layman’s approach to this pickle? I did NOT disable the update features on the plug-ins.

RichardTSchaefer · June 10, 2016, 5:51pm

How man PLEG devices do you have ?
How many other NON ZWAVE plugin devices do you have ?

erkme73 · June 10, 2016, 6:48pm

Pleg: 3
Non-zwave: maybe 10. Do I count each sensor from my dsc alarm panel? If so, another 30…

RichardTSchaefer · June 10, 2016, 11:32pm

That seems fine … You can ignore Z-Wave and DSC attached sensor devices … these are relatively cheap in memory.
The real memory is associated with the Single Z-Wave interface (hidden) and the DSC plugin device.

Do you have triggers that are running every second … continuously ?
If not … I do not think you have a PLEG issue.

There have been problems reported when you have LOTS of Z-Wave actions on multiple conditions running simultaneously.
Seems to push the z-wave chip to hard.

erkme73 · June 11, 2016, 12:49am

I recently added a condition that checks for any pin (*) being entered on any of my three zwave deadbolts (Kwikset). The condition is simply frontdoorpin or backdoorpin or utilitydoorpin - which causes my alarm to disarm (single action). I had to check the ‘repeats’ box.

I also set up a power meter notification for an new Everspring device (powering my refrigerator) - if it turns off, or if load is above/below certain wattage - but these are notifications within the device (no PLEG) - though that does trigger the Vera Alerts.

Really at a loss here. If I were more familiar, comfortable, or confident with the backup/restore process, I’d start unwinding my most recent changes. But in the past, any time I tried that, I simply dug a deeper hole.

As for the loading of my PLEG devices - two have only two conditions each. The third - the one I use for everything else, has about 25 conditions. The actions triggered by any of them are almost all single actions, with a couple that have two or three.

I was hoping this was caused by the updates you were undertaking. If that were the case, I’d just sit back and wait for it to smooth out. But if it’s not, I don’t know what else to do.

ETA: I only have only have one scheduled trigger - and it’s once per hour. It’s been active for at least a year or two. All of my other triggers are state-changes, with two or three having the ‘repeats’ box checked.

On a side note, looking at the log, it is flooded with energy value updates from the various Aeon Labs micro controllers. I assume that’s normal (as I’ve always seen that level of volume). Would plugging a USB thumbdrive into the edge help with making more room? Sorry - I know this is beginning to move away from the thread purpose. I only posted here since Vera TS said it was PLEG…

erkme73 · June 11, 2016, 3:51pm

Richard,

Does the fact that the reboots are PRECISELY 6 minutes apart mean anything to you?

[code]
01 06/11/16 11:24:20.534 UserData::WriteUserData saved–before move File Size: 80574 save size 80574 <0x76da8520>
02 06/11/16 11:24:20.534 UserData::TempLogFileSystemFailure start 0 <0x76da8520>
02 06/11/16 11:24:20.582 UserData::TempLogFileSystemFailure 5912 res:1
-rw-r–r-- 1 root root 33 Dec 5 2015 /etc/cmh/HW_Key
-rw-r–r-- 1 root root 33 Mar 5 2015 /etc/cmh/HW_Key2

02 06/11/16 11:30:20.517 UserData::TempLogFileSystemFailure start 0 <0x76da8520>
02 06/11/16 11:30:20.544 UserData::TempLogFileSystemFailure 5912 res:1
-rw-r–r-- 1 root root 33 Dec 5 2015 /etc/cmh/HW_Key

02 06/11/16 11:36:20.440 UserData::TempLogFileSystemFailure start 0 <0x76da8520>
02 06/11/16 11:36:20.468 UserData::TempLogFileSystemFailure 5912 res:1
-rw-r–r-- 1 root root 33 Dec 5 2015 /etc/cmh/HW_Key[/code]

RichardTSchaefer · June 11, 2016, 5:44pm

The 6 minute interval is when Vera saves a copy of it’s internal state.
Sounds like something is corrupted … or does not have enough resources to save it’s state.

Please post your PLEG status report for your most recently changed PLEG.

erkme73 · June 11, 2016, 6:37pm

Every once and a while, the yellow reload log will show this:

-rw-r--r-- 1 root root 44 Feb 25 2015 check_internet.hosts df -h Filesystem Size Used Available Use% Mounted on rootfs 9.5M 4.0M 5.5M 42% / /dev/root 9.3M 9.3M 0 100% /rom tmpfs 61.9M 144.0K 61.7M 0% /tmp /dev/mtdblock6 9.5M 4.0M 5.5M 42% /overlay overlayfs:/overlay 9.5M 4.0M 5.5M 42% / tmpfs 512.0K 0 512.0K 0% /dev /dev/mtdblock10 64.8M 7.5M 57.3M 12% /storage /dev/mtdblock10 64.8M 7.5M 57.3M 12% /etc/cmh-firmware /dev/mtdblock10 64.8M 7.5M 57.3M 12% /etc/cmh-backup /dev/sda1 487.9M 424.0K 461.8M 0% /tmp/log/cmh /dev/mtdblock9 5.8M 5.8M 0 100% /mios

Mios is at 100%, as is the dev/root. If this isn’t due to Pleg, then I don’t want to muddy up this thread, and I’ll lean more heavily on VERA.

Registration
Installed: Sun Feb 16 2014. You have 1 license, which allows a total of 4 PLEG and/or PLTS plugins.
Triggers

Name Description State Last True Last False
BDOpen Whenever Back Door Sensor is opened whether is armed or disarmed false 2016-06-11 12:26:17.166 2016-06-11 12:26:27.156
BDPINEntered PIN Code #* is entered on Back door true 2016-06-02 22:40:23.346 0
BDUnlocked Back door is opened true 2016-06-11 06:49:13.777 2016-06-10 21:45:03.753
CAC_UnLocked Connor’s Door Lock is opened false 2016-06-09 15:37:57.741 2016-06-11 12:02:37.476
CACDoorOpen Whenever Connor’s Door is opened whether is armed or disarmed false 2016-06-11 10:08:57.708 2016-06-11 12:02:43.374
CACLaskoOn Whenever the Connor’s LASKO is turned on true 2016-06-11 12:02:42.405 2016-06-09 15:32:50.850
CACLightOn1 Whenever the Connor’s Light is turned on false 2016-06-11 10:08:58.100 2016-06-11 12:02:58.758
DRLightOn Whenever the Dining room light is turned on false 2016-06-11 12:27:50.989 2016-06-11 12:30:50.379
ECDoorOpen Whenever Eric’s Office Door is opened whether is armed or disarmed false 2016-06-11 10:07:45.252 2016-06-11 10:08:00.275
FDLockButtonPressed Front Door: Lock button is pressed true 2016-06-02 22:43:20.915 0
FDLSPinEntered PIN Code #4 is entered on Front Door false 2016-05-06 10:18:59.684 2016-06-02 22:43:28.445
FDOpen Whenever Front Door Sensor is opened whether is armed or disarmed false 2016-06-11 12:27:49.617 2016-06-11 12:41:23.180
FDPINEntered PIN Code #* is entered on Front Door true 2016-06-02 22:43:28.445 0
FDTCPinEntered PIN Code #2 is entered on Front Door false 2016-05-30 19:48:18.515 2016-06-02 22:43:28.445
FDUnlocked Front Door is opened true 2016-06-11 08:12:25.617 2016-06-10 13:46:41.399
GarageDoorOpen Whenever GD Sensor is opened whether is armed or disarmed false 2016-06-11 07:58:45.938 2016-06-11 08:02:35.713
GarageLightOn Whenever the Garage Lights is turned on false 2016-06-11 08:19:05.903 2016-06-11 08:29:32.798
GBedDoorOpen Whenever Guest Bedroom Door is opened whether is armed or disarmed true 2016-06-11 08:04:45.455 2016-06-10 17:25:03.108
GoodPINsEntered PIN Code #1,3,4,8 is entered on Connor’s Door Lock false 0 2016-06-08 13:05:07.779
IRBeamTriggered Whenever the IR Beam is turned on false 2016-06-11 12:41:16.462 2016-06-11 12:41:20.104
IsNight Day or Night indicates Night time. false 2016-06-10 20:26:40.180 2016-06-11 06:32:15.205
MACDoorOpen Whenever Michaela’s Door is opened whether is armed or disarmed false 2016-06-11 12:27:09.555 2016-06-11 12:27:31.108
MACRoomLightOn Whenever the Michaela’s Room Light is turned on false 2016-06-11 12:27:22.596 2016-06-11 12:27:33.966
MBRFrenchOpen Whenever Master Bedroom French Doors is armed and opened false 2016-06-11 06:53:40.999 2016-06-11 06:55:24.516
SmokeDetectorAlarming Whenever Smoke Detector is opened whether is armed or disarmed false 2016-06-10 22:01:46.340 2016-06-10 22:01:56.148
UDMSPinEntered PIN Code #3 is entered on Utility Door false 0 2016-06-11 08:01:10.921
UDOpen Whenever Utility Exterior Door is opened whether is armed or disarmed false 2016-06-11 08:19:03.097 2016-06-11 08:19:13.174
UDPINEntered PIN Code #* is entered on Utility Door true 2016-06-11 08:01:10.921 0
UDTCPinEntered PIN Code #2 is entered on Utility Door true 2016-06-11 08:01:10.921 2016-06-09 09:10:49.423
UDUnlocked Utility Door is opened true 2016-06-11 08:19:01.710 2016-06-11 08:03:20.025
URLightOn Whenever the Utility Room Light is turned on false 2016-06-11 11:13:44.224 2016-06-11 11:44:38.596
Schedules

Name On Type On Time On Days Random On Delay Off After Type Off Time Off Days Random Off Delay State Last On Last Off
AutoArmEvery1hrs Interval 01:00:00 None Interval 1:00 None false 2016-06-11 14:00:00.100 2016-06-11 14:01:00.100
Device Properties

Name Device Name Device Variable Value Last Change Previous Change
ArmedMode Partition 1 DetailedArmMode Ready 2016-06-11 08:19:09.539 2016-06-11 08:19:03.261
MACDoorOpen1 Michaela’s Door Tripped 0 2016-06-11 12:27:31.157 2016-06-11 12:27:09.600
Conditions

Name Repeat Expression State Last True Last False
MACLightOn No MACDoorOpen false 2016-06-11 12:27:09.557 2016-06-11 12:27:31.110
HallLightOn No CACDoorOpen OR MACDoorOpen or GBedDoorOpen true 2016-06-09 15:38:06.063 2016-06-09 15:33:37.046
FPLightOff Yes !IsNight true 2016-06-11 06:32:15.211 2016-06-10 20:26:40.189
FPLightDimOnGDClose No IsNight and !GarageDoorOpen false 2016-06-10 20:26:40.190 2016-06-11 06:32:15.220
FPLightDimAtNight No IsNight false 2016-06-10 20:26:40.201 2016-06-11 06:32:15.221
FPLightOn No (IsNight and GarageDoorOpen) or (IsNight and FDOpen) false 2016-06-09 20:26:17.246 2016-06-09 21:00:20.707
FPDimOnFDClose No IsNight and !FDOpen false 2016-06-10 20:26:40.219 2016-06-11 06:32:15.225
GarageLightOn1 No !GarageLightOn and (GarageDoorOpen and IsNight) or (!GarageDoorOpen and UDOpen) false 2016-06-11 08:19:03.105 2016-06-11 08:19:13.182
URLightOn1 No UDOpen and !URLightOn false 2016-06-11 08:19:03.114 2016-06-11 08:19:06.391
DRLightAutoOn No !DRLightOn and UDOpen and GarageDoorOpen and (GarageDoorOpen; UDOpen < 5:00)or FDopen false 2016-06-11 12:27:49.629 2016-06-11 12:41:23.194
AutoLockDoors No !GarageDoorOpen true 2016-06-11 08:02:35.748 2016-06-11 07:58:45.959
AutoArmAllDoorsLocked No !UDUnlocked and !FDUnlocked and !BDUnlocked and ArmedMode ne “Stay” false 2016-06-11 06:49:13.168 2016-06-11 06:49:13.792
ECLightOn No ECDoorOpen false 2016-06-11 10:07:45.266 2016-06-11 10:08:00.288
ECLightOff No !ECDoorOpen true 2016-06-11 10:08:00.289 2016-06-11 10:07:45.271
BPLightsOn No IsNight and BDOpen false 2016-06-10 21:44:59.207 2016-06-10 21:45:09.891
MAClightOff No !MACDoorOpen true 2016-06-11 12:27:31.123 2016-06-11 12:27:09.573
CACLightOn No CACDoorOpen and !CACLaskoOn false 2016-06-11 10:08:57.723 2016-06-11 12:02:42.420
CACLightOff No !CACDoorOpen true 2016-06-11 12:02:43.390 2016-06-11 10:08:57.727
MACLightOn10pct No MBRFrenchOpen and !MACRoomLightOn false 2016-06-11 06:53:41.028 2016-06-11 06:55:14.151
MACLightOff10pct No !MACDoorOpen and !MBRFrenchOpen true 2016-06-11 12:27:31.129 2016-06-11 12:27:09.576
AutoArmHourlyAtNight Yes IsNight and (ArmedMode ne “Stay”) and AutoArmEvery1hrs false 2016-06-11 00:00:00.999 2016-06-11 14:01:00.118
GBLightOn No GBedDoorOpen true 2016-06-11 08:04:45.482 2016-06-10 17:25:03.131
GBLightOff No !GBedDoorOpen false 2016-06-10 17:25:03.132 2016-06-11 08:04:45.496
IRBeamTripped No IRBeamTriggered false 2016-06-11 12:41:16.491 2016-06-11 12:41:20.122
CACLaskoAutoOn No !CAC_UnLocked true 2016-06-11 12:02:37.496 2016-06-09 15:37:57.774
CACLaskoAutoOFF No CAC_UnLocked false 2016-06-09 15:37:57.775 2016-06-11 12:02:37.500
GBedLightAutoOn No GBedDoorOpen true 2016-06-11 08:04:45.497 2016-06-10 17:25:03.137
SmokeDetectorAlarmingEmail No SmokeDetectorAlarming false 2016-06-10 22:01:46.381 2016-06-10 22:01:56.294
SmokeDetectorNotAlarmingEmail No !SmokeDetectorAlarming true 2016-06-10 22:01:56.295 2016-06-10 22:01:46.388
GBedLightAutoOff No !GBedDoorOpen false 2016-06-10 17:25:03.138 2016-06-11 08:04:45.505
disarmPin Yes BDPINEntered or FDPINEntered or UDPINEntered true 2016-06-11 08:01:10.974 2016-06-02 22:31:21.798
Actions

Actions for Condition: AutoArmAllDoorsLocked

Device Actions:

Immediate

Device Action Arguments
Partition 1 RequestArmMode State=Stay PINCode=8169
Actions for Condition: AutoArmHourlyAtNight

Device Actions:

Immediate

Device Action Arguments
Partition 1 RequestArmMode State=Stay PINCode=8169
Delay 15

Device Action Arguments
Back door SetTarget newTargetValue=1
Delay 30

Device Action Arguments
Front Door SetTarget newTargetValue=1
Delay 45

Device Action Arguments
Utility Door SetTarget newTargetValue=1
Actions for Condition: AutoLockDoors

Device Actions:

Delay 15

Device Action Arguments
Front Door SetTarget newTargetValue=1
Delay 30

Device Action Arguments
Utility Door SetTarget newTargetValue=1
Delay 45

Device Action Arguments
Partition 1 RequestArmMode State=Stay PINCode=8169
Back door SetTarget newTargetValue=1
Actions for Condition: BPLightsOn

Device Actions:

Immediate

Device Action Arguments
Back Porch Lights SetTarget newTargetValue=1
Actions for Condition: CACLaskoAutoOFF

Device Actions:

Immediate

Device Action Arguments
Connor’s LASKO SetLoadLevelTarget newLoadlevelTarget=0
CAC Blacklight SetTarget newTargetValue=0
Actions for Condition: CACLaskoAutoOn

Device Actions:

Immediate

Device Action Arguments
Connor’s LASKO SetLoadLevelTarget newLoadlevelTarget=100
CAC Blacklight SetTarget newTargetValue=1
Actions for Condition: CACLightOff

Device Actions:

Immediate

Device Action Arguments
Connor’s Light SetLoadLevelTarget newLoadlevelTarget=0
Actions for Condition: CACLightOn

Device Actions:

Immediate

Device Action Arguments
Connor’s Light SetLoadLevelTarget newLoadlevelTarget=100
Actions for Condition: disarmPin

Device Actions:

Immediate

Device Action Arguments
Partition 1 RequestArmMode State=Disarmed PINCode=2476
Actions for Condition: DRLightAutoOn

Device Actions:

Immediate

Device Action Arguments
Dining room light SetTarget newTargetValue=1
Delay 03:00

Device Action Arguments
Dining room light SetTarget newTargetValue=0
Actions for Condition: ECLightOff

Device Actions:

Immediate

Device Action Arguments
EC Office Fan SetTarget newTargetValue=0
EC Office Light SetLoadLevelTarget newLoadlevelTarget=0
Actions for Condition: ECLightOn

Device Actions:

Immediate

Device Action Arguments
EC Office Light SetLoadLevelTarget newLoadlevelTarget=100
Actions for Condition: FPDimOnFDClose

Device Actions:

Immediate

Device Action Arguments
Front Porch Lights SetLoadLevelTarget newLoadlevelTarget=10
Actions for Condition: FPLightDimAtNight

Device Actions:

Immediate

Device Action Arguments
Front Porch Lights SetLoadLevelTarget newLoadlevelTarget=10
Actions for Condition: FPLightDimOnGDClose

Device Actions:

Immediate

Device Action Arguments
Front Porch Lights SetLoadLevelTarget newLoadlevelTarget=10
Actions for Condition: FPLightOff

Device Actions:

Immediate

Device Action Arguments
Front Porch Lights SetLoadLevelTarget newLoadlevelTarget=0
Actions for Condition: FPLightOn

Device Actions:

Immediate

Device Action Arguments
Front Porch Lights SetLoadLevelTarget newLoadlevelTarget=100
Actions for Condition: GarageLightOn1

Device Actions:

Immediate

Device Action Arguments
Garage Lights SetTarget newTargetValue=1
Actions for Condition: GBedLightAutoOff

Device Actions:

Immediate

Device Action Arguments
Guest Bedroom Light SetLoadLevelTarget newLoadlevelTarget=0
Guest Bedroom Fan SetTarget newTargetValue=0
Actions for Condition: GBedLightAutoOn

Device Actions:

Immediate

Device Action Arguments
Guest Bedroom Light SetLoadLevelTarget newLoadlevelTarget=100
Actions for Condition: HallLightOn

Device Actions:

Immediate

Device Action Arguments
Hallway Light SetTarget newTargetValue=1
Actions for Condition: IRBeamTripped

LUA:

luup.inet.wget(“http://192.168.1.81/admin?camera=Porch44&trigger&user=”,10)
luup.call_action(“urn:upnp-org:serviceId:RGBController1”, “StartAnimationProgram”, {programName = “LAPD”}, 178)
luup.call_action(“urn:upnp-org:serviceId:RGBController1”, “StartAnimationProgram”, {programName = “LAPD”}, 179)
Device Actions:

Delay 45

Device Action Arguments
Controller FR 178/5 StopAnimationProgram
Controller KIT 179/7 StopAnimationProgram
Actions for Condition: MAClightOff

Device Actions:

Immediate

Device Action Arguments
Michaela’s Room Light SetLoadLevelTarget newLoadlevelTarget=12
Michaela Floor Light SetLoadLevelTarget newLoadlevelTarget=12
Actions for Condition: MACLightOff10pct

Device Actions:

Immediate

Device Action Arguments
Michaela’s Room Light SetLoadLevelTarget newLoadlevelTarget=0
Michaela Floor Light SetLoadLevelTarget newLoadlevelTarget=0
Actions for Condition: MACLightOn

Device Actions:

Immediate

Device Action Arguments
Michaela Floor Light SetLoadLevelTarget newLoadlevelTarget=100
Michaela’s Room Light SetLoadLevelTarget newLoadlevelTarget=100
Actions for Condition: MACLightOn10pct

Device Actions:

Immediate

Device Action Arguments
Michaela’s Room Light SetLoadLevelTarget newLoadlevelTarget=10
Michaela Floor Light SetLoadLevelTarget newLoadlevelTarget=10
Actions for Condition: SmokeDetectorAlarmingEmail

Device Actions:

Immediate

Device Action Arguments
VeraAlerts SendAlert Message=SMOKE ALARMS!! Recipients= HouseModeMask=
Actions for Condition: SmokeDetectorNotAlarmingEmail

Device Actions:

Immediate

Device Action Argument
Email Notification SendEmail Subject=Smoke is all clear Recipient_eMail=REDACTED@email.com Recipient_Name=Eric Message=
Actions for Condition: URLightOn1

Device Actions:

Immediate

Device Action Arguments
Utility Room Light SetTarget newTargetValue=1
Delay 05:00

Device Action Arguments
Utility Room Light SetTarget newTargetValue=0

RichardTSchaefer · June 11, 2016, 11:31pm

It’s preferable to post status reports as PDF attachments.

/mios is a readonly partition … it’s where the firm ware resides … it is always 100%

The only potential I see is your LUA … If you get multiple trips quickly … the wget can be blocking and potentially trip a Vera deadlock.

erkme73 · June 12, 2016, 12:05am

The Lua code - specifically the wget is to trigger my BlueIris PC to record. It’s a single (IR beam) trigger, and happens only if someone is at the door. When it fires, my RGB bulbs blink red/blue and BI sends a push notification to my phone. I have not had any random firings, and the restarts are happening regardless of IR beam being tripped or not.

I think the precise 6 min restart is telling us it’s probably not PLEG, right? I don’t want to hijack this thread with standard tech support issues - especially if it’s not even related to the next gen updates.

daemondazz · June 14, 2016, 2:20pm

Hey Richard,

Using the NewAndOld version I downloaded about 20 minutes ago, I am having trouble editing actions. The old editor gives me “Error executing function pleg_Actions(): Cannot set property ‘lua’ of undefined” and the new editor does not allow me to add an interval or devices to the immediate interval.

RichardTSchaefer · June 14, 2016, 3:09pm

This is setup for UI7 users …

daemondazz · June 14, 2016, 3:26pm

Yes, you state that in the first post?

Vera Edge running 1.7.1707

daemondazz · June 15, 2016, 1:22am

Hey Richard,

A little more information from some more testing.

First up, is 1.7.1707 ok? My Edge is saying that it’s up to date (and it did download and update when I set it up a few days ago). I have seen in another thread references to 1.7.1754, but I’m unsure on the support matrix of the various devices.

As for my testing, what I’ve found is that I can’t edit the actions for conditions that existed but had an empty (but existing) action before installing the beta version. When I choose a device in the drop-down list it does not display the editor for the action.

If I remove the empty action and then re-create it, then I can add devices ok and I can use the non “advanced” editor to set the dim level and on/off. Clicking on the advanced checkbox (so I can set SetColor on my RGB bulbs) hides the simple editor but then does not show anything else. For now I’m working around by using LUA to set the colour and then the simple editor to set the level.

erkme73 · June 15, 2016, 1:23pm

Is this at all related to PLEG upgrade?

02 06/15/16 9:18:16.034 OL: (0xa86778) (>3205962) Variable Device_LuaUPnP.cpp l:407 time: 9:17:50a (26 s) thread: 0x72792520 Rel: Y Got: Y <0x7755f320> 02 06/15/16 9:18:16.035 finished check for exceptions <0x7755f320> 02 06/15/16 9:18:16.035 OL: (0x10b980c) (>3205963) Lua LuaInterface.cpp l:2120 time: 9:17:50a (26 s) thread: 0x72792520 Rel: N Got: Y <0x7755f320> 02 06/15/16 9:18:16.035 finished check for exceptions <0x7755f320> 02 06/15/16 9:18:16.036 OL: (0xa86778) (>3206022) Variable Device_Basic.cpp l:520 time: 9:17:50a (26 s) thread: 0x72792520 Rel: Y Got: Y <0x7755f320> 02 06/15/16 9:18:16.036 finished check for exceptions <0x7755f320> 02 06/15/16 9:18:16.037 OL: (0x10143b4) (>3206024) Lua LuaInterface.cpp l:2315 time: 9:17:50a (26 s) thread: 0x72792520 Rel: N Got: N <0x7755f320> 02 06/15/16 9:18:16.037 finished check for exceptions <0x7755f320> 02 06/15/16 9:18:16.037 OL: (0xf5a504) (>3206651) ThreadedClass ThreadedClass.cpp l:49 time: 9:18:15a (1 s) thread: 0x76ff6520 Rel: Y Got: Y <0x7755f320> 01 06/15/16 9:18:16.038 Deadlock problem. going to reload and quit <0x7755f320> 03 06/15/16 9:18:16.038 JobHandler_LuaUPnP::Reload: deadlock Critical 1 m_bCriticalOnly 0 dirty data 1 <0x7755f320> 01 06/15/16 9:18:16.635 UserData::WriteUserData saved--before move File Size: 79527 save size 79527 <0x7755f320> 02 06/15/16 9:18:16.635 UserData::TempLogFileSystemFailure start 0 <0x7755f320>

Getting tons of these today.

RichardTSchaefer · June 15, 2016, 1:31pm

That is caused by something that is taking to long to run …
Should not be anything in PLEG that cause that, that’s not to say that your specific PLEG may not have a problem.
This can be caused by do web calls from LUA … which you can do in PLEG
It can also be caused if you are trying to send Z-Wave commands much faster than then the Z-Wave chip can handle them, which is possible if you have Z-Wave problems with the devices you are trying to send commands to.

erkme73 · June 15, 2016, 1:36pm

Is there no way to drill down in the logs somehow to see exactly which device or action is causing the deadlock? You’d think there’s got to be a better diagnostic process than “it could be any one of your devices not working right”. Not faulting you, and I appreciate your guidance. I’m just frustrated over the seemingly generic/vague logs. Reminds me of the Microsoft “unknown error” dialog box that pops up. So generic it’s useless…