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

MQTT api, preset cycle on and off both send <cy>0</cy> #777

Closed
Skinah opened this issue Mar 16, 2020 · 8 comments
Closed

MQTT api, preset cycle on and off both send <cy>0</cy> #777

Skinah opened this issue Mar 16, 2020 · 8 comments
Labels
bug confirmed The bug is reproducable and confirmed keep This issue will never become stale/closed automatically

Comments

@Skinah
Copy link

Skinah commented Mar 16, 2020

The Http api gives the correct state, however the state does not get published to the MQTT broker.

Cycle on should be
1

instead it stays as

0

@Def3nder
Copy link
Contributor

Hi @Skinah, how did you check this ?

did you send an MQTT message to [DeviceTopic]/v ?
...and the returned XML did included 0 while the User Interface (in the browser) does show the Preset Cycle enabled (and it does cycle the presets) ?

@Skinah
Copy link
Author

Skinah commented Mar 16, 2020

I turn the light on and off with the webpage controls and the status mqtt message that gets sent by wled from the esp8266 does not reflect the state of the control.

If I use the http://ipaddress/win
It shows correctly how I am expecting it to work. The issue is the mqtt does not match what http displays and I only get 0 no matter the state of the control.

I do get the full status messages I have just shortened it to the important part which is 0 never changes via mqtt but it does via http.

@Skinah
Copy link
Author

Skinah commented Mar 16, 2020

Sorry misunderstood. Yes the controls function correctly and the presets cycle like they should. The only issue is the mqtt message does not match what the http api gives and I believe the mqtt is wrong. Because the message does not change it does not get sent which is why I have to use the power switch to get the mqtt message to send.

@Aircoookie
Copy link
Owner

Hmm I believe that the issue could be that MQTT doesn't publish (so the values in MQTT are not updated) when the preset cycle is toggled, just when brightness or color is changed.
The same is likely the case in #776 for the attribute as well. Will look into it, MQTT should be updated if anything in the XML response changes.

@swampdogmash
Copy link

Does sound like this will cause problems for MQTT users like myself. To get the status information into nodered for example for triggering other events. Openhab definitions also work better with MQTT. I'm having similar issues trying to get the MQTT and HTTP feedback loop to work writing my own "version" of what is not even a binding - just item files and rules.

@stale
Copy link

stale bot commented Oct 10, 2020

Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs.
Thank you for using WLED!

@stale stale bot added the stale This issue will be closed soon because of prolonged inactivity label Oct 10, 2020
@Skinah
Copy link
Author

Skinah commented Oct 10, 2020

Still an issue but not for me as I no longer use the mqtt api due to this issue. It effects multiple features of the API.

@stale stale bot removed the stale This issue will be closed soon because of prolonged inactivity label Oct 10, 2020
@Aircoookie Aircoookie added bug confirmed The bug is reproducable and confirmed keep This issue will never become stale/closed automatically labels Oct 12, 2020
@blazoncek
Copy link
Collaborator

Preset cycle has been removed in favour of playlists in 0.12 and above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed The bug is reproducable and confirmed keep This issue will never become stale/closed automatically
Projects
None yet
Development

No branches or pull requests

5 participants