MWareman

Personally - I spent the time (years ago) leaning the clunkiness of VI - simply because it's universally available. This has never let me down. Honestly - it's worthwhile at least learning the basics... https://developer.ibm.com/tutorials/l-lpic1-103-8/

Thanks! Via ticket, Michel has found a parsing error in UDX that looks to be the likely cause of my issue. Hopefully, it’s the cause of others issues as well... and an update takes care of it.

Before the ISY Portal existed, I used an Apache server and the proxy module to allow token based authentication to the REST API without having to reveal the admin password to third parties. I wrote it up here: https://wiki.universal-devices.com/index.php?title=Apache_Reverse_Proxy The ISY Portal is now better alternative. Certainly, less complex to get going...

You are correct. The Java based admin console uses the SOAP interface - and UDI is reimplementing everything with REST so that a native HTML5 admin UI will become possible - and the need for Java will (finally) die. I thing that this is one of the functions still only available over SOAP - but I’ve been wrong on this before as REST endpoints are being added with every release - and not all appear to be well documented yet.

I believe this is achieved via the SOAP API rather than REST....

@larryllix Did you import a custom SSL cert into Polyglot? I did - and just wanted to see if this was common between us.. Thanks! Michael.

Thank you! I just responded. Since the top suspect appears to be the MongoDB - is there a way to definitively determine this? We tried 'deleting' it and letting it recreate - but the issue was still there. Also - there appear to be no operational issues with Polyglot (other than the Polisy settings daemon not working). Wouldn't MongoDB corruption affect Polyglot in other ways? Michael.

@larryllix - Is your Polisy beeping every few seconds as well? If so - your symptoms exactly match mine...

Sent! Thanks..

Michel, Thanks for the suggestions. I do have a bigger network than /24 - so although there is no indication of any failure to connect to ISY I added that line to the .env. It did not change the status (even after rebooting Polisy). So, onto the MongoDB possibility. The status command showed MondoD was running. So - I stopped it and then renamed the old data folder. After rebooting Polisy the issue returned. I had to put back the original MongoDB directory because all the nodeservers went to an ‘Unmanaged’ State - but the fact there is no apparent behavioral difference between a virgin database and my original one suggests no corruption. The UDX binary still cannot make a secure connection to MQTT and the Polisy is still beeping. Michael.

Sorry for the delayed response. Sporadic internet access for a few days... Polyglot is 2.2.8. Also, Just now, I couldn’t logon to the web UI (the logon button did nothing) and I had to reboot Polisy to be able to logon. Michael.

Sorry - just saw this. The schedules were time based. Things like '1 hour before sunrise' would stop working - and I'd have to reboot ISY. This was on 5.0.16 (not A or B). I just ungraded all 3 to 5.0.16B and I'll report if I see the same thing or not.

The firmware 10.0.16B is reporting inconsistent version numbers. On my.isy.io - it reports 5.0.16 (ALL 3 are 5.0.16B): ISY Finder (via start.jnlp) reports 5.0.16B for all 3: And if I retrieve http://isy.domain.com/admin.jnlp and use that - the 5.0.16 admin console is run (this is with a fully cleared Java cache): ISY Finder cannot launch the admin console (this is under Iced Tea on Ubuntu): https://isy.universal-devices.com/994i/5.0.16B/insteon.jar https://isy.universal-devices.com/994i/5.0.16B/ce.jar https://isy.universal-devices.com/994i/5.0.16B/chart.jar https://isy.universal-devices.com/994i/5.0.16B/fp.jar https://isy.universal-devices.com/994i/5.0.16B/RXTX.jar java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.universaldevices.isyfinder.ISYUILoader.launch(Unknown Source) at com.universaldevices.isyfinder.ISYFinder.launch(Unknown Source) at com.universaldevices.isyfinder.ISYFinder.access$7(Unknown Source) at com.universaldevices.isyfinder.ISYFinder$8.actionPerformed(Unknown Source) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) at java.desktop/java.awt.Component.processMouseEvent(Component.java:6632) at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) at java.desktop/java.awt.Component.processEvent(Component.java:6397) at java.desktop/java.awt.Container.processEvent(Container.java:2263) at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) Caused by: java.lang.IllegalAccessError: failed to access class com.universaldevices.ui.UPnPClientApplet$27 from class com.universaldevices.ui.UPnPClientApplet (com.universaldevices.ui.UPnPClientApplet$27 is in unnamed module of loader net.sourceforge.jnlp.runtime.JNLPClassLoader @31687759; com.universaldevices.ui.UPnPClientApplet is in unnamed module of loader java.net.URLClassLoader @73a7280) at com.universaldevices.ui.UPnPClientApplet.main(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.main(Unknown Source) at com.universaldevices.client.ui.UDClientApplet.main(Unknown Source) ... 45 more If I download https://isy.universal-devices.com/994i/5.0.16B/admin.jnlp locally - and run that I get a the old ISY Finder that does not populate (expected). I hit 'add' and type http://isy3.domain.com and the USL and UUID populate: Double-clicking this launches the admin console - and I (finally) get the 5.0.16B admin UI: Main 3 questions. 1) Is start.jnlp launching for others (I assume so - and this is likely an Iced Tea / Ubuntu issue)... 2) If you clear your java cache - and launch the admin UI from http://isy.ip/admin.jnlp (replace isy.ip with your ISY IP address) - does it launch the correct version of the admin UI? 3) Does the 5.0.16B firmware contain the wrong admin.jnlp (5.0.16) on it's image? Personally - I *always* pull the admin.jnlp from the ISY itself to avoid the cloud dependency - and this is the very first time I'm getting a different version of the admin UI from /admin.jnlp than is running on the ISY itself... Michael.

