mbking

@Michel Kohanim, I've been clearing the log before initiating a few events to see if the date and time is correct and it is still giving me the same results. To be clear, I'm looking at the Log file under Tools in the Admin Console for the ISY on Polisy. I took a quick look at the Error Log and it seems to have the correct date and time. I've verified that I have Polisy v5.0.4 firmware per the display under Help->About in the Admin Console. While experimenting with this issue this afternoon, I noticed that while the date and time were correct in the Admin Console display, my time zone was not. The Admin Console showed Los Angeles and my Polisy setting is Austin, TX. The sunrise and sunset where off as well. I went into the Polisy Console and changed my location to San Antonio, TX and then back again to Austin, TX. I then did a "sudo service isy restart" and now the location and sunrise and sunset are correct in the Admin Console for ISY on Polisy. I have the one dimmer controlled by a single program and that program fires at the correct times in the If statement. It's just the time stamps in the log file that I'm having issues with. Anything else I should try to fix the time stamps? Mark

Yes, I’m on 5.0.4. Sent from my iPhone using Tapatalk

I'm seeing some unexpected behavior in the ISY on Polisy log file as well. Not only am I seeing some X10 activity I don't expect to see, but my time stamps are incorrect. I have one dimmer added with a single program set to turn it on and off. That is working as expected. Not sure why the time stamps are incorrect, though. Times in the Admin Console look OK. I forgot to factory reset the dimmer switch before adding it, so I will do that to see if it eliminates the X10 entries. I've received some items from Smarthome that are not factory reset and this could explain the X10 entries. Any thoughts on the time stamp issue?

Not that this will answer the question as to whether Smathome will continue to sell a PLM, but I just got a new serial PLM under warranty, even though the website lists it as Sold Out. It did take several days for them to OK the replacement, but once they did, the new one shipped out immediately. I suppose Smarthome has a supply in reserve. The version is 2.6. I'm going to hold onto the old one and replace all the caps. It has started losing its link table and for me, that's been the first sign of impending failure.

Update was successful. I did not get all the beeping patterns that others have reported, but everything is up-to-date and running normally. Thanks to @Michel Kohanim and the rest of the UDI team for such a smooth update process.

@Michel Kohanim, thanks for getting back on this. Been held up with other priorities, so I haven't tried it yet. I did have a question, though. If this process updates your existing node servers to use Python 3.8, do you need to avoid adding or updating existing node servers until all node servers in the store are updated to use Python 3.8?

Any word on whether it's safe to update Polisy now after issues with OS upgrade to 13?

I'm using the ELK node server in Polisy and it works really well in UD Mobile.

@Javi, couldn't get the above to work. I think I can switch between Mobilinc Connect and ISY Portal within the ISY with relative ease, but we'll see. What's the best way to request feature enhancements in UD Mobile? There are a few things I can do in Mobilinc X that I can't do in UD Mobile, but UD Mobile has the edge in it's implementation of the node servers.

I'd like to test UD Mobile using a remote connection (ISY Portal), but I'm still using Mobilinc Connect. Anyone have any experience switching between the two? Any issues switching back and forth? I want to maintain both for awhile to see how node servers get implemented in Mobilinc X. The node server implementation in UD Mobile is really nice to have.

@Jimbo, I'm running 2.2.11 with a 2.2.9-5 Front End and my log is still not updating. My FreeBSD is 1.2 P3. Am I missing something? -Mark

Thanks for the heads up, Jimbo.

@gviliunas Thanks for the reply. Those are the same lines I see at the end of my overall log. I'm going to hope as well that 3x takes care of it. Thanks again. -Mark

Using the following command, "curl -s https://pkg.isy.io/script/update121.sh | sudo bash", I updated Polisy to FreeBSD 12.2 based on some of the earlier discussions in this post. I too had seen a large number of update files and then suddenly the Update Check stopped working. Rebooting got it working for awhile, but it always returned 0 updates. I thought this FreeBSD update might help. The update completed normally and I'm now showing FreeBSD 12.2. I believe the release is P3. After rebooting Polisy, my 4 node servers appear to be working normally and I am getting the expected logs in those servers, but my overall Polisy log is no longer updating. The last lines in the log were posted about the time of the reboot after the FreeBSD upgrade. Has anyone else seen this or have any ideas how to correct it? Thanks. -Mark

I upgraded successfully yesterday from 5.0.16C to 5.3 on an all Insteon system. No errors or issues that I can see so far. Many thanks to the UDI team. Looking forward to some of the other exciting changes coming in the future. Mark

I have successfully configured my Polisy Pro and have been online with it for about 48 hours now. I started the transition with my ISY at 5.0.16B and Polyglot running on a RPi at version 2.2.3. I have 2 node servers: Hue Emulator and Ambient Weather. The process followed the installation guidelines with a few exceptions. 1) I wasn't sure if I should update Polyglot to the latest version, but others appeared to do that before installing Polisy and it made sense to do so. I wanted to be able to download and restore my node servers to Polisy. I allowed beta versions of the firmware and Polyglot was successfully updated to 2.2.8. I downloaded a backup of my Polyglot configuration. 2) Since I have a program on the RPi that sends the equipment room temperature to the ISY, I needed to keep the RPi running without Polyglot running. To do this, I disabled the service with the following commands: sudo systemctl stop polyglot-v2 sudo systemctl disable polyglot-v2 I shutdown the RPi to be on the safe side and then restarted after Polisy was up and running. 3) I reserved an IP for Polisy. 4) Followed startup instructions for Polisy. Light sequence for me was basically as described with a few differences I didn't capture. Once left light was steady and no beeping, I used https://polisy_ip_address to login. I'm on Safari, so as I ran into with the RPi, I couldn't connect to Polisy. Got the "This Connection Not Private" message. Safari would not let me ignore the message. The solution was to select "Details" in the error message. A Certificates icon is displayed for Polisy. Drag the icon to the Desktop. The file is Polisy.cer. Open the Keychain app. Drag Polisy.cer to the Certificates folder in Keychain. Once there, highlight the file and select Get Info. Open the Trust folder and select Always Trust for all items. Now I can login to Polisy. 4) Updated software on Polisy. As Michel says, be patient. I wasn't. There isn't any feedback while the update process is working. I stepped away for awhile. You do get a complete message at the end of the update. Reboot Polisy. 5) Polisy did not automatically find my ISY. I added it manually. 6) Restored Polygot configuration with the backup I saved earlier. Both node servers showed up and connected. 7) The Ambient Weather node started working without an issue. The Hue Emulator was connected to the ISY, but my Harmony remotes were not communicating with the Emulator. The solution was to go into each remotes configuration, select the Hue device to edit, select Re-Pair Bridge, and then Refresh. Control from the remote was restored. All in all, this was a relatively painless process with a few unexpected bumps in the road. Hopefully others who are using a Mac can benefit from my experience. And if there was an easier way to do what I did, I'd be happy for the advice.

Lee, Thanks for your help. You described what I did and I'll try your suggestions later tonight. I assume then that Insteon devices do not broadcast their status when their state changes. Thanks again. I'll post the results tomorrow.

Do Insteon modules broadcast their status automatically when their state changes? I am not getting module status in my ISY-99i after installing an EZX10RF module to receive the X10 commands from my Palm Pads and control the Insteon modules linked to it. That setup works fine, but I don't see the status of these lights change in the console or on my MobiLinc app. I don't see any status information in the Event Log either. I can control the lights using the console controls and status is displayed correctly then, but any external control of the lights is not reflected as a status change in the ISY. I have recently installed version 3.3.10 of the software. I also can't come up with a good program to query the modules automatically. Querying the manually does give me the correct state. I'm a bit of a novice at understanding all the details here, so any help would be appreciated. Thanks!

We're building a new home and I'm looking to expand my home automation system to include the thermostats. I think we're going with the Venstar T5800 and I'd love to see support for it on the ISY-99i. I'm adding my vote.

I was trying to update to 2.7.13 from my iMac and getting the failures I posted earlier. I dusted off a Windows PC and the update worked. I wonder if the latest update to Safari is the source of the problem. I really don't want to be dependent on a Windows PC to use the ISY. I'm on 2.7.13 now, but I'm hoping a solution can be found so I can use the iMac in the future.

I'm having the same problems with Invalid Length when updating from 2.7.12 to 2.7.13. I've updated several times and have never had this issue before. I got to 13% to first time. After cycling the power on the ISY and clearing my JAVA cache, I got as far as 17% before it failed. If I try again, it goes to 13%. I'm not sure what's different now from the previous updates that worked so well.