Jimbo.Automates

What Kasa devices do you have? Some of the newer devices are not yet supported because Kasa changed the unsupported API. Sent from my Pixel 8 Pro using Tapatalk

Yes I did. Good luck with Rachio. Sent from my Pixel 8 Pro using Tapatalk

Yeah! Glad it's all working. That is correct. and yes, if someone is able to get onto your LAN they can connect to the unsecure port, but they still need a user code to arm/disarm. I could allow connecting via the secure port, but then would have to store the username/password in PG3 which does not yet have a secure way to store the data. Yes, it's the same. and it really could be done either way, but most prefer to control it on the router side not on each individual device. The secure port still works same as before. You can also now use UD Mobile now to control it remotely My bad, yes it's M1XEP.

It's M1XEP When you say unchecked static, I assume you meant you checked "Assigned an IP address via DHCP"? When you say "Now ELK Won't connect to Network" how do you know? Do you mean you can't connect to the ELK? It likely went to a different IP address, confirm your reserved setting is correct on your router. I reviewed the log and it looks like the Elk library is having trouble with the host you entered, earlier you said it was "192.168.50.xx:2101" can you confirm that's exactly what it is? Then on the same page where you did Download Log Package, set the Log to "Debug + Modules" and restart the node server. After you figure out what is wrong with your IP reservation. BTW, I deleted your attached log package, there can be sanative info in those logs so you should PM it instead of attaching.

This should have been posted in the PG3 -> Elk forum, and is being discussed here:

I asked the same a while back, and decided to stay with the Zooz Titan that I already have but appreciated all the input from everyone.

No worries, usually I learn something new, and something to add to documentation if I remember... The "Enable Non-Secure Port" Must be checked, and sent to the M1EXP. Remove the static from the ELK and let it obtain from DHCP, and reboot after fixing #3 as well. I don't want the eisy log, I want the node server log. In the PG3 UI go to Details Page for the Elk nodeserver, then click Log, then Download Log package. Email to jimbo.automates@gmail.com if you can't attach it in a PM and include a reference to this post so I remember what it's about.

This is intended one way: eisy programs/scenes->Notification sever->devices->pushover? Not sure what "devices" are, but it goes from Notification nodeserver -> pushover service -> devices I can use "Add Pushver service nodes" multiple times to connect with multiple pushover apps I've created? Yes It shows up as a device I can use in a "Then" statement from my programs to create notifications more simply? Yes, it's' documented: PG3 Notifications Node Server Do the notifications sent this way not show up on UDM? No, Only UDMobile notifications show up in UDM. I, and many others, used Pushover exclusively for a very long time from the notification node server before UDM notifications were created.

> I went to the node menu, picked the ecobee and install all devices... after a few minutes i got these devices. Never use that, it's not applicable to any node servers that I'm aware of. > I think I'm missing the main control pane, and the names on most of the individual items is wrong... See pics Did you close and re-open the Admin Console after installing the node server and entering the PIN? The Admin console only loads the profile on startup so when the profile changes you have to close it.

Q: There is no need to port forward if the eISY & Elk are both on the same LAN. A: The ELK and eISY are on the same network. To be clear, they are both connected to the same ethernet switch which is then connected to my router. My modem is on bridge mode and it is my wireless router that gives out the IP addresses. Is any of that a problem?? AA: Yes, remove the port forward. Port forwarding is for accessing devices inside your network from outside your network. Q: Personally I don't use the same code as other users, I create a new code just for the plugin so I can know who did it. A: Does this user_ cod mean anything? I assume using my ELK sign in numbers is good enough. Correct? AA: There is no ELK sign in for the node server. It needs the user code to arm/disarm the system. Q: Please confirm with ElkRP2 that unsecure port is allowed and is set to 2101. A: I had it set to 2601. Changed the settings to the way you show. I then saved the changed and rebooted ELK. I then rebooted eISY. No change. Still shows M1WEP status as "False" AA: If "Enable Non-Secure" is enabled as shown in the attached, then we have some other issue. I suspect it's the IP address. Q: Personally I'd do this on the router and let the Elk obtain the IP from the router with DHCP. A: I would prefer that but someone said static was better. Should I change it? Yes, I would. You can assign a static IP in your router for that MAC address, that's a better way IMO to manage it. After confirming non-secure port is enabled, please download log package and PM or email it to me.

> I created a static address for the IP address for my ELK under the MIXEP Setup / TCP/IP Settings Personally I'd do this on the router and let the Elk obtain the IP from the router with DHCP.

@dantoronto > "M1EXP Status" False That's the problem. The plugin is not connecting to your Elk M1EXP. > In my router, I port forwarded 2101 for the IP address for my ELK. I used TCP as the protocol. I could have also used UDP or Both. There is no need to port forward if the eisy & Elk are both on the same LAN. > user_code: used the password we use to arm or disarm our ELK keypad Personally I don't use the same code as other users, I create a new code just for the plugin so I can know who did it. > Host: the IP Address for the ELK with 2101. 192.168.50.xx:2101 Please confirm with ElkRP2 that unsecure port is allowed and is set to 2101.

Thanks, issue created: https://github.com/UniversalDevicesInc-PG3/udi-harmony-poly/issues/36

@dantoronto On the Controller node what is "M1EXP Status" and "NodeServer Errors"? Also, what do you have the configuration parameters set to?

so, I tried turning the "Hold Duration" in the app to "Decide at time of change" and it worked. the problem is that i have children who will adjust thermostats and choose "indefinite" setting change and this will not allow the normal schedule to resume. I'd like to have the ISY be able to setting the "hold duration" to "indefinite" but the thermostats themselves to only be able to change the temp "until the next schedule". I'll try to review the API and see if there's anything that could help. You could have a program the hold and force it back to next schedule? Sent from my Pixel 8 Pro using Tapatalk

That is in slot 3, you'll need to look in the PG3 UI to see what is installed. Sent from my Pixel 8 Pro using Tapatalk

They are installed in different slots?

Thanks. I wasn't sure with Alexa, with Google I use the approach you mentioned with a program to arm. Sent from my Pixel 8 Pro using Tapatalk

I'll need advice from @bmercier on the best device type and hint to use, but this will require changes to the ELK plugin to support. Sent from my Pixel 8 Pro using Tapatalk

Ecobee only has polling. Sent from my Pixel 8 Pro using Tapatalk

I upgrade modules rebooted and no issues. Please set Log Level to Debug, restart, and when you see that error again please "Download Log Package" and PM that to me.

This looks like PG3 didn't send all the info the plugin was waiting for. I see you are on the latest release so I will upgrade and see if I have any issues.

The updates are pushed to the responder so it knows what to do when the controller activates it. The changes were made in ISY many years ago. I have programs which set the Level variable based on time of day and this program reacts to the change.

They do not, you can have a program set them to ignore for that controller. I used to do that a lot when I used them. I still adjust levels in Insteon motion sensor controlled scenes.

Yes, I understood that in the original post, but nothing about the Ecobee plugin could be messing with your lights.