someguy

Okay, thank you! And Thank you to Michel!

@Panda88: any update on this? Or has anyone figured out a workaround. I’ve really appreciated this Tesla connection for some time and would sure love to get it back sometime soon.

Where did you order them and what do they cost?

@dbuss will you please be more specific. 😀

yes, I have this and it works, but the admin console doesn't cooperate with showing it. it cuts off at the bottom of the page and I cannot figure out how to make it show up to see what it is. any suggestions:

Thank you guys both so much for posting this info!!! I just got a new i3 outletlink and it had the same problem and it was fixed by the factory reset as you suggested. Thank you and kudos!!!!!😀

@Panda88 any update on this? I relied on this nodeserver quite a bit and would appreciate it's return to function? 😀

okay, Thank you. I found it. it was at the top of the configuration tab:

I looked there and wasn’t sure what to do. There was nothing that related to “allow isy access”. More detail, please. 🙂

I'm not sure where to "enable "allow isy access by plugin". can anyone help?

Has anyone tried a robotic mower recently? I had one quite a few years ago and it was a huge hassle but I’m thinking of trying it again. There are new ones that don’t use a perimeter wire. perhaps someone knows of a discussion forum where I can talk to others who have these mowers and hear their opinions?

Any update on this? 🤓

every zone connected to my main board have a physical status of "EOL". are these zones with a "Physical status" of "unconfigured" a real problem?

any word on when this will be available and how to get it?

okay. I figured out one problem. I had the "access" box checked and this was blocking it... but with that fixed, I can use the isy to arm or disarm the system. I also cannot use it to change the chime mode. it is as though there is only information coming from the Elk to Polisy, but Polisy cannot tell Elk anything. yes, I'm using the non-secure port. yes, I believe my configuration is set up correctly in PG3(x)... because it does receive data from Elk. I will attach my error log, if I can. OKAY, I FIGURED IT OUT FULLY. FOR OTHERS WITH SIMILAR PROBLEMS: -don't check the "access" box for the user code that PG3(x) uses. -you must have the RP2 software "disconnected" for PG3(s) to connect to it.