<Category_Num> and <SubCategory_Num>

Plugins & Plugin Development General Plugin Discussion
#1

Starting with firmware 1.5.308 the device category and subcategory can be specified in the device file. This has been added especially for the alarm panel plugins. Previously the device category was set based on the device type, but this didn’t work for the alarm panels, because each plugin has a different device type.

Both tags are optional.

The devices categories are listed here: http://wiki.micasaverde.com/index.php/Luup_UPNP_Files#Device_Categories

I updated the wiki with this info:
http://wiki.micasaverde.com/index.php/UI4_UI5_Migration#New_device_file_tags

#2

Thanks for getting these added.

A quick question on consistency. It looks like the existing tags are all camelCase, but the new tags have a different style.

eg. existing [tt], , , , , etc[/tt]
eg. new [tt]<Cagegory_Num>, <SubCategory_Num>[/tt]

even the prior MiOS-specific ones, like [tt][/tt], were using the original conventions.

Was there a reason for making them different this time around?

#3

@guessed

Good question. I asked Aaron about this myself and here is his answer:

#4

Which specific UPnP spec/section is being referred to?

I checked the following, and there is no reference to Category_Num in the Device descriptor:
Section 2.3 - http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf

actually, there’s only one reference to “category” at all in that UPnP Standards document.

#5

Yeah, I noticed this. Maybe he had his reasons when he introduced these tags like this in UI2.

#6

Nice addition as i will help with 3rd party apps to figure out what type of devices these are. Only issue now is making sure of the proper service tag. I wish that would be added to the lu_sdata.

  • Garrett
#7

Ok, I’ll just do it in code until these are normalized. I don’t ever recall these being exposed anywhere before, let alone documented… so not sure where the UI2 reference is coming from.

What we enter, in a standard UPnP Device Descriptor file, doesn’t have to be the exact tag emitted in a JSON or whatever… that’s what Code is for :wink: