Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maximum number of scenes/effects? #236

Closed
fuzzydunlop1976 opened this issue Jul 9, 2024 · 1 comment
Closed

Maximum number of scenes/effects? #236

fuzzydunlop1976 opened this issue Jul 9, 2024 · 1 comment

Comments

@fuzzydunlop1976
Copy link

Govee Device SKU

H6078

Govee2MQTT Version

2024.04.29-30cf7732

Describe the issue

Does the add on have a hard limit of how many scenes (or specifically DIY scenes) it imports/supports? The last 40 are listed and are controllable, but before this, they do not appear. They are useable and visible in the Govee app but not via the add on. When I try to set an effect not listed via an automation, the log shows the error ‘not available for this device’.

From testing, I’m getting an issue after 40 DIY scenes. The 41st oldest scene is never visible free the add on has been restarted. Wondering if this is a hard limit set or part of the Govee api? If anyway to raise or remove it would be appreciated here if possible.

Startup Diagnostics

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=192.168.1.94
GOVEE_TEMPERATURE_SCALE=C
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-07-09T18:52:00 INFO govee::commands::serve] Starting service. version 2024.04.29-30cf7732
[2024-07-09T18:52:00 INFO govee::commands::serve] Querying platform API for device list
[2024-07-09T18:52:02 INFO govee::commands::serve] Querying undocumented API for device + room list
[2024-07-09T18:52:04 INFO govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-07-09T18:52:04 INFO govee::commands::serve] Starting LAN discovery
[2024-07-09T18:52:04 INFO govee::commands::serve] Waiting 10 seconds for LAN API discovery
[2024-07-09T18:52:04 INFO govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.

Additional Logs

No response

Home Assistant Logs

2024-07-09T18:55:22 ERROR govee::service::hass] While dispatching Message { topic: "gv2mqtt/light/E143C6383032245D/command", payload: "{"state":"ON","effect":"GHS Fire"}", qos: AtMostOnce, retain: false, mid: 0 }: mqtt_light_command: state.device_set_scene: Scene 'GHS Fire' is not available for this device
[2024-07-09T18:55:22 INFO govee::service::hass] Command for Cylinder Floor Lamp (E1:43:C6:38:30:32:24:5D H6078): {"state":"ON","effect":"GHS Fire"}
[2024-07-09T18:55:22 INFO govee::service::state] Using Platform API to set Cylinder Floor Lamp (E1:43:C6:38:30:32:24:5D H6078) to scene GHS Fire
[2024-07-09T18:55:22 ERROR govee::service::hass] While dispatching Message { topic: "gv2mqtt/light/E143C6383032245D/command", payload: "{"state":"ON","effect":"GHS Fire"}", qos: AtMostOnce, retain: false, mid: 0 }: mqtt_light_command: state.device_set_scene: Scene 'GHS Fire' is not available for this device

Anything else?

No response

@wez
Copy link
Owner

wez commented Jul 13, 2024

There's no inherent limit in govee2mqtt, but we can only return what the various govee apis are returning to us

@wez wez closed this as completed Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants