Announcement

Collapse
No announcement yet.

UPB Plug-in - Beta Testing

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

  • #16
    Originally posted by Pete View Post
    I am not seeing anything in the HS3 logs regarding turning on and off of the lights.
    If you go to the config page and set the log level to debug, you will see a lot more stuff logged. But maybe I should move some of these logs at the INFO level?

    Originally posted by Pete View Post
    Is there anything in particular that you want me to test at this time?
    Nothing specific, just make sure you can control all your devices from HS. I already know that the UPB devices that use more than 1 channel don't work correctly. So I have to fix that.

    Comment


    • #17
      Set the configuration to debug.

      Here is the log playing with two switches. The garage UPB is a dual load; multitoggle switch. I do notice that only the garage coach lights show up and not the interior garage lighting shows. I utilize many links. Migrated a couple of years ago from single toggle UPB switches to multitoggle (with many links) and dual load switches. Wife knows the kitchen switches better than me. (4-4 multitoggle switches there for the lighting in the kitchen stuff).

      Yup: personally I am OK with the stuff at the debug level versus the info level; but that is me.

      Nov-25 8:56:22 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C37FF220020{0xD}]
      Nov-25 8:56:22 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
      Nov-25 8:56:22 AM UPB DEBUG PIM_SEND:: Sending Message ID 12 to PIM, retry count=0
      Nov-25 8:56:22 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 12)
      Nov-25 8:56:22 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
      Nov-25 8:56:22 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
      Nov-25 8:56:22 AM Device Control Device: Outside Garage Coach to Off (0) by/from: CAPI Control Handler
      Nov-25 8:56:15 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU09056CFF37860707BC]
      Nov-25 8:56:12 AM UPB DEBUG DEVICE[55]:: Level changing on channel 1 from 0 to 7
      Nov-25 8:56:09 AM UPB DEBUG DEVICE[55]:: Level changing on channel 0 from 0 to 7
      Nov-25 8:56:09 AM UPB DEBUG PIM_SEND:: Resuming sending as we received at least one device message
      Nov-25 8:56:09 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU09046CFF37860707BD]
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Pausing because last command expected a reply
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Message ID 34 confirmed sent successfully
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=34)
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=34)
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[07146C37FF3013{0xD}]
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Sending Message ID 34 to PIM, retry count=0
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 34)
      Nov-25 8:56:08 AM UPB DEBUG DEVICE[55]:: Confirmed request to set device to level succeedded -- updating internal state
      Nov-25 8:56:08 AM UPB DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
      Nov-25 8:56:08 AM UPB DEBUG UPB_MGR:: STATE_QUEUE:: Sending state queury for device Garage Coach (55)
      Nov-25 8:56:08 AM UPB DEBUG DEVICE[55]:: Got request to set light to non-normative level -- queueing status request to confirm
      Nov-25 8:56:08 AM UPB DEBUG PIMADAPTER:: Confirmed message to device succeeded
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: Message ID 11 confirmed sent successfully
      Nov-25 8:56:08 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=11)
      Nov-25 8:56:07 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=11)
      Nov-25 8:56:07 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C37FF2264BC{0xD}]
      Nov-25 8:56:07 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
      Nov-25 8:56:07 AM UPB DEBUG PIM_SEND:: Sending Message ID 11 to PIM, retry count=0
      Nov-25 8:56:07 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 11)
      Nov-25 8:56:07 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
      Nov-25 8:56:07 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
      Nov-25 8:56:07 AM Device Control Device: Outside Garage Coach to On (100) by/from: CAPI Control Handler
      Nov-25 8:56:02 AM UPB DEBUG DEVICE[54]:: Confirmed request to set device to level succeedded -- updating internal state
      Nov-25 8:56:00 AM UPB DEBUG DEVICE[54]:: Level changing on channel 0 from 100 to 0
      Nov-25 8:56:00 AM UPB DEBUG PIMADAPTER:: Confirmed message to device succeeded
      Nov-25 8:56:00 AM UPB DEBUG PIM_SEND:: Message ID 10 confirmed sent successfully
      Nov-25 8:56:00 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=10)
      Nov-25 8:55:59 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=10)
      Nov-25 8:55:59 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C36FF220021{0xD}]
      Nov-25 8:55:59 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
      Nov-25 8:55:59 AM UPB DEBUG PIM_SEND:: Sending Message ID 10 to PIM, retry count=0
      Nov-25 8:55:59 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 10)
      Nov-25 8:55:59 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
      Nov-25 8:55:59 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
      Nov-25 8:55:59 AM Device Control Device: Outside Front Door to Off (0) by/from: CAPI Control Handler
      Nov-25 8:55:55 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU08056CFF36866468]
      Nov-25 8:55:53 AM UPB DEBUG PIM_SEND:: Resuming sending as we received at least one device message
      Nov-25 8:55:53 AM UPB DEBUG DEVICE[54]:: Level changing on channel 0 from 0 to 100
      Nov-25 8:55:53 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU08006CFF3686646D]
      Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: Pausing because last command expected a reply
      Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: Message ID 33 confirmed sent successfully
      Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=33)
      Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=33)
      Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[07146C36FF3014{0xD}]
      Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: Sending Message ID 33 to PIM, retry count=0
      Nov-25 8:55:52 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 33)
      Nov-25 8:55:52 AM UPB DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
      Nov-25 8:55:52 AM UPB DEBUG UPB_MGR:: STATE_QUEUE:: Sending state queury for device Front Door (54)
      Nov-25 8:55:49 AM UPB DEBUG DEVICE[54]:: Confirmed request to set device to level succeedded -- updating internal state
      Nov-25 8:55:49 AM UPB DEBUG DEVICE[54]:: Got request to set light to non-normative level -- queueing status request to confirm
      Nov-25 8:55:49 AM UPB DEBUG PIMADAPTER:: Confirmed message to device succeeded
      Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: Message ID 9 confirmed sent successfully
      Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=9)
      Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=9)
      Nov-25 8:55:48 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
      Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C36FF2264BD{0xD}]
      Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: Sending Message ID 9 to PIM, retry count=0
      Nov-25 8:55:48 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 9)
      Nov-25 8:55:48 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
      Nov-25 8:55:48 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
      Nov-25 8:55:47 AM Device Control Device: Outside Front Door to On (100) by/from: CAPI Control Handler
      Nov-25 8:55:40 AM Device Control Device: Outside Garage Coach to Off (0) by/from: CAPI Control Handler
      Nov-25 8:55:27 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU09056CFF37860000CA]
      Nov-25 8:55:26 AM UPB DEBUG PIM_SEND:: Resuming sending as we received at least one device message
      Nov-25 8:55:26 AM UPB DEBUG PIM_RCVR:: Received UPB command [PU09046CFF37860000CB]
      Nov-25 8:55:26 AM UPB DEBUG PIM_SEND:: Pausing because last command expected a reply
      Nov-25 8:55:26 AM UPB DEBUG PIM_SEND:: Message ID 32 confirmed sent successfully
      Nov-25 8:55:26 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=32)
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=32)
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[07146C37FF3013{0xD}]
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Sending Message ID 32 to PIM, retry count=0
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 32)
      Nov-25 8:55:25 AM UPB DEBUG DEVICE[55]:: Confirmed request to set device to level succeedded -- updating internal state
      Nov-25 8:55:25 AM UPB DEBUG UPB_MGR:: passing queueMessage for UPB message to media-adapter
      Nov-25 8:55:25 AM UPB DEBUG UPB_MGR:: STATE_QUEUE:: Sending state queury for device Garage Coach (55)
      Nov-25 8:55:25 AM UPB DEBUG DEVICE[55]:: Got request to set light to non-normative level -- queueing status request to confirm
      Nov-25 8:55:25 AM UPB DEBUG PIMADAPTER:: Confirmed message to device succeeded
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Message ID 8 confirmed sent successfully
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: UPB Device ACK'd current message (ID=8)
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: PIM ACK'd current message (ID=8)
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: ABOUT_TO_SEND[08146C37FF2264BC{0xD}]
      Nov-25 8:55:25 AM UPB DEBUG PIMADAPTER:: Confirmed message marked as being sent, timeout timer has 10000 millis left
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Sending Message ID 8 to PIM, retry count=0
      Nov-25 8:55:25 AM UPB DEBUG PIM_SEND:: Extracted next message to send from queue (ID 8)
      Nov-25 8:55:25 AM UPB DEBUG PIMADAPTER:: Got update on Confirmed message, but still not sent to PIM yet
      Nov-25 8:55:24 AM UPB DEBUG UPB_MGR:: passing sendConfirmedMessage for UPB message to media-adapter
      Nov-25 8:55:24 AM Device Control Device: Outside Garage Coach to On (100) by/from: CAPI Control Handler
      Attached Files
      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
      Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

      Comment


      • #18
        new version available 3.0.0.5

        I have uploaded a new version in first post of this thread.

        The plugin has been renamed to UPBSpud to avoid any license issue with the existing UPB plugin for HS2. So if you are upgrading from a previous version you will need to delete all your UPB devices (UPB Device and UPB Link types)

        I/O devices and devices using several channels are now supported.

        Please test and report any bug. Thanks

        Comment


        • #19
          Thanks Spud!

          - Linux testing with a SA UPB serial PIM to a USB to Serial cable coming up as \dev\ttyUSB0 or \dev\ttyUSB1

          - Updated two HS3 Linux boxes to V.46; Ubuntu 64bit and Ubuntu32bit.

          - Updated remote directories on two above mentioned boxes and Zee.

          - First box tested - HS3 32bit Ubuntu
          a - ran HS3
          b - deleted UPB events and devices
          c - deleted legacy UPB plugin
          d - shut down HS3
          e - deleted files related to legacy UPB plugin
          f - started HS3 and installed new UPB plugin
          g - ran remote plugin on Ubuntu 64 bit
          h - imported export UPB file
          i - box created devices and links (sees dual load switches just fine)

          - Second box tested - HS3 64bit Ubuntu
          a - as above but ran the plugin locally the first time run
          b - imported export file and it created devices and links
          c - disabled plugin
          d - deleted all UPB devices
          e - shut down HS3 lite on Zee
          f - ran remote UPB on Zee
          g - connected and and it created all of the devices and links
          h - probably some 50% slower than the 64bit and 32 bit remote Ubuntu UPB run.
          i - working fine as above (just slower).
          j - will create a few events today.

          Updated Wintel HS3 box yesterday with HS3 V46. Will test UPB plugin on said box today using a Quatech serial server connected UPB serial PIM. Testing will be utilizing an HAI serial UPB PIM connecting via IP serial to network.
          - Pete

          Auto mator
          Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
          Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

          X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

          Comment


          • #20
            Attached Files

            Comment


            • #21
              to see 3.0.0.5 as an option in the updater you need to download the updater_override.txt file from first post of this thread and put it in your HS3 directory. This file changes everytime a new beta version is released so you have to download it everytime.

              so step to proceed:
              - disable UPBSpud from the Manage page
              - copy UPBSpud_3-0-0-5.zip to /Updates3/Zips
              - copy updater_override.txt to your HS3 root directory
              - click the "Update Listing" button, then click "Additional interfaces > Test Plugin". You should see only one line and it should be UPBSpud 3.0.0.5

              You need 3.0.0.5 for your UMI module to work.

              Comment


              • #22
                Also make sure you delete an old UPB related events before deleting the devices. I forgot to do this the first time.

                Spud,

                Where is it the files are supposed to go (or be installed)?

                Initially I thought everything went under the BIN subdirectory; but noticed that only one file goes there and the other files mostly go to the HS root directory.

                Noticed that
                /usr/local/HomeSeer/bin/UPBSpud/UPB4CSharp.dll
                and
                HSPI_UPBSpud.exe and HSPI_UPBSpud.exe.config are in the /HomeSeer root directory.

                Can I delete the old UPB bin directory and HSPI_UPB.exe and HSPI_UPB.exe.config files?
                - Pete

                Auto mator
                Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                Comment


                • #23
                  Originally posted by Pete View Post

                  Where is it the files are supposed to go (or be installed)?
                  HSPI_UPBSpud.exe and HSPI_UPBSpud.exe.config go to to the HS root directory
                  UPB4CSharp.dll goes to bin/UPBSpud
                  images.zip is unzipped to html/images

                  Originally posted by Pete View Post
                  Can I delete the old UPB bin directory and HSPI_UPB.exe and HSPI_UPB.exe.config files?
                  yes you can delete the UPB bin directory and both HSPI_UPB.exe and HSPI_UPB.exe.config files

                  Comment


                  • #24
                    Thank-you Spud.
                    - Pete

                    Auto mator
                    Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                    Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                    Comment


                    • #25
                      What is this error about?

                      11/27/2013 9:54:48 PM ~!~Error~!~Displaying remotely connected interfaces: Object reference not set to an instance of an object.

                      Comment


                      • #26
                        Attached Files

                        Comment


                        • #27
                          UMI and other potentially "interesting devices"

                          Spud, when you mentioned the UMI "seems very different from all other UPB devices" it occurred to me that you should know of at least one other “interesting device”, the US2-40

                          BTW - at this time the US2-40 seems to be working fine with the PI. More testing to come, etc....
                          --------------

                          Personal notes from my setup logs.

                          To operate as both a local device and a controller, the unit (Office Lighting) needs to have Link 241 active. This is placed in the Config automatically at installation. If the 241 link is deleted, the rocker switch will not control the load.

                          - DO NOT DELETE 241 -

                          ---------------

                          Additional discussion

                          http://cocoontech.com/forums/topic/2...t-light-level/

                          --------------

                          Extract from the data sheet
                          http://simply-automated.com/document...ide_090512.pdf

                          The US2 is configured from the factory to accept a single rocker, or a multi-rocker faceplate, where the top-left (#1) rocker provides ON/OFF and dimming control functions for the connected light fixture (local load). However, the local load may be assigned to ANY rocker or button using a link which must be present in both the transmit and receive tables accessible via UPStart. The factory default for local load control is ‘Link 241’ with the transmit options disabled. Additional rockers / buttons function as transmitters to other UPB devices. Local load may be included in any scene using the link feature in UPStart. See illustration at right for actuator numbering examples.


                          --------------

                          Unsure whether UPB would survive the protocol wars, I have only purchased a few items. There may be other UPB devices that act in a similar fashion.

                          Terry
                          Last edited by tam; November 28th, 2013, 12:11 AM. Reason: Clarifications

                          Comment


                          • #28
                            Terry,

                            Interesting mention on the PCI watchdog timer. I used a similiar one many years ago. The currently utilized (one of them) BCM motherboard has a built in watchdog timer as part of the BIOS (industrial mITX board).

                            This is just an information list of the UPB switches I am using and related validating function of said switches related to plugin.

                            Here I have one serial HAI PIM connected to HAI OPII panel, one serial HAI PIM connected to HS2 box, HAI serial PIM floater (Quantech box), SA serial PIM for test HS3 connections.

                            So far all appears fine with the switches and links. Recently have gone from the two in a box switch configurations to single multitoggle switches with oversized difficult to find wall switch plate covers. Nicer footprint and easy to use with links.

                            I am moving towards looking to migrate my outdoor 12VDC LED LV to multiple zoned switching and adding more zones.
                            Right now have some 12 lighting zones connected to 4 LED LV transformers switched by one HAI Relay module which works fine.

                            PCS - WS1D wall switch
                            HAI - 35A00-1 600W dimming wall switch
                            HAI - 40A00-1 15A Relay switch
                            HAI - 59A00-1 300W lamp module
                            SA - UML Lamp Module - Timer
                            SA - US1 / US2 Series Dimming switch
                            US1-40 Single rocker dimming switch - Timer
                            US2-40 Series Dimming switch
                            US22-40T Series Dimming switch

                            HAI - 39A00-2 Split Phase Repeater
                            Last edited by Pete; November 28th, 2013, 06:28 AM.
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                            Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                            Comment


                            • #29
                              Originally posted by Dr_Crash View Post
                              11/27/2013 9:54:48 PM ~!~Error~!~Displaying remotely connected interfaces: Object reference not set to an instance of an object.
                              This is not a UPB specific error, so it hard to say what's going on.
                              Could you give me some more information?
                              What are you trying to do?
                              When does this error show up?
                              Have you installed the UPBSpud plugin successfully?
                              etc...

                              Comment


                              • #30
                                So, have you tested the UMI with 3.0.0.5? Does it work fine?

                                Comment

                                Working...
                                X