giomania

Correct.

I am currently using a Polisy Pro, and IoX v.5.4.5, and am wondering if I should update to IoX v.5.5.2 in preparation for migration to eisy? Background I read the various posts, and understand that the migration tool to go from Polisy PG3 node servers to eisy PG3 is not ready, so I am just waiting until it is. I just want to be able to migrate both the Insteon devices and PG3 node servers at one time. I am currently on IoX v.5.4.5, and while the eisy user guide states that v.5.4.3 is required, I know there might be a caveat in that we should migrate from the same exact version. Thanks for any insight. Mark

I don't think this is totally related to this issue, but I upgraded to Ecobee PG3 several months ago, use Auto all the time, and had subsequently set up programs to adjust the cool set point down as the temperature from OpenweatherMap went up. This worked fine in the beginning, but then it stopped working. If I make the adjustment to the temperature on the GUI of the thermostat, the change sticks until the next scheduled change in the program schedule. The failure point behavior for my program is that the set point would change, but then within a minute, it would revert back to the auto temperature setting. In case there is a problem with the program logic, here is an example. Thanks. Mark

Yes, I restarted the admin console, and it is still displayed. Interesting. Thanks. Mark

I just installed MagicHome Polyglot v3 on the Polisy. Everything works fine, but the device in the ISY Admin Console shows "Writing" state constantly. Is this normal? Thank you.

Good afternoon, I have a Polisy Pro purchased in June, 2019 (received December, 2019). I am following this guide, and I am stuck on this part to update. When I enter the first command after rebooting: cat /usr/local/etc/udx.d/static/update13.sh | sudo bash The response is: No such file or directory. My current release retrieved via "unam -a" is: FreeBSD polisy 12.2-RELEASE-p6 FreeBSD 12.2-RELEASE-p6 r369564 POLISY amd64 I am not sure where to go from here. Thanks for any guidance. Mark

I did not write the code, an AVS Forum member did, and he is using it on a RPi. My initial thought was to get a Pi and copy his code over, but then I was wondering if I could run it on Polisy, so I posted here. I'm not sure it makes sense to get a Pi only for this, function, but I will think about it. Realistically, it is probably over my pay grade, since I do not even know where to enter the syntax. That said, I have not searched for any step-by-step guides that may exist. Now if someone made a Polyglot where you could just paste in the code, then I could probably manage to figure that out. Thanks again for the input.

Thanks Larry, Sounds like it is doable, but unfortunately not possible for me to do this on my own, as I would have no idea without a step-by-step, lol. Mark

I realize this is probably a dumb question, but I was wondering if it is possible to run Python scripts on the Polisy? A member of AVS Forum wrote and shared basic script that retrieves the numeric volume level from an Audio/Video Processor (The Monolith HTP-1) and displays the volume level on a Video Processor (the Lumagen Radiance Pro). The HTP-1 does not have an OSD, and if the unit is behind a cabinet door, the display on the unit cannot be seen, so this is a very handy tool. He runs this script on a Rasberry Pi, but I figured this might work on the Polisy Pro. I looked at the NodeServer store, and if there is something in there that would facilitate this, I missed it. Here is the post, for any interested in the provenance, and below is the code he wrote. Thanks for any input / advice. Mark Python: # A very basic example showing how to do # Lumagen OSD volume messages from HTP1 using Python 3.7 # Probably very bad. But it does work. import asyncio import websockets import json import re import time import serial # edit to be host name / IP address of HTP1 htp1ip = "192.168.10.185" global volume volume = 0 # This function actually does the listening for JSON on websockets, # working out if it is a volume message and setting it if it is async def htp1(): print ("start htp1") global volume uri = "ws://" + htp1ip + "/ws/controller" async with websockets.connect(uri) as websocket: while True: message = await websocket.recv() if message.startswith ("msoupdate ["): # strip the "msoupdate " from the returned message message = message[10:] jsonlist = json.loads (message) for jsondict in jsonlist: # if this was a volume message, set the volume value if jsondict['path'] == '/volume': volume = jsondict['value'] await asyncio.sleep(0.01) # This function sends simple OSD messages to the Lumagen. # It is lazy and sets the OSD colours every message as that # avoids dealing with any messages from the Lumagen. async def lumagen (): print ("start lumagen") global volume prev_volume = 0 ser = serial.Serial('/dev/ttyUSB0',9600,timeout=0.1) while True: if prev_volume != volume: prev_volume = volume osdStr='ZY4180000000\r\n' ser.write(bytes(osdStr,'ascii')) osdStr='ZY4181FFFFFF\r\n' ser.write(bytes(osdStr,'ascii')) osdStr='ZY4182000004\r\n' ser.write(bytes(osdStr,'ascii')) ostring = str(volume) ostring = ostring + "\n" ostring = "ZT1" + ostring ser.write(bytes(ostring,'ascii')) await asyncio.sleep(0.01) # main loop, if there is an exception sleep for 5s and try again. async def main(): print ("main loop") while True: try: taskhtp1 = asyncio.create_task (htp1()) tasklumagen = asyncio.create_task (lumagen()) await taskhtp1 await tasklumagen except: print ("An exception occurred. Retry in 5 seconds") time.sleep (5) asyncio.run(main())

