maxnorth Posted April 23 Share Posted April 23 Just updated my eisy using "Upgrade Packages." My other node servers are working fine, but MQTT is not. It does not start. When you click on Start, Stop or Restart, it displays a red error message that "Update check failed" and it does not start. I don't know what that is, but it seems odd that a failed update check would prevent the existing version from starting. I'm on IOX 5.8.0, PG 3.2.22, and MQTT 0.0.35. Quote Link to comment
maxnorth Posted April 23 Author Share Posted April 23 A clue from the PG log file: "error: updateNs: Node server MQTT has no store entry in Production." But MQTT does appear in the plugin store. Quote Link to comment
maxnorth Posted April 23 Author Share Posted April 23 I reinstalled 0.0.37 from the store and now it starts fine. I can control all devices fine. But the status of the devices no longer updates in the AC. Quote Link to comment
sjenkins Posted April 23 Share Posted April 23 I think this may be with the latest PG3 update & name changes. With the updates that @TriLife and I made I think the number which goes along with the plugin may have finally changed from the old xKing version of MQTT. I had to do the same, delete and reinstall, but didn't think anything of it. Quote Link to comment
EWhite Posted April 23 Share Posted April 23 1 hour ago, maxnorth said: I reinstalled 0.0.37 from the store and now it starts fine. I can control all devices fine. But the status of the devices no longer updates in the AC. after going back and looking.. i am in the same boat...no updates in AC... Quote Link to comment
TriLife Posted April 23 Share Posted April 23 I just checked bot my eISYs. Both report status on AC... Both are 3.2.22/5.8.0. Let's see what @sjenkins reports back Quote Link to comment
maxnorth Posted April 23 Author Share Posted April 23 I just tried again: delete and reinstall the nodeserver (0.0.37) in the same slot. No change. I can control the devices but the status in the AC does not update. For what it's worth, I am using a devlist, not a devfile. I made no changes since the prior version, which was working. Quote Link to comment
EWhite Posted April 23 Share Posted April 23 1 minute ago, maxnorth said: I just tried again: delete and reinstall the nodeserver (0.0.37) in the same slot. No change. I can control the devices but the status in the AC does not update. For what it's worth, I am using a devlist, not a devfile. I made no changes since the prior version, which was working. same.. Quote Link to comment
TriLife Posted April 23 Share Posted April 23 (edited) Are you also deleting the nodes that were created? That sometimes causes problems. Go into PG3x, MQTT plug in DETAILS, then click on nodes. You should be able to delete all nodes except the controller node. Then do a stop/start to force the plugin to install them all. As an aside, after that restart, please observe the bottom right of the screen for a Red warning like " Error processing message from Xxxx die to high volume. Normally this should not pop up, unless you have in excess of 50-80 mqtt nodes to add. Thanks Edited April 23 by TriLife Typos Quote Link to comment
sjenkins Posted April 23 Share Posted April 23 Hey guys, can I get some data from you. As you heard both @TriLife & I are getting status' , also I think I am hearing that some of you are getting mixed results with some working and some not. Is the only device affected the switches? could @EWhite , @maxnorth attach debug level logs? Please point out which are working and which not please. Has anyone done a reboot of their EISY? Because of the variance of experience I am wondering on that too. We should be able to figure this out before too long. Sorry for the inconvenience. Quote Link to comment
maxnorth Posted April 23 Author Share Posted April 23 None of mine are updating, including switches and temp sensors. I have rebooted eisy several times in the process, both before and after the reinstall. MQTT debug log attached. I MQTT_4-23-2024_21205_PM.zip Quote Link to comment
EWhite Posted April 23 Share Posted April 23 same.. its everything... MQTT_4-23-2024_23112_PM.zip Quote Link to comment
EWhite Posted April 23 Share Posted April 23 ive deleted everything, rebooted several times.. reinstalled, re-found...etc...everything works but reporting. Quote Link to comment
TJF1960 Posted April 24 Share Posted April 24 Hello @sjenkins, I was having the IOX status issue as well, in another thread: Just sent you a pm with log. Thank you! -Tim Quote Link to comment
sjenkins Posted April 24 Share Posted April 24 (edited) As this is happening to some and not others, as well happening to some switches and not others I am coming to conclusion that this is to do with the gen.mosquitto server and its persistence. This survives reboot & deletion of an individual plugin. As well as restart of the mosquitto server. I guess that is why they call it persistence. My theory as we all had to delete and install rather than upgrade with the name/author change on this plugin due to the different serial number associated with it, I am thinking that mqtt topics have been corrupted as some things have changed. For those who have an MQTT Explorer on their Mac or the equivalent on Windows, you can get to it your server. This is at the ip of your EISY and the port number 1884 You will find your topics there. Delete back to the ROOT one or all of your switches. You may need to restart the plugin. Your only loss here will be the current status of your devices. ** for those who don't know what I am talking about, wait a few hours until we get some answers from a few users If we prove this out with a number of users, we will find a more elegant way to do this for all users. I may need some help from @bmercier as I don't think we can expect all users doing this. Basically the mosquitto.db needs to be deleted while the service is stopped on the gen.mosquitto.ud server. Edited April 24 by sjenkins 1 Quote Link to comment
TJF1960 Posted April 24 Share Posted April 24 Hello @sjenkins and @TriLife, Success! I deleted each switch, then deleted the ns. Opened MQTT Explorer, deleted all files I could. Reinstalled ns and configured. All switch status now reports in AC. You guys ROCK! Thank you so much! -Tim 1 Quote Link to comment
maxnorth Posted April 24 Author Share Posted April 24 I'm up on MQTT Explorer, but not sure what exactly needs to be deleted. See screenshot Quote Link to comment
TJF1960 Posted April 24 Share Posted April 24 I am no expert, this was the first time using explorer so use at your own risk. It worked for me but I may just have been lucky. I deleted everything under "tele" and "tasmota" and 'stat" if I remember correctly. I then installed the ns and configured and it worked. However there is another problem that I found before doing this. In the condition of programs the switches show up under Control but not Status. So you cannot monitor status of a switch in program. Now I don't know if it is just me or if everyone will is affected. This problem presented after upgrading to .37 and unfortunately didn't change after deleting the files in gen.mosquitto. Maybe you can confirm the loss of status in program conditions. -Tim Quote Link to comment
sjenkins Posted April 24 Share Posted April 24 (edited) 15 minutes ago, TJF1960 said: I am no expert, this was the first time using explorer so use at your own risk. It worked for me but I may just have been lucky. I deleted everything under "tele" and "tasmota" and 'stat" if I remember correctly. I then installed the ns and configured and it worked. However there is another problem that I found before doing this. In the condition of programs the switches show up under Control but not Status. So you cannot monitor status of a switch in program. Now I don't know if it is just me or if everyone will is affected. This problem presented after upgrading to .37 and unfortunately didn't change after deleting the files in gen.mosquitto. Maybe you can confirm the loss of status in program conditions. -Tim per @TJF1960 I would delete all under tele, tasmota, and stat. Do NOT delete $SYS I agree this is NOT the way I would prefer to be sending regular users to. At this point it is outside our plugin and better than sending people into SSH ing into the EISY and deleting files. The program status/control problem he brings up sounds like a profile file issue which is more in my bailiwick to fix. I can get to it tonight after work. Edited April 24 by sjenkins 1 Quote Link to comment
EWhite Posted April 24 Share Posted April 24 ok.. ive deleted everything...started over...still no dice on switches. i think everything else is working tho, just switches still not reporting. Quote Link to comment
sjenkins Posted April 24 Share Posted April 24 @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 Quote Link to comment
maxnorth Posted April 24 Author Share Posted April 24 I won't be able to test the MQTT Explorer solution til tonight. Personally, I'd also be interested in using the SSH solution if you can tell me which files should be deleted. Seems like a more robust solution for a clean install. Quote Link to comment
sjenkins Posted April 24 Share Posted April 24 1 hour ago, maxnorth said: I won't be able to test the MQTT Explorer solution til tonight. Personally, I'd also be interested in using the SSH solution if you can tell me which files should be deleted. Seems like a more robust solution for a clean install. I agree. The issue is finding the file; spent an hour last night until I defaulted to this. Does not seem to be where the mosquitto docs say it should be and Michel is out of town until tomorrow. The others are saying he knows the most about this. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.