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

  • jstaab
    replied
    Geese so there isn't a single line to turn on and off a device by its name!? Good grief.

    Sent from my SCH-I45 using Tapatalk

    Leave a comment:


  • spud
    replied
    Originally posted by jstaab View Post
    Ok, so with HS2, we had the ability to set a device off and on via a script via execX10ByName. With HS3, I think that is gone. With that said, I ASSUME that we are now to use setDeviceValue to say 0 and 100 to represent off and on? With that said, via script, I used SetDeviceValueByName to set a devices value to 100, but the UPB device did not turn on. I did confirm the device value to change to 100. Should UPB devices response to device value changes? If not, what is the proper way to now turn on, off and DIM a UPB device via a script?
    I think the right way to do this in HS3 is to use the Device Control API (CAPI). Some examples here: http://board.homeseer.com/showthread...ht=CAPIControl

    Alternatively I could add to the plugin some public functions accessible by script like TurnDeviceOn, TurnDeviceOff, etc...

    Leave a comment:


  • jstaab
    replied
    Device Off and On via script

    Ok, so with HS2, we had the ability to set a device off and on via a script via execX10ByName. With HS3, I think that is gone. With that said, I ASSUME that we are now to use setDeviceValue to say 0 and 100 to represent off and on? With that said, via script, I used SetDeviceValueByName to set a devices value to 100, but the UPB device did not turn on. I did confirm the device value to change to 100. Should UPB devices response to device value changes? If not, what is the proper way to now turn on, off and DIM a UPB device via a script?

    Leave a comment:


  • Pete
    replied
    Thank-you Spud.

    Shut down HS3. Updated files from zip. Restarted HS3 and all is OK.

    Not sure what the issue was the "updater_override.txt" file ; that said the download of V.4 from the updater worked fine for me originally; even though it was a downgrade from V.5.
    Last edited by Pete; November 30th, 2013, 05:26 PM.

    Leave a comment:


  • spud
    replied
    strange, just tested reinstalling .6 on windows and all went fine.

    anyway to upgrade you can just unzip, then copy UPB4CSharp.dll to bin/UPB and HSPI_UPBSpud.exe to your HS3 root. All the other files haven't changed.

    Leave a comment:


  • Pete
    replied
    Hello Spud,

    Went to update today to most current version of the plugin as posted in the OP.

    Seeing this error.

    Please wait for the updater control file failed to be downloaded or parsed.
    If I remove the "updater_override.txt" I see all of the regular HS3 plugins.

    I did disable and delete the old version of the plugin.

    I do notice that your plugin version dot 4 is showing up in the updater now.

    I installed the one from the Updater. Disabled it and tried to update with most current OP file V.6.

    I am still getting the above mentioned error and cannot install most current update.
    Last edited by Pete; November 30th, 2013, 01:45 PM.

    Leave a comment:


  • Dr_Crash
    replied
    So far all is stable and very quick. This is a great plugin. Thanks.

    Leave a comment:


  • spud
    replied
    Cool, thank you for all the tests!

    Leave a comment:


  • tam
    replied

    Leave a comment:


  • tam
    replied
    98% Functional

    The 2% may be an UpStart thing. I will test further.

    All the problems listed before have been fixed.

    I just registered.

    Thanks

    Terry

    Leave a comment:


  • spud
    replied
    thank you for the tests!

    Please try version 3.0.0.6 attached to first post of this thread. I believe I have fixed some of the bugs you reported.

    Leave a comment:


  • tam
    replied
    V5 ~ 35% Functional

    Spud:

    I created from scratch an UpStart config with just two devices, the UMI and a wall switch which controls the office lights.

    Minimal links

    All tested fine in UpStart
    In 1 closed - lights 10%
    In 1 open - lights off
    In 2 closed - lights 40%
    In 2 open - lights off
    In 3 closed - lights 80%
    In 3 open - lights off

    In the PI:
    Input 1 is ON all the time
    Input 2 is OFF all the time
    Input 3 is OFF all the time
    ...no matter what Input is closed.
    But, the office lights responded exactly as they did when tested in UpStart

    The PI accurately shows the illumination of the lights for each UMI input state

    Also, Out 1's state always changes to ON, when ever any Input is closed.
    Out 1's state changes back to OFF when that Input is again open

    Out1 and Out2 both function normally when clicking them ON/OFF via the PI.

    I have attached the UPE and 16 pages of screen shots to assist with this.

    Let me know how I can further assist.

    Terry
    Attached Files

    Leave a comment:


  • tam
    replied
    V5 ~75%

    So, have you tested the UMI with 3.0.0.5? Does it work fine?
    Spud:

    UpStart Definition
    With regards to UpStart (US), the program itself has always seemed a little odd.
    Putting aside its “cutesy dialogs”, how US specifies the UMIs input and outputs is backward.


    Going forward I will refer to-
    The three channels that respond to external stimuli as Inputs.
    The two channels that provide contact closure are Outputs.


    Summary:
    The PI appears to be ~75% functional.
    -All 5 channels appear

    -Input channels 1 and 3 respond
    -Input channel 2 does not

    -Output channels 1 and 2 have not been tested

    -The links don’t appear to respond either as they did with the HS2 PI. At this time that is not an issue.

    The means of testing may be affecting channel 2. See “Trigger Issue?” below

    I will move the UMI and the attached wiring panel from the cramped upper corner in the server room to a “lab” environment. With the assembly sitting next to my HS3 box the testing can be more precise.

    If I remember correctly you are using borrowed equipment. I respect the timeline that imposes.
    More detail should be available tomorrow morning.


    Detail:


    Because the family home is home today, the testing that least degrades WAF is to leave the garage doors alone.

    Normally when testing like this, the modified CAT5 cable that travels to the garage is unplugged from the assembly. A dummy cable is used in it’s place.

    Trigger Issue?
    The dummy cable when plugged in completes the voltage sense for channels 1 and 2, illuminating the two UMI LED channel indicators simultaneously. Channel 3 is on a separate connector to the assembly and is not an issue. It is because of the cramped quarters that the dummy was made.

    It is the simultaneous action on channels 1 and 2 that **may** be why Input 2's state change is not appearing in the PI.

    Making a Channel 1 and a Channel 2 dummy would be faster than moving the assembly.

    However….

    In the US options for the UMI the Output channels are specified as momentary. I need to stand next to the UMI to see how the PI responds for those two seconds.

    T
    Last edited by tam; November 28th, 2013, 02:45 PM. Reason: Clarification

    Leave a comment:


  • spud
    replied
    So, have you tested the UMI with 3.0.0.5? Does it work fine?

    Leave a comment:


  • spud
    replied
    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...

    Leave a comment:

Working...
X