And looks like the only 570s coming back are the ones I pasted in before, which are the partition labels not the zone labels.
#DSC DLS PANEL COULD NOT BE IDENTIFIED CODE#
I took a look at the code and the log again after altering the zone config and restarting. It’s a Vera3 running 1.5.622 and the current (.38) on the DSC module. Although I agree that the delete device shouldn’t leave you in an inoperable state. There haven’t been any further restart loops. There are a significant # of differences between the versions. You don’t mention the version of your Vera HW/SW, so you’ll want to post that to get further advice. Additionally, their “delete device” should never leave you in a bad state, so that sounds like another bug in their stack that needs to be addressed. That said, if you’re seeing SEGV based crashes, for any reason, it’s best to get those sorted out first with the MCV Team. The debug/diag log for Zone labels is of the form: DSCAlarmPanel: debug setPanelLabel: Zone Label : The example posted above are Command labels, which the Plugin currently ignores, along with a bunch of other types. This worked fine and I was able to re-install the plugin, with the exception of the label broadcasts.Ī DSC Label Broadcast emits a lot of Labels and not all of them are Zone labels. Instead of a complete restore, I pulled this file off and wrote a short program to remove any entries referencing the DSC plugin and replaced it. After some amount forum searching, file modification date examining and logfile reading, I determined that there were references to the now non-existant DSC plugin was still referenced in the user_ file. Logging in I discovered that LuaUpnp was crashing with a segfault. *full disclosure – removing the plugin resulted in the UI not returning. I’m thinking this isn’t really anything with the plug-in, but something on the DSC side preventing the labels from arriving in the IT100, but I thought someone here might have some suggestions as to what to try.
Looking at the (verbose/advanced) log I can see the 570s returning from the IT100 (though it doesn’t explicitly log sending the 002?) :ĥ0Đ6/06/13 10:12:20.234 luup_log:168: DSCAlarmPanel: debug processIncoming:: Command=empty, Data=‘empty’, Checksum=empty ĥ0Đ6/06/13 10:12:20.304 luup_log:168: DSCAlarmPanel: debug processIncoming:: Command=570, Data='150Command O/P 3 ', Checksum=92 ĥ0Đ6/06/13 10:12:20.304 luup_log:168: DSCAlarmPanel: debug Panel::Broadcast Labels (150Command O/P 3 ) ĥ0Đ6/06/13 10:12:20.305 luup_log:168: DSCAlarmPanel: debug setPanelLabel Not set: Command Output Label 150:Command O/P 3 ĥ0Đ6/06/13 10:12:20.394 luup_log:168: DSCAlarmPanel: debug processIncoming:: Command=570, Data='151Command O/P 4 ', Checksum=94 ĥ0Đ6/06/13 10:12:20.394 luup_log:168: DSCAlarmPanel: debug Panel::Broadcast Labels (151Command O/P 4 ) ĥ0Đ6/06/13 10:12:20.395 luup_log:168: DSCAlarmPanel: debug setPanelLabel Not set: Command Output Label 151:Command O/P 4 Īnd they all say that the Label is not set…However, I’ve re-programmed the panel from DLS multiple times, and even changed the labels, which arrive okay at the keypad. I’ve reprogrammed the DSC (1832) with the DLS app to no avail. Now I’m seeing the zone transitions, I can arm/disarm, set the time, etc. So I removed the plug-in and reinstalled it.*
#DSC DLS PANEL COULD NOT BE IDENTIFIED SERIAL#
I restarted the VERA, the panel, and double checked the serial connection – but no luck. But I relocated the vera in the fall and it had been completely reliable until a few weeks ago when it simply quit reporting zone transitions. I had some initial problems with periodic ‘lua failures’ when using it thoguh the wizNet. So I’d had the VERA+DSC via IT100 setup going for about 9 months.
0 kommentar(er)
