apostolakisl

Is this actually going to happen? It really has been a very long time. Perhaps someone else who owns a Tesla should take it over?

Looks like it is working.

Still can't connect. Same thing as before.

Started 2 days ago here as well, but there were no updates or any changes to anything in the system or network.

Same issue with me as well. Didn't notice this thread and already submitted a ticket. I have two ISY's on the same login for the portal. One works fine, the other does not. Everything works fine using a local connection. I get a 404 error in UD mobile for just the one ISY. Other users on the same ISY with their own portal accounts also are seeing the error. Despite the error, UD mobile still displays the device list and I can still control the devices, but the status isn't populating correctly. I can also synchronize UD mobile to ISY without error. I tried rebooting ISY to no avail. Using the portal on my pc to login with the java console, I get authenticated and loads the device tree, but then gets stuck at "starting subscription" and just swirls and swirls.

I have a situation where I would like a youtube channel that goes live to trigger an ISY program. Is that possible? Even better, it would also trigger when it stops being live.

Suggestion to change the name of the plugin from hunterdouglas to HunterDouglas. The plugin store does not alphabetize the lower case letters where you would expect it to be. I didn't realize the node existed until I saw this thread and used the ctrl-f "hunter"

The instructions I provided above is indeed to allow for Alexa to also control the scenes.

There is no reason that 2 kpl's can't control a fanlinc any different than one kpl. You set up 4 scenes, one for high, med, low, and off. First add the fanlinc to each scene as a responder. Then add all 4 buttons to each scene for both kpl's (8 buttons). All of the buttons are responders except the button for that scene. Shown below, you see for fan low, the KPL low button is red, meaning it is a controller. With two KPL's in the scene you would have 8 KPL buttons in each scene and two of them would be red. Then set the on-level to "off" for all of the non indicated buttons in that scene (in this case, high, off, and medium). In the below example you can see that only "KPL Low" on level is set to "on", the others are all "off". Remember that you need to set the on-level for all responders when controlled by each controller. In my case, that is the master scene and the one button in each scene designated (the one shown in red in the tree). In your case, it will be 3 (the main scene and each of the two KPL controller buttons). It will take you a while to set all that up having to go through 4 scenes with 8 buttons in each scene and 3 controllers. In addition to setting the on-level for each KPL button, don't forget to set the fanlinc level to low/med/high/off for each scene 3 times (once for each controller).

yes, nodelink.cmd

You can use windows task scheduler to create a task that 1) under general tab check runs with highest privileges 2) under triggers tab select at startup 3) action tab select to run a program (nodelink)

you may need a flash chip. They sent me one for my polisy. You have to open it up, plug in the flash chip, then issue some commands from an ssh session to reflash the firmware.

When I do that, the one line I see there is blank in the runtime parameter column. Do I just add that?

just finished an online session with Michel. We deleted the whole wrong uuid pg3x instance and restored the backup to the correct uuid, except it didn't work. The restore created the same wrong uuid instance. No doubt, this is how it happened in the first place. I suspect I will have to go through and copy down all the config parameters of every node and move them over manually, but Michel is thinking about it for now.

I tried changing to 0.0.0.0 and the nodes still all seem to work fine, but the uuid is still wrong. I was thinking I could back up this instance of pg3, delete it, and then upload the backup to a new instance of pg3 with the correct uuid. I'm not really sure how the backup and restore works, if it only backs up the nodes or if it backs up and reloads the entire configuration including the uuid. The issue I fear with this is that I will have to re-save every program that has a node server condition within the if clause. Anytime I delete and re-install a node, I have found that despite everything looking correct in ISY, that programs that contain that node within the if clause don't work without opening the program, then clicking on any item in any clause, then clidk "update" even though nothing changes, it causes the program to have the little green arrow meaning it needs to be saved, then I click save, and then it works. I have a lot of programs that use node server items so doing this for every program will be a pain.

I'm at a remote site right now using vpn, so I can't unplug it. However, I have just noticed that the uuid shown in PG3x is not polisy or my 99ir. I am starting to think that perhaps the uuid listed belongs to my old 994 that I replaced with the polisy and that when I migrated over it kept the old uuid. And when UDM goes to sync with pg3, it sees the wrong uuid so it creates a new IoX on pg3 that is then blank. I think I need to be able to edit the uuid in PG3x, but it doesn't let you do that. The uuid (mac) is not anywhere on my network. My router lets me list everything by mac address and this address does not exist. Despite the wrong uuid being there, it still is working, all of my nodes under this particular instance of PG are all showing up on my polisy and working, though I have had some weird behavior which may be related. How would I fix the uuid without starting from scratch? Could I do a backup, delete the pg instance and then create a new instance and restore the backup?

No, all the settings point to 192.168.1.9, that is my Polisy. It used to be my 994 before I bought Polisy, but I suspect I bought Polisy before UDM even existed and thus had all that transfered over. And my 99ir is not linked to the portal (not sure it even can be). I don't even know the ip of the 99ir without looking it up, so I couldn't have brain farted it in somewhere. The ISY finder does find the 99ir and lists it, but it seems to think it is a 994, but regardless, I can't open the admin console on it anyway because of Java security issues. I need to just unplug the 99ir anyway since it is doing nothin but wasting electricity. But UDM keeps listing the mac for the 99ir even thought it is for sure not connected to it. The 99ir is only setup to receive ir signals and then via REST send triggers to Polisy (which it no longer does since Polisy is on port 8080 and my 994 was on 80 and I can't get into the admin console to change that port. Which is a bummer because I really don't feel like going through the trouble of relearning all those ir commands and programming all this into Polisy.