Well - I reverted Polyglot to the default self-signed cert - with the same result. Putting back a (new) cert (so I avoid cert errors from the browser) results still in this: [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:init:464::initializing [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setThreadScope:153::setting scope to 2 successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:196::setting joinable to true [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:204::setting joinable successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setPriority:390::setting priority 6 successful, 0,No error: 0 [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:27::starting to look for LEDs [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:50::opening /dev/led/led1 [T:34373496832][LED:Info]../src/Device/LED/UDXLed.cpp:open:15::opening /dev/led/led1 [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:57::/dev/led/led1 registered successfully [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:50::opening /dev/led/led2 [T:34373496832][LED:Info]../src/Device/LED/UDXLed.cpp:open:15::opening /dev/led/led2 [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:57::/dev/led/led2 registered successfully [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:50::opening /dev/led/led3 [T:34373496832][LED:Info]../src/Device/LED/UDXLed.cpp:open:15::opening /dev/led/led3 [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:registerAllDevices:57::/dev/led/led3 registered successfully [T:34373496832][Audio:Info]../src/Device/Audio/UDXAudioManager.cpp:registerAllDevices:23::starting to look for the Speaker [T:34373496832][Audio:Info]../src/Device/Audio/UDXAudioManager.cpp:registerAllDevices:33::opening /dev/speaker [T:34373496832][Audio:Info]../src/Device/Audio/UDXAudioManager.cpp:registerAllDevices:40::/dev/speaker registered successfully [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:init:464::initializing [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setThreadScope:153::setting scope to 2 successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:196::setting joinable to false [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:204::setting joinable successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:start:112::thread creation successful, ID = 34373499392, 0:n/a [T:34373499392][UDXThread:Info]../src/System/UDXThread.cpp:doRun:62::starting to run [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:66::Home Dir = /var/udx, default = /var/udx [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:70::Logs Dir = /var/udx/logs, default = /var/udx/logs [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:74::Conf Dir = /usr/local/etc/udx.d, default = /usr/local/etc/udx.d [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:78::Log file = /var/udx/logs/log, default = /var/udx/logs/log [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:82::Log file = /var/udx/logs/debug.log, default = /var/udx/logs/debug.log [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:86::Global TZinfo file = /usr/local/etc/udx.d/static/tzinfo.json, default = /usr/local/etc/udx.d/static/tzinfo.json [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:89::flash read file /usr/local/etc/udx.d/.udxr.rom.tmp [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:92::flash write file /usr/local/etc/udx.d/.udxw.rom.tmp [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:95::bios write file /usr/local/etc/udx.d/.udxbios.rom [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:98::bios write file /usr/local/etc/udx.d/.udx.tpm.crypto [T:34373496832][Runtime Config:Info]../src/Config/UDXRuntimeConfig.cpp:init:101::current time info file /usr/local/etc/udx.d/tzinfo.json [T:34373496832][MongoDB:Info]../src/DB/UDXMongoDB.cpp:init:34::creating mongo client for mongodb://localhost:27017 [T:34373496832][Polyglot:Info]../src/Config/UDXPolyglotSettings.cpp:retrieveFromDB:74::successfully retrieved Polyglot settings [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: $oid [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:440::invalid int tag: __v [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: timeStarted [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:301::invalid bool tag: useBeta [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: name [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: key [T:34373496832][Polyglot:Warn]../src/Config/UDXPolyglotSettings.cpp:set:409::invalid string tag: ca [T:34373496832][SysConfig:Warn]../src/Config/UDXRuntimeConfig.cpp:init:107::failed retrieving pg config from db [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:init:464::initializing [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setThreadScope:153::setting scope to 2 successful [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:196::setting joinable to false [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:setJoinable:204::setting joinable successful [T:34373496832][SysConfig:Error]../src/System/UDXSysConfig.cpp:init:59::Cannot make a secure connection. Bailing out. [T:34373496832][HWMonitor:Error]../src/main.cpp:main:126::failed starting the SysConfig MQ [T:34373496832][Audio:Info]../src/Device/Audio/UDXAudioManager.cpp:end:15::closing ... [T:34373496832][GPIO:Info]../src/Device/GPIO/UDXGpioManager.cpp:end:15::closing ... [T:34373496832][LED:Info]../src/Device/LED/UDXLedManager.cpp:end:14::closing ... [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:89::stopping [0] running=false [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:99::destroying attributes [0] [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:89::stopping [0] running=false [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:99::destroying attributes [0] [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:89::stopping [34373499392] running=true [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:96::cancelling [34373499392] [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:stop:99::destroying attributes [34373499392] [T:34373496832][UDXThread:Info]../src/System/UDXThread.cpp:detach:448::detaching [34373499392] MQTT is on the default port: [admin@polisy /var/udx/logs]$ netstat -nab | grep LISTEN | grep 1883 tcp46 0 0 *.1883 *.* LISTEN [admin@polisy /var/udx/logs]$ It is - by default - only listening to 'localhost'. That shouldn't be an issue here though - unless the udx binary is trying to connect to the actual IP instead of 'localhost'. The Polisy itself is beeping up a storm. The udx binary keeps stopping and relaunching - with beeps issued each time..

Hi Michel, I had put a cert in place for Polyglot to use - does that affect the cert MQTT uses as well? I have not changed the port. I do have to renew that cert though. If MQTT is using the same cert as Polyglot that could explain the issue. Michael.

After installing udx: Download https://udx.s3-us-west-2.amazonaws.com/pkg/1.0.26/udx-1.0.26_4.txz sudo pkg install ./udx-1.0.26_4.txz and starting it with: sudo service udx start I am seeing this in the /var/udx/logs/debug.log [T:34373496832][SysConfig:Error]../src/System/UDXSysConfig.cpp:init:59::Cannot make a secure connection. Bailing out. [T:34373496832][HWMonitor:Error]../src/main.cpp:main:126::failed starting the SysConfig MQ And I still get stuck at the 'Please wait, getting configuration...' message....

My 5.1.16 keeps missing scheduled events - and I rely on leak sensors... Do we know if 5.0.16B is likely still this week? Michael.

I have 5.0.16 currently - and twice over the last week I’ve had to restart ISY because time based programs stopped triggering (time offset from sunset). However, I have Flood sensors likely affected by the bug. So, I’m awaiting 5.0.16B before upgrading to the latest.

I'm getting an odd error when I run 'sudo pkg update' [admin@polisy ~]$ sudo pkg update Password: Updating udi repository catalogue... Fetching meta.txz: 100% 820 B 0.8kB/s 00:01 Fetching packagesite.txz: 100% 50 KiB 50.8kB/s 00:01 Processing entries: 0% Newer FreeBSD version for package p5-HTML-Parser: To ignore this error set IGNORE_OSVERSION=yes - package: 1201000 - running kernel: 1200086 Ignore the mismatch and continue? [Y/n]: Processing entries: 100% udi repository update completed. 165 packages processed. All repositories are up to date. It appears that the package 'p5-HTML-Parser' is expecting a newer kernel than Polisy is running

Hit the ‘Send Spokens’ button..

I run Asterisk on a Pi(3). Other than rebooting for kernel updates occasionally it’s been 100% reliable - without underclocking. In total, I have several Pi’s running well (things like Nodelink, the Unifi controller, dedicated DNS servers, ElasticSearch dedicated master node etc). Sounds like either the power supply is not reliable - or you are using a poor quality SD card. Don’t cheap out of these and the Raspberry Pi will be very reliable.

If you have a room named in ISY Portal (assigned to devices) and a room of the same name in Google Home - the devices will be put into the room automatically. The room itself will not be created (to my knowledge). So, create empty rooms in Google Home then try the sync all devices.

Are you absolutely sure your initial variable assignment does not contain the ‘F’? If it does, it likely won’t work. With network and email substitutions this is common and UDI now allow to append .RAW (to get the number without any extra characters). Not sure how to do this inline though - but you could create a network rule to set the variable.

FWIW - I did the upgrade to 2.2.6 when beta - and it was seamless (other than the WiFi starting to connect automatically)

That’s what I thought. My enquiry is more about how do I disable the WiFi interface in a way that won’t break the admin UI when available. Currently, if just commented it out of the rc.conf - but that’s a change that will likely break the admin UI if I don’t reverse it.