widapro / wledPixel

Dot matrix panel management
MIT License
69 stars 12 forks source link

Mqtt Problem #34

Open dbgnu76 opened 1 year ago

dbgnu76 commented 1 year ago

Hello,

Got a strange problem, have been using wled since the beginning. uses mqtt to send info. a week ago it stopped working. the display works as it should, can see ip number and that mqtt mode is activated in the display. I cleared wemos and started over with version 2.5.3b and had to re-enter wifi. but it still doesn't want to show any message, has triple checked that the topic is correct, and has also tried other topics. Anyone have an idea what it could be?

widapro commented 1 year ago

Should be fixed in v2.6 Please check it: https://github.com/widapro/wledPixel/releases/tag/v2.6

dbgnu76 commented 1 year ago

I erased wemos, reinstalled with 2.6, but it didnt help. I can send manual text to display. But when i activate mqtt it goes dark and after 1min it will reboot. At all time i have access to the web configuration and the values are saved as expected.

widapro commented 1 year ago

Could you please share a screenshot of your settings page (Zone settings and MQTT settings)? And please provide more details on how you send messages to display.

  1. What software do you use for it?
  2. What message do you send?
  3. What topic do you use to send messages?

This information will help me to reproduce the issue you faced with.

dbgnu76 commented 1 year ago

i am using nodered, i have also tryed with Android Mqtt client , with different topics.

the message is some temp and a live clock and other infos.

i have been using it for about 2 years without problems, i think it all started after an power out.

mqtt1 mqtt2 wled1 wled2

widapro commented 1 year ago

Could you please run MQTT Explorer, connect to your MQTT broker (192.168.1.243) and perform a search for your topic, and check that NodRed is sending messages to the topic which is wled listen (wled/zone0_text)? See my screenshot of how it should look.

Screen Shot 2023-09-20 at 21 46 18
dbgnu76 commented 1 year ago

Iknow it does, that is why i use android mqtt client to watch, i can also send directly from android client to that topic, i have also tryed change topic and only use android client. I have serveal mqtt different topic around the house so i know what i am doing ;) my whole house is automation controlled. I also use Ikea with mqtt, Zwave and shelly with Hass and a siemens plc that is controlling Alarm system and other things.

dbgnu76 commented 1 year ago

Update,

i connected wemos to arduino serialmonitor, and then i can see that it receive mqtt message, but nothing is showing in display. and after 1 min it reboots.

serialplotter

widapro commented 1 year ago

I was unable to reproduce the problem myself. Analyzing your data, I assumed that you send text to the display very often, every second, and in the zone settings there is a pause of 3 seconds + time for scrolling the incoming effect. When I send several messages before the first message finishes displaying (pause time + effect time), then one of the messages is lost and only the last one is displayed.

Screen Shot 2023-09-22 at 11 29 07

Please check the Display settings just in case, maybe something happened and zone0 does not have module numbers configured.

More guesses, is MQTT only used by one zone? what workMode do other zones have?

dbgnu76 commented 1 year ago

Yes, thats true every second i send a message.

But in this case i doesnt matter, because i have tryed to change topic to other, without disruption. and then i manual send 1 message to that new topic, but it wont show !

it is very strange !

widapro commented 1 year ago

Got it. What about Display settings in top of setting page? Could you please share this too. And what workMode are using in other zones?

dbgnu76 commented 1 year ago

1 2 3 4 5

Grey-Lancaster commented 1 year ago

Should these not match?

image

This works for me

image

widapro commented 1 year ago

Should these not match?

No, it doesn't have to match.

dbgnu76 commented 11 months ago

I don't know what the error was, but I started a new mqtt broker and now it works, I had to transfer all the other data to the new one because I don't want 2 mqtt brokers.