maxnorth

A follow up on the s31 issue. Original details are in this thread: s31 energy monitoring updates (e.g., power factor, current power, total energy, etc.) ARE updating fine in the AC. There does not appear to be any issue with adding the device or keeping it up to date. The issue is that the device is not available in Programs. It is not visible in the "If" statement as a "control" or as "status". It IS visible in the "Action" statement, but with the only action available being "query" (as might be expected with a sensor). I'm not sure that logs would be of any use here, but let me know what you'd like.

I can confirm that in v39 "status" is now showing as an option in programs for most devices. An exception for me is s31. I will post separately about s31.

It seems likely the upgrade introduced corruption. Several solutions were explored in this thread. I would suggest you try deleting the existing nodeserver, and then reinstalling it. If that does not work, after deleting it, use MQTT Explorer (as detailed in the thread) to delete all the nodes except $SYS after deleting the nodeserver, then reinstall v39.

You should review this thread:

The "not required" notes in the might suggest no VALUE is required to be entered in those default keys, where in fact the key can be deleted entirely. I ran the thing with blank keys for many months before I figured this out.

A config file glitch I noted previously: 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.

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.