Bump qs and node-hue-api

[dependabot]

Removes qs. It's no longer used after updating ancestor dependency node-hue-api. These dependencies need to be updated together.

Removes qs

Updates node-hue-api from 1.2.1 to 5.0.0-beta.14

Release notes

Sourced from node-hue-api's releases.

v4.0.8

Fixes issues with TypeScript definitions on the model objects.

4.0.1

• fixes/improvements in TypeScript definitions
• removal of an invalid character in source code of the remote API Issue #155

4.0.0

• Deprecated v2 API and shim and modules removed from library

• Introduced rate limiting in the Light and Group set States to be compliant with the Hue API documentation best practices. This only has an impact on this library, so it may be possible if you are running other software on your network accessing the Bridge, you will still able to overload it.

  • The whole API is currently limited to 12 requests per second by default (currently not configurable)
  • lights.setLightState() is limited to 10 requests per second
  • groups.setState() is limited to 1 request per second

• v3.discovery.nupnp() Now returns a different payload as it no longer accesses the XML Discovery endpoint to return the bridge data as this can become unreliable when the bridge is overloaded. See the documentation for specifics.

• v3.api removed the create function as it was deprecated, use createRemote() fro the remote API, createLocal() for the local API or createInsecureLocal() for non-hue bridges that do not support https connections

• v3.Scene has been removed, use the following functions to create a new Scene instance:

  • v3.model.createLightScene()
  • v3.model.createGroupScene()

  This change has also allowed for the separation of the attributes and getter/setters locked down properly based on the type of Scene, i.e. Cannot change the lights in a GroupScene (as they are controlled by the Group).

• v3.sensors has been removed, use v3.model.createCLIPxxx() functions instead

• v3.rules has been moved into v3.model

  • To create a Rule use v3.model.createRule()
  • To create a RuleCondition use v3.model.ruleConditions.[group|sensor]
  • To create a RuleAction use v3.model.ruleActions.[light|group|sensor|scene]

• v3.model added to support exposing the underlying model objects that represent bridge objects. This module will allow you to create all of the necessary objects, e.g. createGroupScene()

• Capabilities API:

  • capabilities.getAll() now returns a Capabilities object

• Groups API:

  • The following API functions will accept a Light Object as the id parameter as well as an integer value:
    • groups.get(id)
    • groups.getGroup(id)
    • deleteGroup(id)
    • enableStreaming(id)

... (truncated)

Changelog

Sourced from node-hue-api's changelog.

Change Log

5.0.0-beta.13

• Fixing problem with timeouts not being applied from the agent #212

5.0.0-beta.11

• Fixing swapped default rate limits for groups and lights as reported in #196

5.0.0-beta.10

• Fixes #208 issues with discovery.meethue.com CA cert chain changes

5.0.0-beta.4

• More fixes associated with OAuth2 remote endpoint changes fixing new error from #201

5.0.0-beta.3

• Fixes #201 a content type header being added twice for refreshing of tokens

5.0.0-alpha.1

• Providing a fix for the discovery portal (N-UPnP search) issues where a user has multiple bridges, where some of them are invalid. This changes the return value for discovery requiring a major version bump. Issue #168.

4.0.8

• Fixes problems in TypeScript definitions for the model, Issue #181

4.0.7

• Fixes typo in bridge software update configuration choices, Issue #170.

4.0.6

• Same as 4.0.5 due to merge error on my part

4.0.5

• Various TypeScript definition fixes including Issue #166.

4.0.4

• Fixing UPnP lookup results failures, Issue #162.

4.0.3

• TypeScript definition updates

4.0.2

• Fixing TypeScript definition return types for Groups API, Issue #157
• Adding another Rule status looperror to Rule status options, Issue #158

4.0.1

• fixes/improvements in TypeScript definitions
• removal of an invalid character in source code of the remote API Issue #155

4.0.0

• Deprecated v2 API and shim and modules removed from library

... (truncated)

Commits

• 081da83 5.0.0-beta.14
• d54b973 Adding mDNS discovery and removing UPnP as it is no longer available. Fixes #221
• 1103393 Updating changelog
• a3619e1 5.0.0-beta.13
• 8ab7a4a Changes from #211, fixing links in docs
• 7066ebe Fixes #217 incorrect object key used
• bd9875c Fixing issues in the handling of timeouts as the agent does not appear to be ...
• edce6e0 Updating the model to support new classes introduced from iOS application usi...
• 3ffa39c 5.0.0-beta.12
• 9ebc945 Fixing node-fetch security vulnerability GHSA-r683-j2x4-v87g
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.