apostolakisl

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.

Is the Alarm Relay connection an IP connection or phone connection?

@Geddy thank you for the info. Does @Panda88 know about this?

Stopped getting any data from the car. I tried restarting, then rebooting polisy then deleted and readded node. I get the following error 2024-01-25 13:26:01,163 Thread-7 udi_interface ERROR TeslaCloudEVapi:teslaEV_GetIdList: Error getting vehicle list 2024-01-25 13:26:01,164 Thread-7 udi_interface ERROR TeslaCloudEVapi:teslaEV_GetIdList: Trying to reconnect 2024-01-25 13:26:02,051 Thread-7 udi_interface ERROR TeslaEVController:createNodes: Exception Controller start: object of type 'NoneType' has no len() It shows that it is connected and I get the Tesla Node in the admin console but it says zero vehicles.

Haven't touched the Elk itself or the nodeserver in ages. Yesterday, noticed an exclamation mark next to Elk outputs on the admin console. I was still controlling Elk from ISY fine. I checked the node server, it said I had an error from a wrong passcode (which wasn't wrong). Also said I had an update. I did the update and it wouldn't work at all. I then rebooted polisy completely and it still doesn't work at all. I try to start it and it won't start. I did recently update ISY and Polisy firmware to the latest. I really should learn my lesson and stop updating things. Also, my Tesla node server says it is working, but there is zero data showing up in the admin console. Not sure if these have anythign to do with each other. Other nodes seem to be working. EDIT: Turns out the Tesla issue is that the api changed, so not related. And here is the log 2024-01-25 13:21:16,770 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-01-25 13:21:16,772 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-01-25 13:21:16,773 MainThread udi_interface INFO __init__:<module>: User=polyglot 2024-01-25 13:21:16,774 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot 2024-01-25 13:21:16,775 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9023863_16 2024-01-25 13:21:16,775 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6Mzg6NjMiLCJwcm9maWxlTnVtIjoxNiwibG9nTGV2ZWwiOiJXQVJOSU5HIiwidG9rZW4iOiIreUNYQUh0VTgzdncpOT10IiwibXF0dEhvc3QiOiJsb2NhbGhvc3QiLCJtcXR0UG9ydCI6MTg4OCwic2VjdXJlIjoxLCJpc1BHM3giOmZhbHNlLCJwZzNWZXJzaW9uIjoiMy4xLjIzIiwiaXN5VmVyc2lvbiI6IjUuMy4zIiwiZWRpdGlvbiI6IlN0YW5kYXJkIn0= 2024-01-25 13:21:16,776 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-01-25 13:21:17,666 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-01-25 13:21:17,968 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-01-25 13:21:20,186 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-01-25 13:21:20,190 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-01-25 13:21:20,190 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-01-25 13:21:20,191 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-01-25 13:21:20,191 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-01-25 13:21:20,191 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.6 Starting... 2024-01-25 13:21:20,198 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2024-01-25 13:21:20,198 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9023863_16/./elk-poly.py", line 10, in <module> 2024-01-25 13:21:20,200 MainThread udi_interface ERROR udi_interface:write: from nodes import VERSION,Controller 2024-01-25 13:21:20,201 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9023863_16/nodes/__init__.py", line 3, in <module> 2024-01-25 13:21:20,202 MainThread udi_interface ERROR udi_interface:write: from .BaseNode import BaseNode 2024-01-25 13:21:20,203 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9023863_16/nodes/BaseNode.py", line 7, in <module> 2024-01-25 13:21:20,204 MainThread udi_interface ERROR udi_interface:write: from const import NODE_DEF_MAP,ELK_TO_INDEX 2024-01-25 13:21:20,205 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9023863_16/const.py", line 1 2024-01-25 13:21:20,205 MainThread udi_interface ERROR udi_interface:write: 233: "Invalid", 2024-01-25 13:21:20,206 MainThread udi_interface ERROR udi_interface:write: ^ 2024-01-25 13:21:20,207 MainThread udi_interface ERROR udi_interface:write: SyntaxError 2024-01-25 13:21:20,207 MainThread udi_interface ERROR udi_interface:write: : 2024-01-25 13:21:20,208 MainThread udi_interface ERROR udi_interface:write: illegal target for annotation EDIT 2: @Jimbo.Automates I tried uninstalling and reinstalling and it still won't run. It says it is starting, and then after a few seconds it stops.

The time to have done this was while under construction. Running wires after the walls are up is a whole lot more work. You can go with an all wireless system at this point, certainly a pretty basic DIY job, but then you will have to maintain all the batteries. You can still run wires, but it often requires some cleverness, special tools, and a certain level of skill.

For smoke detectors you would want a proper security panel to manage them and then link that panel to Eisy. Your local code may affect your options. If you are out in the country, you may not have to worry about local codes which may not exist. Anyway, some code requires a 120vac smoke system and others will allow low voltage setups. When I built my house I was allowed to use low voltage smokes that are all tied into my Elk panel which then links to ISY via a node server. There are two wire and four wire smokes. I like the four wire setup where power and signal are separate. DSC would be a more cost effective way to do that if you don't care for all the Elk bells and whistles. I haven't ever hooked smokes to a DSC system but I'm sure they have provisions for it. If I were doing it again, I don't know that I would bother with Elk since all that stuff is managed so well from ISY. If you are stuck with 120vac smokes, there may be a dry contact that you could tap into and then hook that to an IO link to bring the status of the smokes into Eisy. I have an all electric house and didn't bother with any CO detectors.

As mentioned, you can not turn KPL buttons on directly from a program, however, if a KPL button is in a scene and a program turns that scene on, the KPL button turns on. So, you need to have a scene that the KPL button is in, even if nothing else is in the scene. Then using the same program that turns on your Bond Bridge, have it also turn that scene on, and similarly for turning it off.

yes, envisalink won't affect your phone dialer. I actually have my dsc connected to polisy via envisalink and I use alarm relay via a phone dialer. If you want to use envisalink to report via IP to alarm relay and to connect to eisy, I don't think that will work. Though you may be able to connect two envisalink units, not sure.

The sooner they get a local api the sooner I buy their products.

@Panda88 It has been a year since I last asked and the answer was that a local api might be in the works. Wondering if there is any new info. Thanks

Elk works great. But if you don't need all the bells and whistles, DSC works very well too for far less money. I have one of each and both integrate very nicely with ISY.

And it integrates with ISY using the wireless tag node server. For about $100 you could have the tag, the hub, and the node server. Then for roughly $25 ea you can keep adding more tags for whatever else, like outdoor temp/humidity, other fridges, water detection, etc. I have done this monitoring some walk-in units at my church and used the hard wired version so I don't have to mess with the batteries. I then have a program on ISY that sends me an alert if the tag hasn't updated the temp in more than 45 minutes. You could do the same but would have to drill a tiny hole in the side of your fridge to run the wire. It is powered off of 5v USB jack but you can cut the wire so you just need to drill a 1/8 inch or smaller hole and then splice the wire back together. You would think a big metal box like a walkin cooler would kill the signal, but it doesn't. Though it definitely attenuates it. The program below runs at startup and just keeps resetting itself if the temp or humidity changes. Freezer Online - [ID 009F][Parent 009D][Run At Startup] If 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Temperature is 0.0°F Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Temperature is not 0.0°F Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Humidity is not 0.0% Or 'Walk Ins / TGOC Walk-Ins / TGOC Freezer' Humidity is 0.0% Then Wait 45 minutes Repeat Every 1 hour Send Notification to 'Lou and Stuart' content 'Freezer Monitor Offline' Send Notification to 'Denis Phocas' content 'Freezer Monitor Offline' Else - No Actions - (To add one, press 'Action')

As was mentioned, you usually do not put refrigerators on GFCI circuits, but that is a separate point. What you are basically asking for is to monitor for the presence of power. If you want to do that with Insteon and have an immediate report of loss of power, well, there isn't an Insteon device that does that. However, you could make one. I would suggest using a small electromagnet and an Insteon door close sensor. Into another outlet on the same circuit as the fridge, plug in the electro magent. Put the battery powered Insteon device next to that magnet. If the magnet shuts off, then the door sensor will show "open" status. Since the Insteon device is battery powered, it will be able to immediately communicate the power loss. The electormagnets I am thinking of run on 12vdc so you would plug in a 12vdc wall wart and then connect that to the magnet power supply. The magnet I show here pulls 4w, so you might hunt for a less powerful magnet, or perhaps you could try powering it off of lower voltage.

I use Blue Iris software to monitor all my cameras and the Blue Iris node server. I find that for the price Foscam has some nice cameras. I have had a number of the cameras die, but only after many years of use and they are so cheap that I don't get upset about buying replacements. Blue Iris does require an always on PC but it is very capable software.

I have Levelor blinds that don't have an open API so you can't make a PG3 node unless you want to try to reverse engineer it, if that is even possible. It does however link to Alexa. Alexa has a skill that lets you trigger events with a url. This skill is free and as far as I can tell lets you make unlimited url's. Once you have a url trigger for an alexa scene, you can use the ISY network resource to issue that url. It is limited in that it won't report status of the blind and you can only trigger the blind to go to one spot per url. It works just fine for a simple open/close command. Pearl here, it seems that you need to use the primary account login for Alexa to get it to work. https://trigger.esp8266-server.de/ EDIT: Here is how the network resource will look in isy.