ADIOcelot Plugin

[Michael McSharry]

Jim S had a similiar problem that was traced to mixed case in the Interface property of the devices. I made an attempt to correct this with the latest which contains some debug on clock sync just a few posts up. I also posted a utility in this thread to manage the Interface property. This will at least give you an easy way to observe what you have.

[sbessel]

Jim S had a similiar problem that was traced to mixed case in the Interface property of the devices. I made an attempt to correct this with the latest which contains some debug on clock sync just a few posts up. I also posted a utility in this thread to manage the Interface property. This will at least give you an easy way to observe what you have.

I tried the latest version, 1.9.6 and there was no change. I searched the thread and could not find any utility. Is there a way to specify the house codes? I hate to have these change...

[sbessel]

It looks like I have the same problem as jsteed

here is a device hanging off one of my Sec16's It works properly in 1.7.0 anything higher and it does not show up. All the rest of my Ocelot devices are like this one, interface wise.

So what was the fix? I can't see manually editing my .xml file, that seems like a huge risk...

    <z:row record_type='1' can_dim='False' dc='3' dev_type_string='GarageDoor' hc='$' interface='' iomisc='2!11!2!1'
         iotype='0' location='House' misc='16' name='Garage Closed (t)' ref='42832' sldim='0' status='17' status_support='False'
         ui_action='' buttons='' values='' zwave_nodeid='0' zwave_nodetype='0' zwave_pollrate='0' CS_Status='0' IS_Label=''
         IS_Ircommand='' IS_Value='0' IS_Image='' IS_Row='' IS_Column='' delete='False' dtmf='' eprom_address='' ev_abs_time='0'
         ev_app_path='' ev_date='' ev_days='0' ev_dimpercent='0' dim_to='False' ev_func='0' ev_hc='' ev_mail_message=''
         ev_mail_subj='' ev_mail_to='' ev_offset='' ev_offset_before='False' ev_time='' ev_trig_dc='' ev_trig_func='0'
         ev_trig_hc='' ev_wav_path='' events='' group='' handled='0' ir='' irmatch='0' mail_attach_path='' evmisc='0'
         misc_actions='' evmisc2='0' evname='' phone_actions='' phone_event='0' phone_line='0' pi_trig_name='' pi_trigger=''
         popfrom='' rec_mins='0' rec_secs='0' relay='' scripts='' sec_action='' sec_trigger='' security_offset='0' speak_after_script=''
         speak_before_script='' speak_device='0' speech='' vcmd='' pi_actions='' cd_condition='0' cd_ctype='0' cd_dev_ref='0'
         cd_time='' cd_orindex='0' cd_plugin='' dev_devid='0' dev_dim_percent='0' dev_dimto='0' dev_eprom_address='0'
         dev_func='0' dev_new_string='' dev_secs_delay='0' setpoint_action='0' tv_daytime='0' tv_daytimerdate='1899-12-30T00:00:00'
         tv_moddev='' tv_modhouse='' tv_nolimit='False' tv_passdev1='' tv_passdev2='' tv_passdev3='' tv_passdev4='' tv_passhouse=''
         tv_status='0' tv_timetype='0' tv_totaltime='0' tv_useddaytime='0' tv_usedtime='0' tv_username='' retrigger_delay='0'
         graphics=''/> 

[jsteed]

yes, that's what mine looked like. I edited the file manually with an xml editor, XML Marker which made it fairly painless. Sort by housecode and then cut/paste. You'll need to do it with HS shutdown. Just make sure that you keep a backup (or two).

The utility that Michael mentioned, ManageInterface, was included in the AdiOcelot194.zip.

jim

[jsteed]

Michael,
When you send the packet to the ocelot are you sending 1-7 for the weekday or 0-6?

I want to experiment a little more with this but I did get this yesterday during one run. I had just restarted HS with 1.9.6.

