hart2hart

I did same and bought standard USB to micro USB at Amazon. https://www.amazon.com/gp/aw/d/B0C14W14F7?psc=1&ref=ppx_pop_mob_b_asin_image&th=1

@sjenkins All has been great with Virtual! I defined 9 switches using the json format as you took ownership of the node server, and they worked as expected and had values of On and Off. I've upgraded to each of your releases (except most recent beta). This morning, I defined 3 additional switches, but their values are showing as True/False. The json configs are the same other than IDs and names. Looking at the node details the UOM is 25 for the original 9 switches with values of On/Off. The UOM is 2 for the 3 created today that have values of True/False. For the non-programmers in the family, I need On/Off. Advice?

@Javi I really like this feature and have used it for last few zwave devices. The only issue is the QR code on the devices is very small so it takes a bit of patience, stillness, and tinkering with distance and lighting for camera on iPhone 15 to read device code. Can you use 2x to make it better or let user pick zoom?

Hi. Just seeing post. I’ve got two ezflora still clicking along after I replaced all capacitors. Would you be interested in parting with it?

192.168.1.xxx is very/most common for Class C addresses. Depending on how you assign addresses(DHCP or Static) in your network., I’d tend to go back to it to make sure 192.168.50.x has not broken something else you haven’t even noticed yet.

You need to enter a support ticket. UDI will likely be able to get your PLM and Devices in sync.

It is fantastic! I’d request considering doing the same for creating Topology.

Thanks, Javi. The reboot fixed it!

Everything in the ESPHome version looks and is working great! I do have a question about its interaction with UDM and have synchronized it to eISY A few times. The standard device has status values as expected. However when creating a Favorite with a door’s status, I get status integers of 1,2,3… instead of status values of Open, Closed, Opening, Closing etc. When I do UDM Advanced Status Configuration on the favorite I see the status values and I can say if Open display Open. Is there a linkage, hint, or mapping that needs to be updated? Also, if more of a UDM question can you assist me, @Javi ?

@bmercier What is the latest update? Will you be releasing a fix for PG3X or is it up to impacted plugin developers at this point?

@Goose66 ,thanks for update supporting what appears to be the mainstream ratgdo firmware. I saw other post about you desiring to debug case where ratgdo are not discoverable. I've updated my two ratgdos with ESPHome firmware. They are both reachable and controllable from the web interface, but discovery throws errors on both. I had deleted the prior version of plugin and installed version 4.0.8 in the same slot. What do you need for debugging?

Have you created a node server that uses the ESPHome firmware -- Damn! You've put so much into Garage Door node servers.

@sjenkins Upgraded to 3.1.5 and see the Discover button in PG3 and the updated documentation. They work and are clear. I have nine virtual switches declared using JSON, so I'll take your advice and look at declaring them with YAML. Either one is far superior to standard declaration. There appears to be a substantial bug in the ratgdo MQTT firmware with security + 2.0 where it randomly stops controlling the garage door but keeps reporting the status values. It takes a full erase and reflash to fix it. @Goose66 , that wrote the ratgdo nodeserver, has found where the bug does not appear to exist/been fixed in ESPHome version of the firmware. If a repaired version of MQTT version is not released soon, I may consider the added complication of installing the HA container on eISY. Does it make sense that the garage virtual device you've created would provide a simple interface from it providing the equivalent interface to current ratgdo node server via HA?

No worries and no rush. Just wanted to let you know in case I was missing something.

No real issue but I’m running version 3.1 and PG3 is telling me an upgrade is available to 3.1.0. It does not see them as the same.

@sjenkins The JSON configuration documentation and method are excellent. For sake of documenting what I have, I "redefined" them using JSON configuration including their names. I Restarted vs Discovered and all looks great and is functioning well. Thanks for moving this forward. I believe there will be many ways to use and expand the node server! in the future now that it has an owner.

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"}

I’ve been using Win 11 since it came out on two 4K monitors. Fonts read great. Been a while but I recall having to mak an adjustment to settings.