GQuack

Hi all, I’m revisiting this post because I’ve just upgraded my system and added a 2nd inverter with attached battery. I’m thinking there are several options and wanted to reach out here to get these added to the ISY. 1) Stop and restart the node server and see if the new nodes show up since the new components are now part of the overall SolarEdge site. (answer: tried this and they don’t) 2) Delete the existing nodes within the ISY, then add all nodes again (seems like a more likely approach) 3) Try to add all nodes within the ISY and see if the new nodes show up (answer: tried this and they don’t) 4) other?

That is helpful, I didn't know that was there. Also just experimented with the Copy Folder to Clipboard and then paste to Excel or Word which would also be possible to use with search in those programs plus form a basis for the documentation. Thank you MrBill

Does a means exist to create a cross reference of where devices and variables are being used in programs? I know you can see where devices are used in scenes, but I use variables as a major piece of logic control and manually having to find everywhere a variable and / or device is referenced in multiple programs leads me to always miss something. I'm feeling like I may have to do something drastic like create detailed documentation, the last thing anyone wants to do. ?

bpwwer, you are da man! That was exactly it, Polyglot did not act on the api-key it received until stopped and then restarted. I now have 4 entries, 1 for the controller, 1 for the site plus 2 sub-notes under that, 1 for the battery and 1 for the inverter. Thank you so much! Hope this helps you as well when you get your system.

I just deleted the SolarEdge from the ISY, re-added it, generated a new api_key, added that to the config parameters, same result. I don't speak Python but it looks like there may be some errors in this log data (attached), anyone speak Python that can take a quick look? Screen shot from SolarEdge below showing the new api-key, screen shot of the configuration page, and text file of the log. solaredge-0021b90250ef-2.txt

I do know for a fact Michel that I do have Admin Access as that was a struggle with SolarEdge to acquire and I had to use a separate email account to do that. I have the ability to create, modify, and assign profiles to my inverter which requires admin access. I'm going to try to start over and delete what is there and add it again now that I have the api-key value. It's also possible once I generated that key it may have taken some time on the SolarEdge side for everything necessary to propagate.

Where can I find some documentation on setting this thing up so I don't have to keep posting questions? The wiki has very little info and nothing on SolarEdge that I can find. I entered the api_key, the controller node shows up in the ISY but is blank with no information. I see the 4 nodes available to install under the node server configuration but when I select Add all, nothing happens. I'm clearly missing more setup info.

Thank you MIchel, I will look for that but...how do I specify that value within the configuration?

Hi all, just upgraded to V5.0.15A and am taking my first adventure into Polyglot. I am working on adding WeatherFlow and SolarEdge to my ISY. I was successful with WeatherFlow and that seems to be working correctly, my issue is with SolarEdge. I am seeing the message in the log: Please specify api_key in the NodeServer configuration parameters and did some searching on this forum for that info. I am the administrator of my site so I have the site ID which looks to me like a seven digit number. I see the comments referring to both site_ID and API_key. I am assuming these are one and the same? My question is: add it where? In the NodeServer configuration, I tried adding that seven digit number as a custom configuration parameter under both site_ID and api_key but that has not been successful. What am I missing?

If version 5 is stable, why hasn't UDI made that the "official" version? They show 4.7.3 as the official although 5.0.16 is now available.

mmb, I do not have that little right arrow option for variables in version 4.7. Going to have to think seriously now about migrating to V5.

Well that would explain a lot...keep wondering when version 5 is going to be "official."

I am trying to pull the humidity level from the thermostat. Based on that value I will take action using the IR control. Look for the variable in the thermostat.....where is that available, I don't see it anywhere?

I am sorry mmb, I don't see that option at all. I am in the Then section. The only choices I have are set to another variable or a number. I don't see that right arrow option anywhere. Is this perhaps a new option? I am running 4.7.3

Huh? Where is this? Where is "assign the Humidity value in the device?" I don't see that option in the program section..Thank you for your help, this is exactly what I was looking for. I just need to set up a program to periodically query the variable, right?

Yes.

I may not be seeing it but is there a variable I can access in an ISY program for the humidity level as reported by an Insteon Thermostat? (2441TH). I am using IR control to turn on and off an A/C unit based on the temperature and that works just great. But..I would also like the ability to turn the A/C unit to it's humidifier setting if the humidity rises to a high enough level. While I see the humidity level on the thermostat display I don't see any way to access that value in a program. Am I missing it? Thank you for any help.

