dbwarner5 Posted Thursday at 04:21 PM Posted Thursday at 04:21 PM @bpwwer Loaded the new plug in. Again took quite a while for discovery ~ 15-20 minutes. Lots of errors. Everything is pointing to "offline" in AC No node for the Controller in AC No grouping of nodes.. they ended up as their names alphabetically --> for testing purposes would be easier if they were grouped under the controller. One item did not come in with its name.. came in as Smart Bulb. Attached are the logs after I hit Discovery. Cheers!! Meross_4-10-2025_121759_PM.zip Quote
bpwwer Posted Thursday at 05:33 PM Posted Thursday at 05:33 PM That's good data, thanks! I see a couple of bugs that need to be fixed. One, it's not making sure the device names are legal for the eisy nodes. There are a couple of the names that are too long and I see at least one with a character that's not supported in node names. That's a pretty easy fix. It also looks like there's a bug in the switch nodes. I thought I had tested those but something slipped through. Shouldn't be a big deal to fix. A lot of the errors are just the plug-in trying to connect locally to the device and failing. I thought I had the logic right to make one attempt to connect locally and then mark the device as a remote device and not attempt local connections anymore, but that doesn't seem to be working given how much it's attempting local connections. This is probably the biggest issue. I've designed the plug-in so that it tries to mimic how the eisy handles Insteon and Z-Wave devices. Thus, there isn't a "controller" node, just device nodes. There's both pros and cons to doing it this way with the biggest con being that it does make it more difficult to find the nodes for testing. The eisy only allows for a single parent/child relationship between nodes. I'm currently using that for devices like the indoor/outdoor 2 outlet device and hub/sensor devices. If I grouped them under a controller, I'd no longer be able to have the multi-outlet or hub/sensor groupings. Trade-offs. I think a lot of the time it's taking to discover is because of the check to see if the device is local. It looks like that takes about 30 seconds. 1 Quote
dbwarner5 Posted Thursday at 06:45 PM Author Posted Thursday at 06:45 PM Yes. All of my devices are remote not local. thanks! let me know when you want me to try again Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.