When a SCRIBE device is discovered via libhdhomerun, what will the device type be set to? Will it be detected as HDHOMERUN_DEVICE_TYPE_TUNER or HDHOMERUN_DEVICE_TYPE_STORAGE?
I'm retooling my project to not care about what the type of device is and use things like the presence/absence of Lineup URLs and/or Storage URLs to decide what the capabilities are, but this particular flag would still be good to understand what to expect for a SCRIBE.
I also assume that SERVIO will always be HDHOMERUN_DEVICE_TYPE_STORAGE based on end user experiences already, but if that's incorrect I would appreciate being corrected
Want to write your own code to work with a HDHomeRun or work with the HDHomeRun DVR? We are happy to help with concepts, APIs, best practices.
6 posts • Page 1 of 1
- Posts: 1209
- Joined: Wed Oct 01, 2008 8:46 pm
- Device ID: 131EB7F7;131ED0E0
- Location: Elkridge, MD USA
Thank you Nick, I very much appreciate the quick response.
Follow-up question based on changes I've already made guessing how to deal with this ... will the HDHOMERUN_TAG_BASE_URL for both of these responses be the same with a SCRIBE? I changed things around to use the presence of "LineupURL" and/or "StorageURL" in the JSON discovery data to determine if the device has tuner(s) and/or storage available, but I think based on this information a SCRIBE user would end up with duplicate entries for a single device this way. I can de-duplicate on the base URL, if that's how SCRIBE works.
I guess I'm asking if a SCRIBE shows up as two devices everywhere (my.hdhomerun.com/discover and libhdhomerun), or if it will be collapsed into a single device instance in the discovery JSON and just have both sets of attributes.