MQTT won't start after update: "MQTT Update check failed"

[maxnorth]

I had explored this somewhat in a previous thread: 

 

There are a couple of paths listed in there that might be helpful.

 

[EWhite]

3 hours ago, sjenkins said:

@EWhite appreciate the feedback ; couple questions:

1.  just to be clear, did you delete back to root on the topics?

2. you mentioned everything else is working.  Above here you said everything was not sending status.  Is that a change with this or were the other devices working.  

thanks

yes.. i did delete back to root.

i was mistaken on that, i had a device error, once fixed it was reporting.(temperature on a wemos)

so as it stands...switches are still not reporting, but everything else seems to be working as expected.

[maxnorth]

Ok, I've had a chance to test the MQTT Explorer solution:

1. Delete MQTT nodeserver

2. Using MQTT Explorer, delete all in tele, tasmota and stat folders (not $SYS).

3. Reinstall MQTT in same slot

Result: Status of all devices IS now updating in AC. This includes switches and temp sensors in my case. (Good work, guys!)

Can confirm: These devices are available in AC programs as "Control" but not "Status." 

Perhaps unrelated, but adding to radar: My sole "type:s31" device is not available as either Control or Status, so is unusable in programs. See this earlier thread, which received no response: 

 

[maxnorth]

I should have said that the temp sensors ARE available as Status in programs.  If a temp changes, I can detect it. Not true for switches.

[TriLife]

Good morning @maxnorth, @EWhite. @TJF1960, @sjenkins

As mentioned earlier, I was able to reproduce the error on two different eISYs here. (We have not yet identified the root cause)

I also was able to revert back to V35 and confirm that at least on these two eISYs it works as intended, updating status when it changes.

Now, we have a choice:

A- V35 is available  on the beta store under 'MQTT' (NOT 'mqtt-poly'!).

If you chose to go there your functionality should return. But you will habe to delete the contents of your slot and reinstall from beta.

or

B- I can put V35 on the Production store and you should get an 'Update Available' in PG3. It will automatically install in your slot, no reconfiguration necessary.

My preference is for B, since there are likely users out there, who are not necessarily monitoring the forum... 

PLEASE LET ME KNOW!

If I don't hear from you, I'll back-rev the Production Store.

@maxnorth: Sorry I didn't see your post about the s31. I don't have one of those to troubleshoot. I'm about to embark on a multi week overseas trip without access to a computer. I'll make a note to reach out to you upon my return.

 

Edited April 25 by TriLife
added missing information

[TJF1960]

Hello @TriLife,

I agree with you, version B, back-rev on production.

edit: I did try non-prodction but the AC page for all of the devices didn't load all the way, tried numerous closings and openings and reboots. I meant to take a snapshot but forgot. Attached is after reverting back to production. Everything in the red circles was all squished down and the three buttons on the bottom were not visible.

Thank you for working on this before your big trip, its the last thing you wanted to do I am sure what with getting ready. Safe journeys!

-Tim

 

Edited April 25 by TJF1960

[EWhite]

i agree with B  hehe

 

[sjenkins]

So there is a new version up 0.0.39

Want to explain the issue & why it sometimes worked for some things.

Seems it was a timing error which raised its head as we went to the new plugin template

The new template is much more asynchronous than the previous which was much more script

Its why you have to restart the plugin every time you change a parameter (for a future fix)

Basically the plugin does the mqtt.subscribe on connect to the mqtt server.

unfortunately discover is handled from the parameter side of things

So a "wait for me" flag was required here.

So sorry everyone, but this one was a hard one to debug as I never saw the issue & my test file of 160 nodes does not have devices updating to it.

Please let us know here if it worked for you!

Edited April 25 by sjenkins

[TriLife]

Good morning everyone: @EWhite, @TJF1960, @maxnorth

@sjenkins did a stellar job hunting down the bug overnight. Thanks!

So, we decided on Option C :

The production store now has V39 on it, which should fix the issues you have been experiencing. It did so on both my eISYs.

A simple UPDATE in your plug-in will get you up to date.

Sorry for putting you through this.

I also managed to 'follow' the MQTT thread in the forum, so you don't have to mention me for me to get a message.

There is an updated link in the CONFIGURATION for future comments. Keep them coming!

Cheers.

Edited April 25 by TriLife
added missing information

[maxnorth]

My store still shows 0.37

[EWhite]

YES!!!!!

that fixed it.. all is working as expected i do believe...

Thank you much!

[maxnorth]

Never mind. Refreshed the store and did the update to .39.  All devices update and work fine.  Switches "Status" still not available in programs.

[maxnorth]

BTW, I noticed an odd entry in the configuration help text:

""status_topic": For switch this will be the cmnd topic (like cmnd/sonoff1/power)"

I believe that should say "For switch this will be stat/sonoff1/POWER"

At least that's the way my devlist is structured.

[TriLife]

7 minutes ago, maxnorth said:

BTW, I noticed an odd entry in the configuration help text:

""status_topic": For switch this will be the cmnd topic (like cmnd/sonoff1/power)"

