Scripting Help

[jlemley]

Hi,

I'm trying to log the value of some Zigbee temperature and humidiy sensors in the HS4 log via the &nhs.writelog command. I've got it working fine referencing the values with hs.devicevalue:






But if I use hs.devicevaluebyname (which would be my preference), then I always get a value of -1:





I've tried multiple iterations of the device name, but always get the same results. I believe this is a problem with the device name I'm using since I get the same -1 result even if I use garbage for the device name. Hoping someone can point out what I'm doing wrong.

[jon00]

I tried it and could not get it to work with any HS4 created devices. Most probably linked to the parent/feature relationship changes in HS4.

It does still work fine with HS3 created devices (in HS4) but not surprising as it is a HS3 scripting function.

There is not an equivalent HS4 function I can see either...

[ewkearns]

tenholde, don't you use "name" a lot? Have you noticed this?

[tenholde]

I prefer to use a device/feature name as that is less likely to change than the device ref (which screws up existing events). You can use GetFeatureRefByFullname to get the devref and then use hs.DeviceValue. See the link below for more information:


https://tenholder.net/tenWare2/Scrip...eRefByFullname

[jlemley]

tenholde said:

I prefer to use a device/feature name as that is less likely to change than the device ref (which screws up existing events).

My thoughts exactly.

I understand what you're suggesting as a solution, but I was hoping to accomplish this as a one line immediate script command in order to keep it simple.

Is there some place that lists all the Homeseer script commands and functions? I've searched through the documentation and cant seem to find this.

[ewkearns]

Well, there is this: http://help.homeseer.com/help/HS3/static/

However, it is for HS3 scripting, is incomplete, has errors, and is sorely lacking in examples, but it is all HST has given us to work with. Probably the best approach is to engage in self-help as far as possible, using the documents available, then get the brain trust available, here, to help sort your attempt out.

[pseudocode]

To find the device by name it uses the following case-insensitive checks, iterating over all devices and stopping on the first match - and treating devices and features the same:

Entered string =
Location + " " + Name AND Location <> ""
OR Location2 + " " + Name AND Location2 <> ""
OR Location + " " + Location2 + " " + Name
OR Location2 + " " + Location + " " + Name
OR Name

So in your case you'd want to look for "Zigbee Dining Room Humidity" for maximum accuracy.

[pseudocode]

For the actual scripting, attached is a dump of all the public members of hsapplication - some of the new ones may be obvious, but without proper documentation it would be trial-and-error.

HS4 scripting.txt

The plugin documentation https://homeseer.github.io/Plugin-SD...tml?vb#methods has a lot of overlap, so some of that helps.

For example, a nice new method which simplifies CAPI control is SendControlForFeatureByValue

[tenholde]

tenGlobalMethods.GetFeatureRefByFullname has been updated to include an optional parameter FeatureNameOnly. If set to True, then the Featurename parameter should only be the Name without Location and Location2.

https://tenholder.net/tenWare2/Scrip...tallation.aspx

See documentation at: https://tenholder.net/tenWare2/Scrip...eRefByFullname

Or if you use tenScripting: https://tenholder.net/tenWare2/tenSc...tallation.aspx