Announcement

Collapse
No announcement yet.

Homeseer reading ocelot variables.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Per the LEOPARD manual:
    Variables 0 – 59 are general-purpose memory locations that can be used to count events or to initiate quasi-subroutines.

    Variable 60 indicates the last received IR. (65535 indicates a non-recognized IR)
    Variable 61 is not used in the Leopard™.
    Variable 62 is the beep function. The Leopard will beep for the amount of seconds you set variable 62 to.
    Variable 63 selects the displayed screen.
    Variables 64 – 79 indicate the X-10 temperature received from an RCS® Thermostat. If you are not using an RCS® Thermostat (parameter 21 = 0), variables 64-79 can be used for general-purposes.
    Variables 80-127 are general-purpose memory locations.


    Per the OCELOT:

    Variable 61 is not used in the Ocelot™.
    Variable 62 is for factory use only.
    Variable 63 is not used on the Ocelot™.
    Variables 64 – 79 indicate the X-10 temperature received from an RCS
    Thermostat.

    (see profile for environment)

    Comment


      #17
      Ok, thanks for the info on the variables.

      The variable 62 changing is not causing the problem, and that got me sidetracked. When HS polls for the variables, it should catch any that change. Whats happening is that the plugin keeps a local copy of all the variables so it doesn't have to keep asking HS what the current values are. This speeds up processing. The local copy and real copy where becoming out of sync and HS was showing the wrong value. I made a change to insure that changed variables would be detected on the next poll and HS would be updated properly. This would not fix an issue where a variable changes from 1 to 0 to 1 again within the poll time. The plugin would not detect this change. Unfortunately the Ocelot does not notify me of variable changes like it does for I/O and X10. The change does fix this timer issue where HS sets a variable and the Ocelot changes it back.

      The new version of the plugin is 1.0.24 and is posted to the updater.

      -Rich

      HomeSeer Technologies LLC
      💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

      Comment


        #18
        Rich,

        Great I will give it a try tonight..

        StevenE
        Why oh why didn't I just leave things alone, they had been working.

        Comment


          #19
          Rich

          The variables now update and run great.

          Thank for the help and fix.

          StevenE
          Why oh why didn't I just leave things alone, they had been working.

          Comment


            #20
            Any chance I could get a copy of your CMAX logic and an understanding of the events in HS that you created to build a watchdog for HS?

            I haven't played with timers in CMAX (or done that much CMAX coding). Any help would be appreciated.

            Did you use a relay to actually hard reset the PC?

            SteveP

            Comment


              #21
              Steve p,
              I don't know how reliable it is yet. it has been running for about a week. and once it triggered the safety. ( could have been something i did )
              And I am by no means an expert with hs or cmax.

              if timer #0 = 0
              then timer #0 = 1 ( start timer counting. )
              if timer #0 is > 93 ( if timer is over 93 seconds )
              or Timer #0 is = 0
              then module# 3/point# 8 turns off ( turn off relays on modules )
              then......... ( all relays on modules. )
              then time # 0 is 1 ( set timer 0 back to 1 )
              then variable # 10 is 13 ( set variable 10 to 13
              else load data to: variable # 6 ( copy timer count to variable )
              ( just so i can see the timer in hs )


              if timer #0 is > 20 ( if timer is over 20 seconds )
              and variable #10 = 97 ( and variable 10 is 97
              then time # 0 is = 1 ( set timer 0 back to 1 )
              then variable #10 = 3 ( set variable 10 to 3 )


              in hs I have variable 10 and variable 6
              variable 6 shows me the count of timer 0.
              variable 10 has 1 event.

              a recurring event every 30 seconds.
              with the condition.
              if variable 10 = 3
              then set variable 10 to 97


              The hs controls the heat in my house through the ocelot. So at worst case the heat is on for 93 seconds with no hs control
              and if hs is not responding the ocelot turns off the relays every 93 seconds.
              ( i have wall thermostats set at the minimum temp the house is allowed 55 degrees )
              Why oh why didn't I just leave things alone, they had been working.

              Comment


                #22
                I will review this and see if I can implement it here.

                SteveP

                Comment

                Working...
                X