I see on the Downloads page that there is a downloadable version of the various point tags for specific equipment. Is there anywhere where these can be downloaded as a complete list? The use case I have is to keep libraries updated in field devices. It would be nice to have a complete list instead of having to know the specific equipment types that have been created. This would enable us to future-proof our product and ensure we always have the latest and greatest tag sets. Any thoughts?

Hi Shawn, what exactly are your thoughts about what a "complete list" would entail? Do you mean combining everything in that list with the text documentation too?

While having complete documentation would be nice, that was not what I had in mind. I was thinking something simpler that would simply combine the current equip points lists into one. Doing this would enable us to keep definitions up to date when new equipment types are added without having to modify our code with new URIs. The intent is to have self updating tag libraries in our system. Something like below would be a simple implementation, but I would certainly be open to a more thorough model which includes documentation of the tags if the community felt there was a need.

[[ahu]]
**Discharge**
discharge air temp sensor
discharge air humidity sensor
...

**Return**
return air temp sensor
return air humidity sensor
...

[[chiller]]
** Run/Status **
run cmd
run sensor
...

**Chilled water to/from AHUs**
chilled water leaving temp sensor
chilled water leaving temp sp
...

Yes we definitely need something like that. I'm actually thinking we should make this server a Haystack server and have some ops for querying tags, docs, etc.

That sounds like a great idea. Let me know if there is anything I can do to help.

Since I know you have more important things to do than work on this, is there any chance of providing a directory listing at http://project-haystack.org/download/equip-points/ so we can at least have some programatic way of keeping all the equipment lists up to date?

We already have something pretty close to what I think you want such as /download/equip-points/ahu. What specific enhancements would you like to see? Maybe combine them all into one file?

I requested previously that we put them all into one file. However, since that has yet to happen, a good stop gap measure would be to expose the /download/equip-points/ directory as a listing of available equipment. That way a program could iterate through the available equip types and rebuild its internal lists.

Ok, we are on same page. This is still on my todo list for next time I'm in that code enhancing the export stuff.

In the meantime, now that its all open source, its pretty easy to generate yourself a file from source. The key code is in Html:

typeof.pod.files.findAll |f| { f.pathStr.startsWith("/equips/") }.sort.each |f|
{
  out.li.a(`/download/equip-points/${f.basename}`).w(f.basename).aEnd
}

That works if you're using SkySpark. In the meantime, I will simply parse the /download/ HTML for HREFs starting with "/download/equip-points/". Thank you.