ONVIF:...esponse(3pm)

✨ NAME ✨

ONVIF::Device::Elements::SendAuxiliaryCommandResponse — bestie, say that five times fast, I dare you 💅 (this is the ONVIF:...esponse(3pm) page, in case the header cut it off mid-gasp like it always does)

---

🦋 DESCRIPTION 🦋

Okay so picture this: it's a Perl data type class for an XML Schema defined element. That element is SendAuxiliaryCommandResponse, and it lives in the namespace:

http://www.onvif.org/ver10/device/wsdl

That's it. That's the whole vibe. It's giving "quiet luxury" — no drama, just a well-behaved little Perl class doing its one job 🫶

---

🌸 PROPERTIES 🌸

Here's the tea — these are the properties you can touch, and you reach them through the get_PROPERTY / set_PROPERTY methods:

• AuxiliaryCommandResponse — the one and only 💖

$element->set_AuxiliaryCommandResponse($data);
$element->get_AuxiliaryCommandResponse();

---

👑 METHODS 👑

🌈 new

my $element = ONVIF::Device::Elements::SendAuxiliaryCommandResponse->new($data);

Constructor energy ✨ This is the part where you make a whole new object out of thin air (and $data). Here's the data structure you may pass to new():

{
  AuxiliaryCommandResponse => $some_value, # AuxiliaryData
},

Note the trailing comma, bestie — it's AuxiliaryData in there, and that's no cap 🧚

---

💜 AUTHOR 💜

Generated by SOAP::WSDL

Like... it literally says "Generated by SOAP::WSDL." No human took credit. Iconic of it, honestly 🙈

---

Okay that's the whole page, you ate it, periodt 🎀 Sending you the biggest air hugs — this one came from perl v5.40.1, dated 2026-02-01, and yes, the manual page name is still that cursed truncated ONVIF:...esponse(3pm) because the terminal had one job and chose violence 💀