not an issue - continues call of MQTTPublishState() & other improvements

[eldrik]

Hi,

newest release is a great improvement.

Any chance of inoperating the wopr effect from https://github.com/jasperhax0r/wledPixel ?

I have recogniced some things that would be nice

• call MQTTPublishState() when the intensity is changed via the web interface

• call MQTTPublishState() when the workMode is changed via mqtt (actual it only happens while changing intensity and display power)

• display the workMode info when changed via mqtt or web interface etc. (e.g. change from owmWeather to mqttClient = MQTT on the display until the first message arrives)

Kind regards
eldrik

[widapro]

Hi eldrik,
Thanks for the feedback! I have implemented all the functions you requested. Please test them out in the new v3.1 release.

[eldrik]

outstanding!

But there seems to be a little bug.

If I publish from my homeautomation system the following sequence of commands sometimes switching to mqttClient does not display MQTT, instead it displays the 4 first digits (e.g. Auss) and sometimes even the complete first mqtt text message (e.g Aussentemp).

publish wledPixel-EC4C/zone0/workmode mqttClient; publish wledPixel-EC4C/power on; publish wledPixel-EC4C/zone0/text Aussentemp; sleep 5; publish wledPixel-EC4C/zone0/text Racktemp; sleep 5; publish wledPixel-EC4C/zone0/workmode wopr;

Update: the described above happens on my esp32 but I also got an esp8266 there is a slightly different behavior.

It seems there are minimum two bugs

The first:

If something ist published with the retain flag to the zone0/text topic and changing the workmode via web interface to mqttClient the last retained message is displayed twice.

If changing the workmode via mqtt only MQTT is displayed!

The second:

If sending workmode change to mqttClient and a mqtt text message via mqtt without a minimum of sleep 1 between both commands the behavior is reproducable that the text message is displayed instead of MQTT and after that the text is displayed.

[widapro]

Hello eldrik!

Thanks for the detailed bug report. I’ve analyzed the logs and implemented fixes for all the issues you described. Please test the attached beta firmware build:

wledPixel-v3.2-beta_ESP8266.bin.zip
wledPixel-v3.2-beta_ESP32.bin.zip

What has been fixed:

1. Truncated Text (e.g., "Auss"):
Fix: Implemented a smart "Ticker Mode". If a message is wider than the zone, the firmware now automatically forces continuous scrolling (Left Alignment + Scroll Left + No Pause). This ensures the full text is always visible and readable, overriding any static effects that would otherwise cut it off.

2. Double Display / Glitches (Message overlapping "MQTT" status):
Fix: Resolved a race condition where the active animation (e.g., the "MQTT" status label) would latch onto the new text buffer for a split second before the new animation started. The display now explicitly clears before updating the text buffer, ensuring a clean transition without artifacts or double-starts.

3. Missing Messages (Text ignored when switching mode):
Fix: The device now subscribes to text topics unconditionally upon connection. This eliminates the race condition where a text message sent immediately after a "switch mode" command would arrive before the subscription was active. Now, the device is always listening, and the logic simply filters messages based on the active mode.

Please let me know if this resolves the behavior on your end!

[eldrik]

thx for the beta update!

Tested it on my esp8266 and no more truncated text, glitches and missing messages so far!

One thing that bugs me, if changing brightness via web or mqtt in the mqtt topic it is always counted one digit less e.g. changing to 4 is displayed as 3 and 5 as 4 and so on.

And another thing that relates to the ne scrolling text feature, but I think the behaviour is intended and there is no other way.

If the scrolled text is displayed once its gone, so maybe if someone has a 4digit wled and like to display "Outsidetemp -3 Grad" it is scrolled once and without any new message the display is black afterwards, maybe continues repeating of the message until a new one arrives would be an option?

[widapro]

Hi! Thank you for suggesting this new feature. I really appreciate it!

I'm happy to report that I have addressed both of the points you mentioned in the latest beta firmware (v3.2-beta2):

