someguy

where is the "display on keypad" feature? is that something in Elk or is it in ISY? i dont think the PLM can talk to the Elk system itself. my Keypad connects to the Elk M1 through an ethernet connection (or wifi).

@apostolakisl yes, I understand what you are suggesting and it makes sense. what I'm trying to accomplish is to have a use for the new keypad I bought: Elk 7TS touchscreen "keypad" I'd like to have the screen show the current status of a few lights so that I can see that they are off when I go to bed (and turn them off if I desire to do so). This is why I want Elk to know what the status of lights are in ISY.

I appreciate any help i can get here.

I updated to the newest version (0.2.10) and it is still not working, again. I tried re-authenticating it and that hasn't helped either. any suggestions?

I’m looking into using yolink. If I want to use it with local API, what do I need to do? Is there a certain hub I should buy? Thank you.

Does anyone have any suggestions as to how to get this sorted out?

well, I tried re-authenticating it. then I checked the webhook and now, it is working! I'm not sure what changed but, Thank you!!

I just tried out the new TeslaEVStream nodeserver and I get all of the nodes but they are all devoid of data. any suggestions?

When I go to details in the node server in pG3 there is a blue box that takes me to a browser to grant access for wireless tag to PG3. I click the button that says to give UDI access and that error page pops up. I’ve tried this on two different computers and three different browsers.

how might I fix this, please:

I was able to get my Elk set up to control lights, but even though I can control my lights with the Elk keypad, the keypad and the elk system aren't getting updated on what the status of the lights is when I change the lights' status using any other method than the Elk system itself. how can I address that?

I've got them set like this: how do those settings affect the behavior? I think I found the problem though. maybe I spoke too soon. I found a program that was changing the "climate type" to away but it wasn't showing up in the Programs > Summary page, as far as I can tell.

I am having a problem with my "vacation" setting in the ecobee. when I set a vacation inside of the ecobee app, then the thermostat goes into vacation mode and then my ISY somehow changes it to "away" mode and this fouls up the temperature settings. I have proven that it is the ISY doing so because when I stop the Ecobee nodeserver in Polyglot, the problem doesn't happen. I've looked through all of my programs and I can't figure out how it could be doing this because I don't have any commands of this type. any suggestions?

@Jimbo.AutomatesI appreciate your help with this great nodeserver. I am having one snag: even though I can control my lights with the Elk keypad, the keypad and the elk system aren't getting updated on what the status of the lights is when I change the lights using any other method than the Elk system itself. how can I address that?

@Jimbo.Automates: I got my lights imported to my Elk system and there is good news and bad news: now, when I try to turn the lights on or off with the M1, it works! and it is instantaneous! but, when I turn the lights on with any other means, the M1 doesn't know that the lights are on. here are a few other comments I have that could help others get through this process. 1) there is an "export" button in the Elk Nodeserver in the Admin Console. it is confusing because that is not the "export" that is used to export the data from the ISY (to later import into ElkRP2. 2) when using the "ELKID" method there cannot be anything else in the "notes" than the ELKID=x. also there cannot be anything in the "location" which is right above the "notes" in the admin console. 3) Scenes don't work using this ELKID method, which is unfortunate but not surprising. 4) In ElkRP2, the "import" that is necessary is found in the "lighting" area by right clicking it and then selecting "import lighting data".