Michel Kohanim

@waffles, Please check your error log for SMTP errors: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages#SMTP_Errors With kind regards, Michel

@Tango, The most important things are: 1. Make sure the pattern of lights upon reboot is identical to what's described here: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs.2FLights 2. If it is, then the issues is 100% network related and has nothing to do with ISY With kind regards, Michel

Also, here are some links: 1. The quick start page on our website 2. User guide on our Wiki Wtih kind regards, Michel

Hi Michael, First a little clarification on the difference between admin.jnlp and start.jnlp: - admin.jnlp is the actual Admin Console and thus you will not see the Type and Version columns (as is the case in start.jnlp) … so, isy/994i/<version>/admin.jnlp is going to bring up the Admin Console for that version - start.jnlp reads admin.jnlp and downloads correct UI and other resources based on the type of the device … so, based on the firmware version and the type of ISY, start.jnlp will go to the correct URL to download the correct version of the Admin Console Next, the ISY Portal does not understand the concept of A, B, xx after the version. This is a bug. With regards to Ubuntu, I really do not know why it does it. I think everyone should move to FreeBSD With kind regards, Michel

@Tominnh, We have been shipping! The last batch shipped was for June of 2019. We should be able to ship July and August today and tomorrow and the rest on Thursday. With kind regards, Michel

@asbril, my pleasure. Just so that everyone knows the issue: I had asked @asbril to format the SD because of many file errors he had. This said, I had forgotten to mention that he had to reinstall the firmware. That was the root cause of everything else. With kind regards, Michel

@zerop, Make a program without the If condition. In the Then turn off the outlet. Save. In the program summary tab, click on the program and choose Run at Startup. With kind regards, Michel

@asbril, You have changed your HTTPS client settings and thus the issue (cannot make a secure connection). Please make sure you follow the instructions here: Make sure your HTTPS Client Security Settings are set to TLS 1.2 and Strength of All and Verify is Unchecked by following Network Security Configuration guidelines With kind regards, Michel

@MWareman, What version of Polyglot do you have? UDX gets the certs from Polyglot's mongodb. And, as far as I know, there is no tag called "key". With kind regards, Michel

@MWareman, Missing schedules based on device states (leak sensors) or just time based schedules? With kind regards, Michel

@garybixler, thank you. Please send me your /var/udx/logs/debug.log to support@Universal-devices.com . With kind regards, Michel

@garybixler, Please do: ps -aux | grep udx and let me know what you see. With kind regards, Michel

@MWareman, This means two things: udx cannot connect to MQTT. Have you changed MQTT port or certificates? With kind regards, Michel

@garybixler, Can you please send /var/udx/logs/debug.log to support@Universal-devices.com ? With kind regards, Michel

Hi everyone, to install udx without having to worry about dependencies, please: 1. If you have already installed udx: sudo service udx stop sudo pkg delete udx 2. Download https://udx.s3-us-west-2.amazonaws.com/pkg/1.0.26/udx-1.0.26_4.txz 3. Go to the directory in 2: sudo pkg install ./udx-1.0.26_4.txz With kind regards, Michel

@garybixler, you can click on the reset button on the front (through the little hole in the middle), you will hear a beep, and polisy will go back to dhcp. With kind regards, Michel

Thank you all. I am going to include these dependencies in the package. With kind regards, Michel

@Bumbershoot, thank you. This is odd as it should have come with pkg upgrade. Did you try that? If so, can you please do: sudo pkg install libbson With kind regards, Michel

@gviliunas, Yes, sudo service udx start If it keeps beeping, then sudo service udx stop. With kind regards, Michel

@gviliunas When you start udx, do you hear a beep or beeps? With kind regards, Michel

All, It's best to do: sudo pkg update && sudo pkg upgrade first. Then install udx. With kind regards, Michel

@gviliunas, Did you install udx? With kind regards, Michel

@Bumbershoot, Yes, you need the udx package for this to work: sudo pkg install udx. With kind regards, Michel

@DennisC, Since we are doing everything in a modern web based (HTML/JavaScript) way for Polisy, having a mobile app reuse the same might be an option. With kind regards, Michel

Hello everyone, We found a few last minute bugs most of which have already been fixed. So, although we could not ship today, but we can definitely ship by no later than Friday. @larryllix, to answer your questions, as you may know, Polisy is a brand new platform, OS, and completely different than ISY. The most important difference between ISY and Polisy is the difference between RTOS and a Unix based system. So, when we started this journey, we had to make sure that the design is a) extensible and modular b) light weight enough so that both ISY and Polyglot can run on the same platform and c) conducive to piece by piece integration and d) modern UI that allows configuration of the hardware and d itself. i.e. we decided against a big bang approach. Given the history, the tasks were: 1. Deploy our own package repository, build process, and packages. This way, not only Polisy is extensible and modular but also all packages are built and tested exclusively for Polisy 2. Design a modern and secure communication interface for configuring the hardware. We call this UDX which is a light weight and secure service layer to the hardware and OS. UDX currently does network configuration, WiFi configuration, date/time zone configuration, checking for upgrades, upgrading the system, managing the serial ports, GPIO, reset switch, logs/rotations, etc. All this is done through MQTT using certificate authentication (even though they run on the same box). So, the only way anyone can communicate with UDX is to have access to the certificates 3. Enable the integration of Polyglot UI with UDX through MQTT 4. Migration of ISY: a. Extending UDX to include the abstraction layer for ISY b. Connecting physical ISY through the abstraction layer so that a modern UI can be hosted on Polisy as a proxy to ISY c. Porting/migrating ISY using the abstraction layer and thus removing the physical ISY So, where are we now? 1. Done 2. Mostly done 3. Done for everything in #2 4a. 85% done. Almost all RTOS high level artifacts, such as Mailbox, Queue, Task, Flag, etc. have already been designed, developed, and tested with test programs 4b. 0% done 4c. 0% done So, in addition to full fledged Polyglot (minus bluetooth support as it has proven more difficult than anticipated), what you will be testing, and what's being shipped is Polyglot + Polisy configuration in one UI allowing you to configure and manage the system (#2 and #3). And, of course, the beauty is that once deployed, upgrading everything (including Polyglot) will be as easy as clicking a button (no more sudo pkg update && sudo pkg upgrade). Even easier than ISY since Polisy will download, decompress, and install everyting on its own. Once this infrastructure is in place, all our efforts will be spent on 4a, 4b, and 4c. With kind regards, Michel