wledPixel-v3.2-beta2_ESP8266.bin.zip
wledPixel-v3.2-beta2_ESP32.bin.zip

1. Brightness Reporting Fixed: I resolved the "off-by-one" error where brightness values were reported via MQTT as one digit less (e.g., 4 displayed as 3). The values should now clearly match between UI and MQTT.

2. New "Infinite Scroll" Feature: Based on your suggestion, I've implemented a new option to control message scrolling behavior. You can now choose whether a message scrolls once or loops indefinitely.
   In Web UI: There is a new checkbox "Infinite Scroll" in the Zone Settings (visible in MQTT Client mode).
   Via MQTT: I added a new topic to control this dynamically: devicePrefix/zoneN/scrollInfinite Send true to enable looping. Send false for single-pass scrolling.

Could you please give this beta version a try and verify if these changes work as expected for you before I go to full release?

[eldrik]

Thanks again.

My findings:

1. Description in web ui states following controltopic that is missing the scrollInfinite under the on/off switch

Control topic prefix: %mqttDevicePrefix%/zone0/*

In the inbuild description on the right it is complete
devicePrefix/zoneN/scrollInfinite - infinite scroll (true/false)

2. The new function works as intended, text is scrolling inifinite and setting is listed in the mqtt state. Changing from true to false scrolling happens just once and the corresponding state scrollInfinite changes in the mqtt state and web ui.

3. The brightness difference is fixed

4. I also recogniced the backup/restore feature and tested it successfuly

5. ScrollInfinite is only available for mqttClient what about long input that is send via manualInput or via the api/message?
   And wouldn't it be nice maybe more intuitive to have scrollInfinite changed via on/off instead of true/false?

6. I tried the different scroll effects and while using the "SPRITE" effect no text is displayed at all.

[widapro]

Hi eldrik,

1. scrollInfinite now supports on/off: I have updated the API so scrollInfinite now accepts true, on, 1 to enable, and false, off, 0 to disable. This consistency applies to both the HTTP API and MQTT.

2. scrollInfinite now works in Manual work mode.

3. Regarding SPRITE: The generic "SPRITE" option was a placeholder. It has been replaced by specific custom effects: PACMAN, MARIO, GHOST, DINO, etc. Please select the specific animation name from the effect list to see them.

Thank you for your feedback!

Please verify this "RC" version before release:

wledPixel-v3.2-rc_ESP8266.bin.zip
wledPixel-v3.2-rc_ESP32.bin.zip

[eldrik]

Thx again.

My findings:

1. scrollInfinite succesfully is en/disabled via true/false, on/off, 1/0 & manualinput mode does also contain scrollInfinite and works

2. on my 4 digit display are two zones 0-2 & 3-3 on zone0 the outside temperature is displayed and on zone1 the weather icons (cloud, fog etc.), zone0 font is cyrillic Character spacing 0 and scroll in effect OPENING_CURSOR both zones are running in mqttClient workmode.
   The text (e.g. -1°C) fits without scrolling but now every 3 to 5 sec the scroll in effect repeats also on manualInput workmode.

[widapro]

Thank you eldrik for help with new features! I fixed Manual zone scroll OUT effect issue and published v3.2 version

[eldrik]

@widapro thx again for the fix!

Unfortunatly in mqttClient workmode text, that fits without scrolling on the display, is still repeated will scrollInfinite enabled.

And another thing, today I used the reset wifi settings to put them in the designated iot network, on the esp8266 resetting and using the AP with a new connect worked without a problem.
On my esp32 the wifi settings were reseted, the esp32 goes into AP Mode but login is not possible cause the standard passwords is wrong, i tried it numeros times, even forget the AP ssid on my iphone but it won't connect, maybe there is a inconsisty with the filesystem or something else?

[widapro]

Hi @eldrik ,
Thanks for the feedback! Please check the release notes for the new version and test it. The changes in the new version should resolve the issue you are experiencing.