maxnorth

When MQTT server is first installed, it adds configuration keys by default: mqtt_server, mqtt_port, mutt-user, and mqtt_password. None of these is needed for a native eisy user. Most users will not use a separate MQTT broker. So why add them? It creates confusion. Use configuration help instead to describe how to add them when/if needed. It also add a "devfile" key by default with a suggestion as to where to store the file. But do most users have the skills to create such a file and use terminal to store it on the eisy? Perhaps use a devlist default instead OR add more extensive configuration help describing how to create the file and copy it to the eisy.

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

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?

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.

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.

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

My store still shows 0.37

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.

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:

I had explored this somewhat in a previous thread: There are a couple of paths listed in there that might be helpful.

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'm up on MQTT Explorer, but not sure what exactly needs to be deleted. See screenshot

We will have to wait for the devs to make it available in the store, I believe.

v35 was stable for me.

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

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.

For what it's worth, I installed 0.0.37 and now I have the same problem you do. I can control devices but the status in the AC does not update. Any clues @TriLife?

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.

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.

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.

Well, one device is working, so that suggests the issue may be with the config of the clients. Let's review: - You are using Tasmota, I assume - You have logged into the Tasmota web interface for each device and configured it correctly, especially the "Configure MQTT" menu choice. (Be sure to type in the password even though there appears to be one there already). - If so, you should be able to look at the "Console" menu choice in the Tasmota interface and see the MQTT messages being published by Sonoff. When the device is turned on or off, you should see a properly formed MQTT message. Its format should match the format you've specified in the dev list for stat/ and cmnd/, in particular the device name should match. Capitalization should match. - If there is a mis-match, it does not throw an error. Just nothing happens.

Pick one of the offending devices, delete it from the node server (both as a node and from the dev list). Then re add it to the dev list and try again. Once a device is added to the node server, it stays there until the node is deleted, so this will ensure a fresh start. Just test on one device first.

Try using all caps POWER in your command topics.

I have had similar issues on a one-off basis since my migration. Naturally, you think the program is not working, at first. But, as it turns out, I have been able to resolve all of my issues so far by just restoring the device. (Highlight, right click, restore device).

@xKing, I have had no takers on this question. The power sensor device (s31 in dev file) simply does not show up anywhere in programs. (Sonoff temp sensors DO show up). I'm on the latest PG3 and 0.0.35 of the node server.