Thank you Paul...

Hi all, pretty sure I know the answer but would like to confirm before I pull apart my previous wiring. I hooked up 3 new ceiling fans via fanlincs and 6 button keypads. I used the load connection for each keypad as the line to the fanlinc not thinking through the ramifications of that and setup a scene to turn on the light when the ON keypad button is pressed. The light works fine but I can only get the fans to work when the light is on since power is only being supplied to the fanlinc when ON is pressed....duh. I just need to tie the line connections together and the neutral connections together which means abandoning the load connection on the keypad. I can then continue to use the ON button to control the light via my existing scene and independently control the fan speed via the other buttons. I'm pretty sure not having anything connected to the load from the keypad would be a problem but would like to confirm that??? Thank you for any responses.

Hello all, thought it worthwhile to post a final follow-up and again a thank you to those who helped me through this. After replacing the bad IO Linc, I've completed the project which was to use IO Lincs to separate 4 sets of outdoor lighting into unique "zones" all using the same transformer. I used an outdoor plug-in module to control the main power to the transformer and routed the 4 sets of outdoor wiring through an electrical box in which I mounted a high quality surge power strip for the IO Lincs and wired each strand of the landscape wiring through it's respective IO Linc. Each IO Linc is controlled via a scene from a keypad. While I know the power strip is probably not a best practice, the overall result works great, I can now control each of the 4 zones independently but all powered from the same transformer. I've attached a couple of pictures for anyone who is interested. Regards

I am likewise experiencing this same issue. All has been fine and today tried to discover devices due to some changes and am getting the same error: Unable to complete your request. The Echo and ISY are talking just fine together, lights, scenes, etc already in Echo work without issue. Have tried: disable / enable skill, reset the network completely, unplug the Echo...all same result either through the Amazon app or browser.

Hi all, here's my report back. The short answer: The IO Linc was bad. Tested using the 9 volt battery and voltmeter and could not get a current to pass through. Still the same odd behavior with the LED status light. Replaced the IO Linc with a new one using the same configuration and with the 9 volt battery and voltmeter...success! LED status light is responding as expected. Rewired into the exterior lighting and tested again, still success, Yay!!! Moving forward.... Thank you all for your replies and help, this was a good learning experience other than the cost of a new IO Linc.

lilyoyo1, I disassembled the wiring yesterday. Going to experiment inside with a 9 volt battery as the power source and use the voltmeter to see if I can figure out what is happening. I’ll report back...

Yes, the lights work fine. I've had them direct connected for some time now and am trying to move into the segregation method. I've been reading and re-reading the section of the manual that palayman referenced...if you want an ON command to open the relay, set the relay to be open. If you want an ON command to close the relay, set the relay to be closed... Using the ISY, how do you "set the relay to be open" or "set the relay to be closed?" I have latching continuous selected and am using the N/O physical connection. I see no other options, Is there more to it than that?

Thank you all for your responses. ronvond: to answer your question, I do have a relay controlling power to the transformer but assuming I get this problem solved, I will be using 4 IO Lincs to control 4 separate runs of lights for the same transformer each run controlled with their own scene. palayman: to answer your question, I am using a 6 button Insteon keypad linc for this exercise and per my above comment, will be using 4 of those buttons each controlling one of the 4 scenes. The scene itself has only 2 devices in it, 1) the keypad linc button as controller, and 2) the IO Linc Relay (not sensor) as responder. The IO Linc is set to 100% relay on level. Turn the scene on, I expect the IO Linc to pass the current through the run wired to that IO Linc. Turn the scene off, the run turns off. oberkc: to answer your questions, I do not have anything connected to the sensor terminal. For testing, I am trying all the following; 1) turning the scene "ON" via the keypad button, 2) turning the scene "ON" via the admin panel, and 3) turning the Relay only "ON" via the admin panel. In all 3 scenarios, the admin panel shows the Relay status of "ON" but the status LED light behaves differently. The status LED light is lit only in scenario 3, it is not lit in scenarios 1 and 2. This makes no sense to me, I would expect the status LED to be lit anytime the relay is "ON" regardless of the method used to turn it on. I get no change in behavior (lights are not on) when the relay is either in "ON" or "OFF" status. I think the voltage probe is the next logical step. I'm sure there's something staring me in the face and I just don't see it. Any other comments or things to try are most welcome.