I believe that should say "For switch this will be stat/sonoff1/POWER"

At least that's the way my devlist is structured.

good catch @maxnorth,

the correct format is in the lines above "status_topic": "stat/sonoff1/POWER", "cmd_topic": "cmnd/sonoff1/power"}

[sjenkins]

9 minutes ago, maxnorth said:

BTW, I noticed an odd entry in the configuration help text:

""status_topic": For switch this will be the cmnd topic (like cmnd/sonoff1/power)"

I believe that should say "For switch this will be stat/sonoff1/POWER"

At least that's the way my devlist is structured.

@maxnorth we are compiling a list of errors / improvements for this plugin, like above.

For today can we verify that everyone is up and going?

I will start a "suggestions" topic thread for items like the s31 fix, typos like above, & perhaps @TriLife & I will share our list.  Together we can prioritise !!!

[TriLife]

21 minutes ago, EWhite said:

YES!!!!!

that fixed it.. all is working as expected i do believe...

Thank you much!

I wanna know, if your chickens are happy! 😄

[sjenkins]

21 minutes ago, maxnorth said:

BTW, I noticed an odd entry in the configuration help text:

""status_topic": For switch this will be the cmnd topic (like cmnd/sonoff1/power)"

I believe that should say "For switch this will be stat/sonoff1/POWER"

At least that's the way my devlist is structured.

@maxnorth I can confirm that only control works and not status on switches.

I tended to only use control in my programs ; can you confirm, is this new or an old issue?

thanks

 

Edited April 25 by sjenkins

[maxnorth]

7 minutes ago, sjenkins said:

@maxnorth confirm that only control works and not status on switches.

I tended to only use control in my programs ; can you confirm, is this new or an old issue?

thanks

 

I can confirm the all switches appear in the "Control" dropdown in programs, and sensors do not (as expected). In "Status" dropdown, only sensors appear and no switches.  Honestly, I don't know if this is new.  I also tend to use only Control for my switches.  If I really needed to know status, I could always use a variable that would toggle as Control was toggled.

[sjenkins]

@maxnorth appreciate knowing if it was new. Shouldn’t be as nothing was changed in that area of the program, but. 
 

we certainly can add the above to the list. Shouldn’t be a big deal. 
 

my next stop is to start the thread on bugs and suggestions. 

[TJF1960]

Hi @sjenkins, Switch status not showing up in dropdown programs is new as of .37

Many of my programs use Sonoff status in order to work and control things.

-Tim

Edited April 25 by TJF1960

[EWhite]

2 hours ago, TriLife said:

I wanna know, if your chickens are happy! 😄

yeppers!

😁

[sjenkins]

12 minutes ago, TJF1960 said:

Hi @sjenkins, Switch status not showing up in dropdown programs is new as of .37

Many of my programs use Sonoff status in order to work and control things.

-Tim

Thanks Tim,  let me take a look at it tonight.

 

[maxnorth]

I am interested in converting from a dev list to a dev file. Can one of you file users post a snippet so I can get the proper format?  Also, where do you store it?

[TriLife]

2 hours ago, maxnorth said:

I am interested in converting from a dev list to a dev file. Can one of you file users post a snippet so I can get the proper format?  Also, where do you store it?

devices:
# SAMPLE SECTION
- id: "Test1"
  name: "Friendly Test1"
  type: "switch"
  status_topic: "stat/Test1/POWER"
  cmd_topic: "cmnd/Test1/power"

# TOPIC in Sonoff Quad MQTT CONFIG "Test4CH" Note no CH# and no UNDERSCORE !
- id: "Test4CH1"
  name: "Friendly 4CH1"
  type: "switch"
  status_topic: "stat/Test4CH/POWER1"
  cmd_topic: "cmnd/Test4CH/power1"
- id: "Test4CH2"
  name: "Friendly 4CH2"
  type: "switch"
  status_topic: "stat/Test4CH/POWER2"
  cmd_topic: "cmnd/Test4CH/power2"
- id: "Test4CH3"
  name: "Friendly 4CH3"
  type: "switch"
  status_topic: "stat/Test4CH/POWER3"
  cmd_topic: "cmnd/Test4CH/power3"  
- id: "Test4CH4"
  name: "Friendly 4CH4"
  type: "switch"
  status_topic: "stat/Test4CH/POWER4"
  cmd_topic: "cmnd/Test4CH/power4"

# Hallway Box (IP x.20...)
- id: "OfcBath" #{1:"Orientes", 2:"Interior", 3:"Sky", 4:""}
  name: "Office Bath"
  type: "switch"
  status_topic: "stat/OfcBath/POWER"
  cmd_topic: "cmnd/OfcBath/power"

there you go. 

devices:

is critical. every '-' starts a new device.

I keep my file in /usr/home/admin/<file-name>.yaml

May I suggest we move the conversation over to this 

 for suggestions and general questions?

Thanks

Edited April 25 by TriLife
added missing information

[maxnorth]

Perfect, thanks. Feel free to move it.  Not sure how.