DSC & IT-100 Woes

Hello,
It’s been a very long time since I posted and I’m throwing in the towel hoping for some help. I had my DSC system working with my IT-100 (Serial 2 USB Converter) like a champ for about a year or so. I needed to configure a Cisco firewall on a small project so I borrowed the cable from my working IT-100 and DSC connection for this work. Upon replacement back into services with Vera, I’m no longer able to control my DSC alarm panel.

I at first thought it was strange and uninstalled it all, deleted the devices, etc. I added the plugin back and it sees my partition, doors, etc. The problem is that it doesn’t sense if anything is tripped, I can’t arm it, and it’s not really in communication with it. I even tried replacing the converter with no luck as I thought maybe something went bad in the USB to Serial converter.

I manually uploaded the plugins files as if I was on UI4 and maybe they were corrupt on the unit. Same results

Of course I made sure that I had disarm in the remote “EnableRemoteArm” section. Using my pin to update the time doesn’t work either and all of this worked before

I just double checked my wiring and the IT-100 is blinking every .5 seconds which according to the manual means everything is fine with that connection. (http://tinymicros.com/mediawiki/images/2/23/DSC_IT-100_Installation_Manual.pdf)

I even plugged in the USB connection into my laptop, fired up Putty, and tuned into COM3 and it has a connection. I attached a screenshot to show you how it detects everything when I add in the module. It’s connected right but I’ve got to be missing something, somewhere. :frowning:

I’m at a loss on what to do next other than a factory reset on my Vera3. I’ve been messing with this for a few months and am so frustrated. Can you help? Any ideas?

-Paul

Do you have the it linked to the correct Serial port in serial port area in Apps /develop apps? correct baud rate etc?

Also you mentioned that you installed this per UI4 instructions, but you have a Vera 3 (only ever UI5). You should be installing this really from the app store.

I would also recommend posting this in the DSC sub forum, or getting a mod to move it.

Thanks for moving this to the right forum. I was stating that I had even tried the UI4 way after trying via the UI5 directions over and over with no result.

I assume that I have the right serial port as that information was propagated automatically. How can I double check it? I have the baud rate set at 9600 per the instructions. It all worked great before which is why it’s so confusing. Thanks again.

I would start by deleting the plugin and then installing it from the App Store.

After you’ve done that then make sure you have the plugin configured to use the IT100 within the plugin.

For the serial port screen, perhaps post a screen shot if you can?

Hi, I did it through the app store at least 20 times added, and removed trying to fix it. I did it again and attached some screenshots. It won’t let me add them all so I’ll reply again with the last one.

Here is the last screenshot. It auto added all the zones, etc but I can tell they are not right. For example zone #2 is for the window in my office but it’s showing as a door. I have 3 doors too. If I put in my pin to try and set the time, nothing happens, and I can’t set the alarm, etc. It can’t tell when something is open either. Does any of this help?

Thanks,

Can you get a screen grab the same as the attached?

whoops! I thought I attached it. I did take it. My bad. :frowning:

Ok so that looks OK.

For the Door and Window Zones you will have to set those yourself. The plugin sets zones 1-6 up regardless of what you have, so you will need to define those along with how many partitions you have. Are you using wired or wireless sensors, and what are your actual zone numbers?

Regardless, even if the zones are not configured correctly, you should be able to set the time at least, or maybe arm or disarm unless you you have some weird configuration with partitions.

What do you have between the IT100 and the USB to serial? Is it possible this cable went bad?

Other than the cable, we would likely need to see the output of the LuaUPnP.log to perhaps help more.

I went around the house and documented all my zones as shown below.

1-front door
2-office windows
3-front windows
4-back door
5-garage door
6-living room windows

I’ve also attached a zip of some pictures of my setup including the cables. As such, I also swapped and put in my newer GearHead black cable. Additionally, I swapped it with the USB drive for logging so we can see if it actually changed the serial information. A screenshot of that is also included. I’m noticing that both cables, in different ports are showing the same path of /dev/ttyUSB0. Shouldn’t that change depending on the port? It auto put in the name of pl2303 and changed the Device number.

Do you want the whole log or a subset via grep or something?

I just went through, updated the zones to be correct in naming for my house, updated them in the plugin with the right numbers and zones by type. Made sure it was using the new serial device, etc. Same results. No errors, no nothing.

Hi,
I tried to sync time and arm the unit with no response. I pasted in the logs from right when i did it. Maybe this helps?

10 01/06/14 17:45:11.627 mg_callback from IP:127.0.0.1:59427 /port_3480/data_request start id: 75 <0x2ed79680>
12 01/06/14 17:45:11.627 luvd_get_info_data_request starting /data_request?id=lu_action&output_format=json&DeviceNum=97&serviceId=urn:micasaverde-com:serviceId:DSCAlarmPanel1&action=SyncTime&PINCode=1117&rand=0.18355487496592104 pMem 0xdd6000/14508032 diff: 7323648 <0x2ed79680>
10 01/06/14 17:45:11.628 JobHandler_LuaUPnP::HandleRequest id lu_action request pMem 0xdd6000/14508032 diff: 7323648 <0x2ed79680>
10 01/06/14 17:45:11.629 sbrk JobHandler_LuaUPnP::HandleActionRequest from IP:0.0.0.0 pMem 0xdd6000/14508032 diff: 7323648 <0x2ed79680>
08 01/06/14 17:45:11.629 JobHandler_LuaUPnP::HandleActionRequest device: 97 service: urn:micasaverde-com:serviceId:DSCAlarmPanel1 action: SyncTime <0x2ed79680>
08 01/06/14 17:45:11.629 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=97 <0x2ed79680>
08 01/06/14 17:45:11.629 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:DSCAlarmPanel1 <0x2ed79680>
08 01/06/14 17:45:11.630 JobHandler_LuaUPnP::HandleActionRequest argument action=SyncTime <0x2ed79680>
08 01/06/14 17:45:11.630 JobHandler_LuaUPnP::HandleActionRequest argument PINCode=1117 <0x2ed79680>
08 01/06/14 17:45:11.630 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.18355487496592104 <0x2ed79680>
50 01/06/14 17:45:11.632 luup_log:97: DSCAlarmPanel: debug Action::SetTime:1745010614 <0x2ed79680>
25 01/06/14 17:45:11.632 luup_io_write 97 size: 15 <0x2ed79680>
51 01/06/14 17:45:11.633 0x30 0x31 0x30 0x31 0x37 0x34 0x35 0x30 0x31 0x30 0x36 0x31 0x34 0x38 0x45 0xd 0xa (01017450106148E\r\n) <0x2ed79680>
25 01/06/14 17:45:11.633 luup_io_write 97 result: 1 <0x2ed79680>
50 01/06/14 17:45:11.634 luup_log:97: DSCAlarmPanel: debug sent (010,1745010614), setup callback (function: 0xb640e0) <0x2ed79680>
10 01/06/14 17:45:11.635 luvd_get_info_data_request creating file buffer /data_request?id=lu_action&output_format=json&DeviceNum=97&serviceId=urn:micasaverde-com:serviceId:DSCAlarmPanel1&action=SyncTime&PINCode=1117&rand=0.18355487496592104 pMem 0xdd6000/14508032 diff: 7323648 <0x2ed79680>
10 01/06/14 17:45:11.637 luvd_get_info_data_request done /data_request?id=lu_action&output_format=json&DeviceNum=97&serviceId=urn:micasaverde-com:serviceId:DSCAlarmPanel1&action=SyncTime&PINCode=1117&rand=0.18355487496592104 ret 0 size 40 pMem 0xdd6000/14508032 diff: 7323648 took 0 info (nil) <0x2ed79680>
10 01/06/14 17:45:11.637 mg_callback /data_request stop id: 75 <0x2ed79680>
42 01/06/14 17:45:14.033 0x1 0x5 0x0 0x47 0x1 0x1 0xbd (###G###) <0x2c35f680>
24 01/06/14 17:45:14.034 ZWaveSerial::ReceiveData got frame type 0x0 command id 0x47 m_iFrameID 230 gwf_drr <0x2c35f680>
41 01/06/14 17:45:14.034 ACK: 0x6 (#) <0x2c35f680>
24 01/06/14 17:45:14.054 ZWaveSerial::ReceivedFrame holding the srm mutex for m_iFrameID 230 gwf_drr <0x2c35f680>
24 01/06/14 17:45:14.055 ZWaveSerial::ReceivedFrame receive data not waiting for frame: 0x9576b0/gnd_arr ack 3 expect 1 good 0 type 0 cmd:47/46 gd: 1 m_pRes 0x925468 m_pReq (nil) resp REQUEST pzw->m_c 0x47 m_iFrameID 230 gwf_drr <0x2c35f680>
10 01/06/14 17:45:14.055 AlarmManager::AddRelativeAlarm current time 1389051914 delay 0 type 52 <0x2c35f680>
10 01/06/14 17:45:14.055 AlarmManager::AddAbsoluteAlarm alarm 0x6db2d0 entry 0xb45660 id 251 type 52 param=0x853908 entry->when: 1389051914 time: 1389051914 bCancelFirst 0=0 <0x2c35f680>
31 01/06/14 17:45:14.056 AlarmManager::Run 0x6db2d0 notified of a change entry 0x6fc120 id 2 deleted 0 <0x2bd5f680>
31 01/06/14 17:45:14.056 AlarmManager::Run 0x6db2d0 notified of a change entry 0x95c940 id 239 deleted 0 <0x2bb5f680>
31 01/06/14 17:45:14.057 AlarmManager::Run callback for alarm 0x6db2d0 entry 0xb45660 type 52 id 251 param=0x853908 entry->when: 1389051914 time: 1389051914 tnum: 1 slow 0 tardy 0 <0x2bb5f680>
24 01/06/14 17:45:14.057 ZWaveJobHandler::DoReceivedFrame m_iFrameID 230 gwf_drr node 0 command 0x47 data <0x2bb5f680>
24 01/06/14 17:45:14.057 ZWaveJobHandler::DoReceivedFrame m_iFrameID 230 collission with job#28 :getnodedetails 4 dev:7 (0x87f208) P:38 S:7 node 4 <0x2bb5f680>
10 01/06/14 17:45:14.058 AlarmManager::AddRelativeAlarm current time 1389051914 delay 1 type 52 <0x2bb5f680>
10 01/06/14 17:45:14.058 AlarmManager::AddAbsoluteAlarm alarm 0x6db2d0 entry 0xab0020 id 252 type 52 param=0x853908 entry->when: 1389051915 time: 1389051914 bCancelFirst 0=0 <0x2bb5f680>
31 01/06/14 17:45:14.058 AlarmManager::Run finish callback for alarm 0x6db2d0 entry 0xb45660 type 52 id 251 param=0x853908 entry->when: 1389051914 time: 1389051914 tnum: 1 slow 0 duration 0 <0x2bb5f680>
31 01/06/14 17:45:14.059 AlarmManager::Run 0x6db2d0 notified of a change entry 0x6fc120 id 2 deleted 0 <0x2bd5f680>
31 01/06/14 17:45:15.004 AlarmManager::Run callback for alarm 0x6db2d0 entry 0xab0020 type 52 id 252 param=0x853908 entry->when: 1389051915 time: 1389051915 tnum: 1 slow 0 tardy 0 <0x2bb5f680>
24 01/06/14 17:45:15.005 ZWaveJobHandler::DoReceivedFrame m_iFrameID 230 gwf_drr node 0 command 0x47 data <0x2bb5f680>
24 01/06/14 17:45:15.005 ZWaveJobHandler::DoReceivedFrame m_iFrameID 230 collission with job#28 :getnodedetails 4 dev:7 (0x87f208) P:38 S:7 node 4 <0x2bb5f680>
10 01/06/14 17:45:15.006 AlarmManager::AddRelativeAlarm current time 1389051915 delay 1 type 52 <0x2bb5f680>
10 01/06/14 17:45:15.006 AlarmManager::AddAbsoluteAlarm alarm 0x6db2d0 entry 0xb45660 id 253 type 52 param=0x853908 entry->when: 1389051916 time: 1389051915 bCancelFirst 0=0 <0x2bb5f680>
31 01/06/14 17:45:15.006 AlarmManager::Run finish callback for alarm 0x6db2d0 entry 0xab0020 type 52 id 252 param=0x853908 entry->when: 1389051915 time: 1389051915 tnum: 1 slow 0 duration 0 <0x2bb5f680>
31 01/06/14 17:45:15.007 AlarmManager::Run 0x6db2d0 notified of a change entry 0x6fc120 id 2 deleted 0 <0x2bd5f680>
31 01/06/14 17:45:16.100 AlarmManager::Run 0x6db2d0 notified of a change entry 0xb45660 id 253 deleted 0 <0x2bb5f680>
31 01/06/14 17:45:16.101 AlarmManager::Run callback for alarm 0x6db2d0 entry 0xb45660 type 52 id 253 param=0x853908 entry->when: 1389051916 time: 1389051916 tnum: 1 slow 0 tardy 0 <0x2bb5f680>
24 01/06/14 17:45:16.101 ZWaveJobHandler::DoReceivedFrame m_iFrameID 230 gwf_drr node 0 command 0x47 data <0x2bb5f680>
24 01/06/14 17:45:16.102 ZWaveJobHandler::DoReceivedFrame m_iFrameID 230 collission with job#28 :getnodedetails 4 dev:7 (0x87f208) P:38 S:7 node 4 <0x2bb5f680>
10 01/06/14 17:45:16.102 AlarmManager::AddRelativeAlarm current time 1389051916 delay 1 type 52 <0x2bb5f680>
10 01/06/14 17:45:16.102 AlarmManager::AddAbsoluteAlarm alarm 0x6db2d0 entry 0xb65830 id 254 type 52 param=0x853908 entry->when: 1389051917 time: 1389051916 bCancelFirst 0=0 <0x2bb5f680>
31 01/06/14 17:45:16.103 AlarmManager::Run finish callback for alarm 0x6db2d0 entry 0xb45660 type 52 id 253 param=0x853908 entry->when: 1389051916 time: 1389051916 tnum: 1 slow 0 duration 0 <0x2bb5f680>
31 01/06/14 17:45:16.103 AlarmManager::Run 0x6db2d0 notified of a change entry 0x6fc120 id 2 deleted 0 <0x2bd5f680>

We’ll probably need more than that from when the plugin starts up, and also make sure that you’ve enabled verbose logging along with removing any sensitive data like PINs or passwords that you don’t want to change afterwards.

I did enable verbose per some of my debugging. I’ve watched this URL then restarted and copied it all into a text file that is attached here.

Let me stop here and say Thank you for your help so far. I really appreciate it.

I’ve noticed a lot of errors regarding the door locks, EchoStar, and some other things like Ergy. I can’t delete some of these devices for some reason. :frowning: Maybe there is a conflict?

I went through the whole log and didn’t see any passwords or anything that I could easily identify as sensitive. Thank you again.

-Paul

Out of curiousity, how many “serial ports” do you have listed under:
Apps / Develop Apps / Serial Port configuration

and do there look like there are any “duplicates”?

In the past, I’ve found that hot “unplugging” a USB-Serial device from Vera, whilst it’s still running, causes all sorts of duplicate Serial-Port problems when it’s later reconnected. I have 4x of these showing in my system, even though there is only one attached, and you have to know the “right” one to configure/attach or it doesn’t work correctly.

It’s only showing the single one with the controller in it. I’ve only seen it show one. I’m assuming it won’t show one for my USB drive for logs right? So I should only be seeing one.

That UI only shows the Serial ports, not everything attached to USB.

Realize this thread is past its expiration date, but since it wasn’t resolved, in case the OP is still struggling with the DSC IT-100, here’s my suggestion. My 5010 is connected to an IT-100 and the IT-100 intermittently stops responding. Its led still flashes normally, it just doesn’t send or receive, including to any sort of terminal program (eg putty). The rest of the panel works great and there are no trouble indicators. I’ve replaced the it-100 as well as going through a couple of cables and the problem persists. I have found the most reliable way to deal with it is to reboot the alarm panel. On the 5010 that means disconnecting the AC then unplugging both batteries, reconnecting the batteries and connecting the AC. The time and date has to be reset. Hardly if needs doing, and I have it automated so I can reset it from afar if necessary. Hope this helps some fellow sufferer aka owner of these things.