hart2hart

I found the following line in the Configuration help: Discovery Discover button will add or remove nodes not in one of the configuration methods. ..and located the following in one of your other posts: 3.1.2 renaming of nodes based on configuration ISY nodes to be renamed based on config / YAML / JSON changes - rename will happen upon restart or Discover - rename will not happen to default named nodes, where no name was given in the config, so as not to wipe out user renamed nodes in ISY Does that mean the name will not be used since the device was already created and renamed on the eISY? Regardless, I'll enter the names that I gave them on eISY for "documentation". Also, Does the Discover button only exist under certain circumstances? I don't see it in the production 3.1.4 version.

Thanks. I upgraded production instance to 3.1.4. Of course devices are delcared via Standard config: 1 switch 2 switch 3 temperature ... How can/Can I maintain the same devices but include their names by moving them over to JSON config?

I have same issue with electronic interference where my eISY is located. I relocated the zwave and matter antennas over coax cable instead of the entire dongle over usb.

I didn’t start AC until after I installed the 3.1 update. However, I just ran it again and it of course is there. Thanks again. I’ll chat with FLUME to see if they can set it true as a test.

Thanks! I updated to 3.1 and checked variables and status and do not see a leak indicator. Where should I be seeing it?

I pulled it up again today and they are grouped together.

Thanks for update.

@sjenkins I used the JSON method to create test devices. It worked but why were some devices created at different levels in device tree? Key Value 101 {"id": "101", "type": "switch", "name": "Front Porch Switch"} 102 {"id": "102", "type": "switch", "name": "Back Porch Switch"} 201 {"id": "201", "type": "dimmer", "name": "Patio Dimmer"} 202 {"id": "202", "type": "dimmer", "name": "Driveway Dimmer"} 301 {"id": "301", "type": "temperature", "name": "Outside Temp"} 302 {"id": "302", "type": "temperature", "name": "Inside Temp"}

Went for run and back home. Prod 3.0.1 and beta 3.1.0 now.

Hi. No they are both still showing the prior versions in plugin store. I updated/reinstalled production and beta versions to see if new version numbers would show afterwards but they didn’t. Edit: tried with different browser options n case it was a cache issue. Still same.

Thanks again for moving Virtual forward. Just letting you know that the upgrades are not showing for either beta or production versions.

Hi. Haven’t seen your name pop up in a long time. Are you still active with Weatherflow?

I had wondered the same thing. Just got them reflashed and working so I'm going to create programs that turn their lights on/off in middle of light a couple times to see how long until it happens again

Do you think there is a design issue in HW preventing a fix via FW?

Both doors non responsive again. Hope FW gets fixed.

Thanks for picking virtual up. It was not intuitive a year ago on how to set up as names of fields overlapped. I’d suggest something like 3 fields to define a virtual device: Virtual Device Number (01) Virtual Device Type (switch) Virtual Device Name (Front Porch Motion Enabled)

Great. Were the nodes created by the beta the same nodes from v2 production?

Like others have said, thank you. I've been using the plugin since moving to eISY. I mostly use switches to act as binary variables. I turn them on or off to set behavior/events. For instance, I set a virtual switch on to signal an irrigation program to run that night and its sets switch off. Also, use them to control motion detection for Ring lights. I set the switch on (as a favorite in UD mobile or Alexa) to block motion detection so program will not run with motion and light stays on at whatever level it has been set to manually. Some may be set as devices for Alexa to trigger announcements for leak detected or something else -- can't recall. I'll look if anyone is interested. I'll install and test in next week. Paul

I notice a light was not coming on when I walked through Ring light with motion. Finally got around to sorting it out. I did following: Checked all conditions and the motion event was the only thing missing for program execution. Looked at NS log and events were not showing Restart NS Rebooted eISY Stopped and Started NS Authenticated to Ring At least two times each above I reinstalled the NS and motion is detected again. Programs run and can see activity in the NS log works Let me know if you want me to DM logfile

It would be highly coincidental if it failed at same time of 5.8 install but I’ve had to recap both of mine as they fail like a PLM.

I’ve got two of them working with 5.8. At some point since the last irrigation season, scenes that included the device zones had an issue. I had to set the zones Scene On status in the scene. It had become Off and I selected it to On.

Open a support ticket with UD.

@Jimbo.Automates What do you think of adding the possible leak status?

Me too! My question is would it even be possible to use the ESP Home FW in our environment.

@Goose66 I’ve recently flashed with erase for second time. As you noted and others, the ESP Home FW does not appear to have this issue. Feel certain you’re tired of GDO at his point, but if MQTT FW is not fixed at some point is moving plug in to ESP Home even a possibility?