Nope. I then tried changing the name from My Polyglot to IoP (which is the correct name), and it then loaded all the nodes and showed them as managed elsewhere. In addition, when I went back to PG admin console there were now two Instances available both named IoP but with the second and new instance having the mac address of isy99ir. Then I thought to look at UDM's main configuration and there it lists the mac address of my 99ir. However, it clearly is not connected to that. The 99ir is basically blank yet I have full access to my Polisy ISY via UDM. So somehow, UDM has the wrong mac address of my Polisy but yet is connecting to it normally as far as ISY is concerned but not as far as PG3 is concerend. I do not know how UDM ever got that wrong mac address. I never connected it to my 99ir, never entered its IP address. Perhaps there was some network search it did and found it? EDIT: I tried "clear UUID" in UDM, then resynced, and it put the wrong UUID back again.

It was connected to my ISY as there was a node in the #8 slot from that. I told it to "delete current iox" while I had that one opened and it removed the node from the #8 slot in my ISY and left all the other correct nodes from the other pg3 instance. However, I synced my UDM after that and now it says there are no node servers installed for this system. . . . Then a pop up says could not get isy . 500

From PG3x dashboard, when I click iox configuration -> edit current iox it shows 192.168.1.9 port 3000 for one of the two mac addresses of isy's and port 8080 for the other. 192.168.1.9 is the IP of polisy. The mac 00:21:b9 . . . is the one that is correct.

It is a 99ir, not 994, it is ancient, can it actually allow for that? But the one that is supposedly linked to my 99ir is not, all the nodes are on my ISY that is on Polisy. I should unplug the 99ir since it appears Java will not allow me to ever log into it again to change the port from 80 to 8080 so it can relay IR messages. Anyway, how do I access the second instance of PG running on my Polisy? I only know of one way to access the PG admin console on my Polisy and it doesn't manage that node.

How do I do that? I don't understand how this happens. How can there be a PG3 instance that shows its mac address as my ISY 99ir? And if I click on that instance of PG3, then it lets me manage the nodes that are clearly on my Polisy. I have no idea where the one mystery node is running. It lists Polisy mac address as its location, but when I log into the Polisy PG3x admin console, that is the only node that is not managed there. If you see below, there are two listed. MyPolyglot is the one that loads by default. It manages one node, it is the mystery node that I don't know where it actually resides. The mac for that one is the mac of my polisy. If I click on the IoP one, it lets me manage all of my "real" nodes. The mac listed is actually my ISY99ir, which clearly is not hosting PG. I would like to completely get rid of the mystery PG instance where it lives and have just the one correct instance. And what is up with my ISY rebooting upon opening this section of UDM?

I just pulled up UDM and it was already on the plugins page. It just swirled and swirled. Then I backed out of it to the main page and saw my home ISY was offline. Upon logging in to ISY admin console from my computer and found that ISY was rebooting. I logged into PG3x admin console from my computer and it showed nodes coming back online. It appears that accessing the UDM triggered a reboot of ISY or perhaps the both ISY and pg3x, not sure. The run times for my nodes still say multiple days but those run times never seem to be right. The settings per above are all correct and have been the same and working for a very long time without need to change. It is my local IP address [http://192.168.1.9] (the same as entered in the settings part of the plugin section and the same I use to login to the admin console from a pc) and here it is port 8080. My ISY connects to UDM and I can control ISY and see all the correct states of things. I assume it is using the local path when I am on my home network. I have two ISY's registered to UDM at 2 different physical locations. I was on the same local network as my home Polisy hosting the pg3x in question. The config I put into the plugins part of UDM (the IP address) was the local IP for my home Polisy and port 3000. The user/pass I put is the same I use to log in from my PC. From UDM click shield - select isy, I select home - it then shows all the nodes and all of them are managed by someone except for a single instance of notificatons, which is shown on the pg3x admin console as manage by someone else. I then click on the gear icon and I see it lists two choices under isy configuration, IoP and My Polyglot. If I click on IoP, then it shows all my nodes being managed and accessible. In short, it seems there is a second polyglot instance this thing is accessing. I have no idea what this polyglot instance is. I do have a PG2 running on my second ISY 994i at a separate location but it has a totally different set of nodes that don't match anything here. I used to have a PG2 on this Polisy which I recently moved over to PG3 as part of moving to PG3x. So, where in the world is this second PG instance running? I was told that PG2 would be deleted and indeed I can not access PG2 from my browser. But it seems like PG2 might still be running somewhere and that is the "My Polyglot" EDIT: I just checked the mac addresses on the two units listed under gear icon tab of plugins section of UDM. The address for "my polyglot" is mt polisy pro. The mac on the other one is my old isy 99ir I had been using to relay IR commands (though that is broken since I can't log into to change the port number to 8080). The 99i could not possible be hosting an instance of PG, yet when I click on that one, it lists off all my PG3x nodes and allows me to manage them.

I click on the admin shield icon, then plugins, then my home isy, and it reported could not get isy. 500. I canceled our of the error and put in my isy IP address user and password. It then lists all my nodes. However, the nodes all say managed by another polyglot instance except for one of them. I can log in from my computer and log out and it doesn't change. If I open one the nodes that it says isn't managed and click log it says invalid credentials 401

Against my better judgement, I switched to PG3x and now it is a mess. PG3x isn't finding Iox, and most of my programs simply disappeared.