1/30/2005 8:41:44 PM~!~Speak~!~HVAC Status Devices Initialized.
1/30/2005 8:43:01 PM~!~ADIOcelot~!~Initiating 59 second wait for start of next minute to set clock
1/30/2005 8:44:00 PM~!~ADIOcelot~!~For Weekday 1, Setting Clock to 200501302044
1/30/2005 8:45:00 PM~!~Event Trigger~!~Recurring Trigger (Temperature Log)
1/30/2005 8:45:09 PM~!~ADIOcelot~!~Initiating 51 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:46:01 PM~!~ADIOcelot~!~Initiating 59 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:00 PM~!~ADIOcelot~!~Initiating 0 second wait for start of next minute to set clock
1/30/2005 8:47:01 PM~!~ADIOcelot~!~Initiating 59 second wait for start of next minute to set clock
1/30/2005 8:48:00 PM~!~ADIOcelot~!~For Weekday 1, Setting Clock to 200501302048

jim

[Michael McSharry]

I believe I'm sending 1..7. This should be visible from the debug that shows both the weekday from the OS and the bytes sent. All the messages with 0 second wait should not be there. I may have messed up something when I looked for 0 rather than 59.

[jsteed]

After I posted last night I found a second version of the set clock function (same document as the first version, just two pages farther down). It's mostly the same except for a couple of items. I'll post it tonight when I get home. I noticed with the second one rather than having the leading zeros that it showed those two positions as setting the seconds digits. That should eliminate the need to sync the clock set.
jim

[Michael McSharry]

That was the hardest part of the implementation. Making it simpler would be best.

[jsteed]

Here's the alternate version (why this is defined twice in the same document I'm not sure). This indicates that the seconds can be set as well.

The other thing that it shows is that it's looking for weekday to be 0-6. That would explain how it's acting on my system. However, it doesn't explain why it's working on Paul's system. (I hate stuff like this- makes my head hurt)
jim

Set CPUXA Real Time Clock
->Send 50 binary bytes: <241> <61> <n2> <n3>…… <n47> <n48> <csum>
<-Receive 3 byte header: <6> <0> <6>
Note: This command loads and starts the CPU-XA Real Time Clock.

n2 = 61; //set RTC
n3 = seconds ones digit 0-9 (23:59:3x)
n4 = seconds tens digit 0-5 (23:59:x4)
n5 = minutes ones digit 0-9 (23:5x:34)
n6 = minutes tens digit 0-6 (23:x9:34)
n7 = hours ones digit 0-3 (2x:59:34)
n8 = hours tens digit 0-2 (x3:59:34)
n9 = day ones digit 0-9 (12/0x/99)
n10 = day tens digit 0-3 (12/x4/99)
n11 = month ones digit 0-9 (1x/04/99)
n12 = month tens digit 0-1 (x2/04/99)
n13 = year ones digit 0-9 (12/04/9x)
n14 = year tens digit 0-9 (12/04/x9)
n15 = day of the week 0-6 (Sunday-Saturday)

csum = the 8 bit sum of 241 + 61 + n2 + n3 + n4…n47 + n48

[Michael McSharry]

I added the seconds, made the weekday range 0..6, and changed the sync algorithm to try to set the clock 2 seconds after button push or at 1 AM. Some form of sync/retry is needed to handle the situation where the ocelot is busy at the time the set clock desires to start. Debug still in at point of setting the clock.

[jsteed]

Thanks, I shoudl be able to take a look at it this weekend.
jim

[jsteed]

Michael,
I think you grabbed the wrong file when you posted the last version. The plugin identifies itself as 1.8.0 and the file is dated 11/17/2004. When you have time.
thanks
jim

[Michael McSharry]

Try again

[jsteed]

It's been loaded for about 24 hours now. I set the clock several times yesterday and today. So far I haven't seen anything that I shouldn't. I'll keep an eye on it for a day or two but it appears to be working fine for me now.

As others have said- thank you for the time and effort that you spend making this and other items available for the rest of us.
jim

[Michael McSharry]

Thank you also Jim for those who will want this feature in the future. I posted V1.9.8 at the top of the thread and it is the same as 1.9.7 without the write to the log at time of the clock being set.