Announcement

Collapse
No announcement yet.

UltraM1G HSPI - Feature Requests

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

  • bdhall
    replied
    Originally posted by Ultrajones View Post
    I just added GetZoneState() and GetOutputState to UltraM1G HSPI version 1.1.3060.26371. Check out the UltraM1G Users Guide for an example on how to use them.
    Ultrajones,

    I tried the GetOuputState Function and it looks good.

    I did notice a minor typo in the docs:

    Dim strOutputName = Zone("Name")
    Dim strOutputStatus = Zone("Status")
    Dim strOutputLastChange = Zone("LastChange")

    I believe you intended to have "Output" instead of "Zone" in your example.

    Thanks for the update, it will be a big help.

    Brian

    Leave a comment:


  • Ultrajones
    replied
    I just added GetZoneState() and GetOutputState to UltraM1G HSPI version 1.1.3060.26371. Check out the UltraM1G Users Guide for an example on how to use them.
    Last edited by Ultrajones; May 18, 2008, 03:35 PM.

    Leave a comment:


  • bdhall
    replied
    Originally posted by brian270999 View Post
    This is great news and will help a lot. Thank you for checking on this.

    Are you still planning to add support for reading the status of individual outputs?

    Thanks!
    Brian
    bump

    Leave a comment:


  • bdhall
    replied
    Originally posted by Ultrajones View Post
    Spanky from Elk indicated counters would be available in the next firmware release. I'll add support for it shortly after they release the firmware update ...
    This is great news and will help a lot. Thank you for checking on this.

    Are you still planning to add support for reading the status of individual outputs?

    Thanks!
    Brian

    Leave a comment:


  • Ultrajones
    replied
    Spanky from Elk indicated counters would be available in the next firmware release. I'll add support for it shortly after they release the firmware update ...

    Leave a comment:


  • bdhall
    replied
    Need access to variables

    From another post last year:

    "I checked with Elk Tech Support and there is no way to get access to the 64 counters using the ASCII Protocol." Has there been any change on this? - would be a very handy feature since the custom values are limited to 20.


    I tried to figure a way to use the lighting for storing and retrieving variables without having the PLC connected but that looks like a no go.


    Unless the counter access has changed, I guess that leaves using outputs as the last option. I noticed a feature request for adding GetOutputStatus to scripting API. Any idea if/when we will see this?

    Thanks!
    Brian

    Leave a comment:


  • Ultrajones
    replied
    Originally posted by jlegault View Post
    Would be nice to be able to write to custom values, I control my sprinkler zone times and hvac program via custom values.
    Writing to custom settings should be available in the latest version.

    I'll be posting an update in the next few days that will include documenation and a few new features. The docs should show how to write to the custom settings ...

    Regards,
    Ultrajones

    Leave a comment:


  • jlegault
    replied
    Would be nice to be able to write to custom values, I control my sprinkler zone times and hvac program via custom values.

    Leave a comment:


  • Ultrajones
    replied
    New Feature

    Originally posted by ScottKemp View Post
    A couple more things related to above...

    When creating an event using Elk Zones/Outputs for either the trigger combo box or the action combo box, they are listed as "Output 1", "Output 2", etc, rather than what I named them in Homeseer or even ElkRP for that matter.

    I would prefer to see the Home seer name in that list as I will be having possibly as many as a 100 inputs and outputs and trying to keep the numbers straight will be tough.

    Thanks!

    Scott
    UltraM1G version 1.1.2922.27929 adds Area, Keypad, User, Zone, Output and Task names to HomeSeer triggers, conditions and actions.

    Leave a comment:


  • Ultrajones
    replied
    Originally posted by MPodlin View Post
    Could you add some additional thermostat triggers, conditions, and actions?

    Triggers and Conditions:
    • mode set to Heat, Cool, Auto or Off.
    • temp equals.
    I believe you can use a Device Value change to detect this. Within your HomeSeer event, select the Condition Tab, then select "Device Value Change", then select the HomeSeer device.

    Actions:
    • Set CoolSetPoint or set HeatSetPoint
    • Set mode to Heat, Cool, Auto or Off.
    These 2 options are already available. You access them though the CoolSetPoint, HeatSetPoint or Mode HomeSeer device. In the Event Action Tab, just select "Device Action", then select the HomeSeer device.

    I have a couple Elk rules now to adjust the thermostat down at night and back up in the morning, but once and awhile the elk seems to miss adjusting the thermostat. I'd like to fire off a HS event to check the thermostats 10 minutes after the elk should have adjusted them, and if they aren't set to the correct temp, have HS and UltraM1G adjust them.

    The Pod
    As stated by Chakara, this is a known issue and appears to be corrected in the next M1XSP firmware release. I have been testing it and it seems to be MUCH better and executing the commands.

    Firing off an event to "check the thermostat" won't work because the Elk M1 already thinks the value is correct. Elk Tech Support recommends just sending the command again. Hopefully the new M1XSP firmware will eliminate the need for this additional step.

    Regards,
    Ultrajones

    Leave a comment:


  • Chakara
    replied
    Originally posted by MPodlin View Post
    I have a couple Elk rules now to adjust the thermostat down at night and back up in the morning, but once and awhile the elk seems to miss adjusting the thermostat.
    That missed thermostat command issue is known by Elk and should be fixed in the next firmware update for the serial expander....

    Leave a comment:


  • MPodlin
    replied
    Could you add some additional thermostat triggers, conditions, and actions?

    Triggers and Conditions:
    • mode set to Heat, Cool, Auto or Off.
    • temp equals.


    Actions:
    • Set CoolSetPoint or set HeatSetPoint
    • Set mode to Heat, Cool, Auto or Off.


    I have a couple Elk rules now to adjust the thermostat down at night and back up in the morning, but once and awhile the elk seems to miss adjusting the thermostat. I'd like to fire off a HS event to check the thermostats 10 minutes after the elk should have adjusted them, and if they aren't set to the correct temp, have HS and UltraM1G adjust them.

    The Pod

    Leave a comment:


  • Ultrajones
    replied
    Originally posted by MPodlin View Post
    When adding HomeSeer devices for thermostats, could you make it so the each of the thermostat items can be added individually. Example is I have 2 RCS16 thermostats which do not report humidity, so I would like to not add this as a HS device. Also one thermostat controls both the AC and heat, but the other is only a furnace so it would be nice on the second thermostat not to add the cool set point as a HS device.
    I can add this to the feature request list. In the mean time, just delete the ones you don't want. They won't be re-created and will be ignored by the plug-in. Just don't delete the mode devices as this is the primary thermostat device.

    Could you also add HS logging of device status changes coming from the Elk and use the check box in the HS device "Do not log commands from this device" as the option to add or not add the device changes to the HS log from the Elk. This could be useful with UltraLog and querys to track how many times a specific elk zone/input/output/etc changed over a period of time.
    The Pod
    This feature should already in there for zones, inputs, outputs, etc.

    Regards,
    Ultrajones

    Leave a comment:


  • MPodlin
    replied
    When adding HomeSeer devices for thermostats, could you make it so the each of the thermostat items can be added individually. Example is I have 2 RCS16 thermostats which do not report humidity, so I would like to not add this as a HS device. Also one thermostat controls both the AC and heat, but the other is only a furnace so it would be nice on the second thermostat not to add the cool set point as a HS device.

    Could you also add HS logging of device status changes coming from the Elk and use the check box in the HS device "Do not log commands from this device" as the option to add or not add the device changes to the HS log from the Elk. This could be useful with UltraLog and querys to track how many times a specific elk zone/input/output/etc changed over a period of time.

    The Pod

    Leave a comment:


  • petez69
    replied
    Hi Ultra

    ELK will be releasing new binaries for the M1G in 1-2 weeks. There is a new command being implemented for system troubles, looks interesting.

    If you'd like to PM me with your e-mail, I can send you the latest updated serial document..

    Cheers..Pete

    Leave a comment:

Working...
X