Thank you very much. I don' have a Z-Wave menu, so I will upgrade the firmware.

I decided to just check on the last few updates, since I am on 5.0.16C. It seems, based on my (limited) research that the releases have been primarily focused on Z-Wave. Since I am not using Z-Wave, there is no need to upgrade? Thanks for any guidance. Mark

That sounds like what happens to me once in a while and the fix is in their wiki; you have to delete some files to get it working again. give it a shot. Sent from my iPad using Tapatalk Pro

Update: Fixed! I used some different keywords to search, and found another thread that prompted me to use some different keywords, and I found another thread, which led to a post from @Michel Kohanim with the solution that fixed the issue. Since I only use Windows defender, and the Java was running, I knew it wasn't the antivirus issue, but I do run multiple monitors, so found the files noted in the Wiki and deleted them, and I am back in business. I guess the lesson is to describe the symptoms in the Google search, and it probably would have brought me directly to the solution. The question is why did this happen all of a sudden, but I guess that is Windows for you. ? Anyway, for reference: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Closes_Automatically With kind regards, Michel Admin Console Minimized/Invisible and Cannot be Restored This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.* file patterns: udi_tree.state udi_frame.state udi_pgm.state udi_finder.state udi_launcher.state

Thanks for the replies. Unfortunately, neither solution worked for me. The symptom is that when I launch "Start.jnlp" from the desktop, the "UD" icon appears, and then disappears, but in task manager, the Java Web Launcher (32 bit) is running. Here are the steps I took: I uninstalled Java using the Java exe, and the remove option. Then I restarted the computer Then I reinstalled Java, restarted again, and then tried launching it again (fail) Next, I added the ISY to the Java Control Panel -> Security sub-tab -> Exception Site List -> add my ISY's IP Address as a URL (i.e. http://192.168.1.100)

I am suddenly unable to launch the Admin Console using Java 1.8.0_251 I searched, and all the threads are old. I cleared the Java cache and even tried reinstalling it, but no dice. I recently upgraded from v4.7.3 to v5.0.16C, and was able to log in after the upgrade. Fixing my scenes...that will be another post, LOL. Thanks for any assistance. Mark

DOH! I didn’t notice there was a dash in universal devices. Now, what was that I was saying about bonehead mistakes? [emoji6] Sent from my iPhone using Tapatalk Pro

Thanks. I emailed support and hopefully this isn’t some bonehead issue of my own making. [emoji3166] Sent from my iPhone using Tapatalk Pro

Hi Michele, Yes, both devices are on the same subnet. I use Ubiquiti UniFi, and I did some rearranging of the managed switch the policy is connected to prior to installation yesterday, but I went through all the ports on the switch to make sure they were on the same network. I noticed in the wiki that the ISY needs to be on version five something and I’m still on four something, but I figured that would not affect the initial policy set up. Thanks. Mark Sent from my iPhone using Tapatalk Pro

I just received my Polisy Pro, and it booted up fine with the seemingly normal beep sequence. It is on my network with a DHCP-assigned IP address, but I cannot connect to it either with the hostname (polisy) or the ip address. I am not sure what is going on. I tried Chrome and Edge, but received the same message on both: This site can’t be reached polisy’s server IP address could not be found. Try running Windows Network Diagnostics. DNS_PROBE_FINISHED_NXDOMAIN

The irrigation module factors in the current EvTo, which I’m assuming factors in the rain for the prior day. my basic program is set to run if EvTo is over a certain amount and it’s going to rain less than a certain amount, then irrigate. Sent from my iPhone using Tapatalk Pro

Yes I did mean the irrigation module. Sent from my iPhone using Tapatalk Pro

Thanks for sharing. I only irrigate in the early morning (starts at 3:15 AM) because I read that when you water at night you can have an increased chance of mold / disease issues. However, that may have been based upon my 100% Kentucky bluegrass turf. I also only irrigate based upon the irrigation requirement as dictated by the weather module, which I figured was the point of paying for that? I also read that you’re supposed to water once and deeply, vice frequently. This means that ideally you would only water once a week for the specific amount that the particular turfgrass type needs. I remember correctly I think it’s 1 inch of water per week generally. My soil type can’t handle more than .25” before run-off occurs, so that is as “deep” as I can water in one cycle. I’ve had this going out for around three years and it’s working fine. It has saved me a whole bunch of money in water, which is very expensive here. Mark Sent from my iPhone using Tapatalk Pro

Perhaps he was posting that the bulbs can’t be used in “the upside down”? [emoji41] Stranger things season 3 comes out tomorrow after all! Sent from my iPhone using Tapatalk Pro

How does this work exactly? Is that via Polyglot? Thanks. Mark Sent from my iPhone using Tapatalk Pro

I have never used polyglot but with announcement of the new hardware I did some quick research to see what’s available in polyglot. I found Ecobee and AV Remote items of primary interest, and others with a lesser interest, so I decided what the heck. UDI is a great company and I need to use polyglot eventually so why not get the appliance designed for that, which will make my life easier. I am in for the Pro model. Mark Sent from my iPhone using Tapatalk Pro