maxnorth

I am currently running v40.2 mqtt-poly from the non-production store. With the production version be updated to 40 from v39 any time soon? I ask because I need to rebuild all my scenes manually each time I switch between production and non-production versions.

It is. Here is the body of one of my pushover messages: "message=The garage door state is ${var.1.7} where 0 is closed"

5.8.3

I had an odd thing happen on my eisy. The system went offline for some reason, which is rare. I powered off and back on, making sure the PLM came online first. It came up fine, but then I was getting some strange behaviors. It turns out that some of my programs that were set to disabled were now enabled. So, they were getting triggered where they should not have been. I also had a couple of programs that weren't working as expected. I fixed those by "updating" them without making any changes. I'm just posting this for informational purposes. I probably could have simply done a restore, but by the time I figured out what was going on, it was just as easy to do the fixes.

Ok, on a second try, status has started to show up now! Perhaps just rebooting the AC again is what was needed. Looks good. I'll post again if I have any further problems with the s31. Here's an example of what's in my devfile: - id: "sSonoffs31POW" type: "s31" name: "WaterHtrLoopEnergy_225" status_topic: "tele/sSonoffs31POW/SENSOR" cmd_topic: "cmnd/sSonoffs31POW/power"

Installed mqtt-poly, which shows as v40.2 as of this evening. My s31 device is still not visible in "status" for programs. Also, installing using a different name (mqtt-poly) is not ideal, because there is no "reinstall" option. This means you must delete your existing MQTT and then reinstall mqtt-poly in the same slot, if you wish to preserve your programs in AC. And you must reconfigure it in PG3. Then, you need to reverse this if you want to revert. Having said that, I appreciate all of your efforts. You need to get paid soon!

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?