Richard,
there is still a bug - I see this, at least, once a day. Not always in the morning as I was before. Ctrl-F5 and Reloads does not fix. Vera Log attached
happened again no more than 4 hours after a reboot, maybe less. this is the 3rd time today, that I know of. The only difference is I moved from 6.6 to 6.7 last night. I have not changed any of the PLEGs or other devices/scenes/etc. No other apps have changed, no new apps.
Are modifing some LUA structures in the Vera Startup LUA ?
I see variable_set to device 229 before device 229 is initialized. (To Triggers, ConditionMap, Actions, ObjectStatusMap)
[quote=“RichardTSchaefer, post:3, topic:180777”]Are modifing some LUA structures in the Vera Startup LUA ?
I see variable_set to device 229 before device 229 is initialized. (To Triggers, ConditionMap, Actions, ObjectStatusMap)[/quote]
Device 229 is new as of a week ago, it is a tilt sensor. I added it and done absolutely nothing to it except changed the Name. I have not even changed the room. It is not used at all, not in ANY PLEG or native vera Scenes. So, nope I don’t modify anything in LUA… I would not even know how to.
See near the top of your previously posted log in this thread:
Device_Variable::m_szValue_set device: 229 service: urn:rts-services-com:serviceId:ProgramLogicC variable: e[35;1mTriggerse[0m was: ....
I though 229 was your security PLEG.
Wholly smokes Batman… I found 62 references to it in the log over just a few day span. I SHOULD NOT be a PLEG device - maybe this is wreaking havoc? It is ALSO showing as…
Device_Variable::m_szValue_set device: 229 service: urn:micasaverde-com:serviceId:HaDevice1
Device_Variable::m_szValue_set device: 229 service: urn:micasaverde-com:serviceId:ZWaveDevice1
Device_Variable::m_szValue_set device: 229 service: urn:rts-services-com:serviceId:ProgramLogicEG
… this is showing items like ‘nightPatio’ which are from an OLD PLEG device that has not existed since before, when I deleted ALL my PLEGs, uninstalled 5.9 and installed and licensed 6.5.
Now I only have 3 PLEG devices, 226 / 227 / 228.
Suggestions on how to kill 229 PLEG intruder?
I have a feeling you have run into some Vera related problems … because you are reusing deviceIDs.
When you create a new device … it creates a device with a deviceID of +1 higher than the current highest device.
If you go through a create 1, delete 1, create 2, delete 2, create 3 sequence without any other device creates in between, all 3 creates will have the same device ID.
If you do:
create 1, create 2, delete 1, create 3, delete 2 .
Then each create will have a different device ID.
i.e. Create the new devices before you delete the old ones … This is only important if you are deleting the highest numbered devices in Vera.
[hr]
I noticed this early on when working with Vera.
As a result I rarely delete a device … I have found no real benefits to doing so.
The only devices I delete are ones I use for testing … and only when I need to test the logic for creating a new device.
When I do this I always create a new device first … then delete the old one.
But I reused PLEGs all the time for new purposes … just delete inputs and conditions and retarget the test PLEG.
Good suggestion. I kinda figured it reused the Device IDs… now I need to figure out how to clean out the garbage from the old devices. Any suggestion on a safe way to do that?
just create new devices.
Then delete the old ones.
I think Vera will figure it out after this.
This is now occurring to one of my PLEGS.
I have no control over it, powering down Vera has no effect and I’m at a loss what to do next except to delete it and start again.
Is there another way to get it going?
Turn on debug to the the VERA log file for that PLEG (Use the LOG command).
Restart Vera and post the log.
Where you changing the configuration when it happened ?
Do a PLEG Backup for that device as well … Post the backup … You can find it in the App-> Develop Apps → LUUP files.
I can probable fix the backup file … and you can restore it be on your way.
Richard, I didn’t change anything in the PLEG, I was checking it’s status, on closing it failed to start and is stuck in a loop.
It’s a PLEG I use for environment, with winter coming, it’s time to blow out the cobwebs in the ducted heating.
I’m using a Remetec Thrmostat, it’s pretty well self contained so not having Zwave access won’t stop it.
Deleting it won’t upset me either .
I’m not sure what you mean by “Post the backup … You can find it in the App-> Develop Apps → LUUP files.”
Do you meant the device file for the Remotec?
The latest version of PLEG has support to backup and restore an individual PLEG.
So if something gets corrupted you can restore it (assuming you backed it up in the first place).
Another potential benefit, I was referring to, If you do a backup while it’s corrupted … It should capture the corrupted state.
I might be able to correct the backup file … so you can import it and continue.
Might be more than a corrupted file, when I try to backup I get a warning.
Command failed:ERROR: Device not ready
& unable to proceed any further.
At least the heater works…so if you want to find the culprit, I’m happy to continue with your debugging on a step by step basis.