DennisC

@bpwwer It looks like PG3 on v3.1.20 is not showing messages when there is an update ready for a node server. I just checked after being told there was an update to the Elk node server. I found there were two node servers that had updates available and I had to go to Purchase - Reinstall to get the updates. Stopping and starting the node server didn't trigger the update.

Thank you, I completely forgot about that, sorry. When I was there this morning, there was no update message. I just checked again and there was still no update message. I went to purchases and did a reinstall and now I am on 3.7.0. Here is what I get in the log now: 2023-04-14 18:05:02,780 Command udi_interface INFO Area:cmd_display_message: display_message(1, False, 0, "Temp 76.14F", "Hum 35.08%") 2023-04-14 18:05:17,224 ELK-7665 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:1005186140423110 elkm1_version:5.2.10 xep_version:2.0.34 remote_programming_status:0 system_trouble_status: temperature_units:F user_code_length:4 type=<class 'elkm1_lib.panel.Panel'> cs={'real_time_clock': '1005186140423110'} 2023-04-14 18:05:17,225 ELK-7665 udi_interface INFO Controller:callback: real_time_clock=1005186140423110 2023-04-14 18:05:47,243 ELK-7665 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:4005186140423110 elkm1_version:5.2.10 xep_version:2.0.34 remote_programming_status:0 system_trouble_status: temperature_units:F user_code_length:4 type=<class 'elkm1_lib.panel.Panel'> cs={'real_time_clock': '4005186140423110'} 2023-04-14 18:05:47,244 ELK-7665 udi_interface INFO Controller:callback: real_time_clock=4005186140423110 2023-04-14 18:06:17,262 ELK-7665 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:1006186140423110 elkm1_version:5.2.10 xep_version:2.0.34 remote_programming_status:0 system_trouble_status: temperature_units:F user_code_length:4 type=<class 'elkm1_lib.panel.Panel'> cs={'real_time_clock': '1006186140423110'} 2023-04-14 18:06:17,264 ELK-7665 udi_interface INFO Controller:callback: real_time_clock=1006186140423110 2023-04-14 18:06:47,281 ELK-7665 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:4006186140423110 elkm1_version:5.2.10 xep_version:2.0.34 remote_programming_status:0 system_trouble_status: temperature_units:F user_code_length:4 type=<class 'elkm1_lib.panel.Panel'> cs={'real_time_clock': '4006186140423110'} 2023-04-14 18:06:17,264 ELK-7665 udi_interface INFO Controller:callback: real_time_clock=1006186140423110 2023-04-14 18:06:47,281 ELK-7665 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:4006186140423110 elkm1_version:5.2.10 xep_version:2.0.34 remote_programming_status:0 system_trouble_status: temperature_units:F user_code_length:4 type=<class 'elkm1_lib.panel.Panel'> cs={'real_time_clock': '4006186140423110'} 2023-04-14 18:06:47,282 ELK-7665 udi_interface INFO Controller:callback: real_time_clock=4006186140423110 2023-04-14 18:06:55,594 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV1 to 1 UOM 25 2023-04-14 18:06:47,282 ELK-7665 udi_interface INFO Controller:callback: real_time_clock=4006186140423110 2023-04-14 18:06:55,594 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV1 to 1 UOM 25 2023-04-14 18:07:17,290 ELK-7665 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:0907186140423110 elkm1_version:5.2.10 xep_version:2.0.34 remote_programming_status:0 system_trouble_status: temperature_units:F user_code_length:4 type=<class 'elkm1_lib.panel.Panel'> cs={'real_time_clock': '0907186140423110'} 2023-04-14 18:07:17,290 ELK-7665 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:0907186140423110 elkm1_version:5.2.10 xep_version:2.0.34 remote_programming_status:0 system_trouble_status: temperature_units:F user_code_length:4 type=<class 'elkm1_lib.panel.Panel'> cs={'real_time_clock': '0907186140423110'} 2023-04-14 18:07:17,292 ELK-7665 udi_interface INFO Controller:callback: real_time_clock=0907186140423110

Hi @Jimbo.Automates, I was checking PG3 today and noticed some warnings repeating in the log. I checked my Elk system and the Elk log and all was fine. Not sure what any of the following means, do I need to do something: 2023-04-14 12:46:17,360 ELK-2691 udi_interface WARNING Controller:init_isy: pyisy_version=2.1.6 2023-04-14 12:46:17,361 ELK-2691 udi_interface INFO Controller:init_isy: ELK Controller: got isy=<udi_interface.isy.ISY object at 0x803cd3100> pyisy=<pyisy.isy.ISY object at 0x803ceea00> pyisy.connected=True 2023-04-14 12:46:17,362 ELK-2691 udi_interface WARNING Controller:sync_complete: ELK Controller: No node address or name match for 'Outdoor Pole_Wa' 2023-04-14 12:46:17,363 ELK-2691 elkm1_lib.notify ERROR notify:notify: 'bool' object has no attribute 'address' Traceback (most recent call last): File "/var/polyglot/pg3/ns/000db952c01c_2/elkm1_lib/notify.py", line 39, in notify observer(**notify_parameters) File "/var/polyglot/pg3/ns/000db952c01c_2/nodes/Controller.py", line 538, in sync_complete if node.address.endswith('_'+default_address): AttributeError: 'bool' object has no attribute 'address' 2023-04-14 12:46:37,628 ELK-2691 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:3146126140423110 elkm1_version:5.2.10 xep_version:2.0.34 remote_programming_status:ElkRPStatus.DISCONNECTED system_trouble_status: temperature_units:F user_code_length:4 type=<class 'elkm1_lib.panel.Panel'> cs={'real_time_clock': '3146126140423110'} 2023-04-14 12:46:37,629 ELK-2691 udi_interface INFO Controller:callback: real_time_clock=3146126140423110 2023-04-14 12:46:38,236 Thread-6196 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete

I'm seeing the same thing and the correction worked fine.

As stated by others, you are limiting the amount of assistance we can offer. As @MrBill indicates, knowing what the variables are doing, how the programs are written, and what might have been captured by the logs is important. With so little information, I am guessing here, but the Pushover node server allows you to set the number of retries and an expiration field, what do you have these set at?

Everything said above is good advice. I migrated from Polisy to eisy in early March and I wanted to keep my Polisy ready to go in the event the migration had issues or failed. Therefore, I elected to use a new USB PLM I already had. My experience was the upgrade to eisy and the new PLM went without a hitch. The only manual intervention I had to do was with ZWave and what is spelled out in the documents (resaving programs & network resources).

To post a program, right click on the program name and select "copy to clipboard" all the way at the bottom. Then post the result here. It makes it much easer to read. You should also post related programs (Driveway Alexa Trigger). Could you tell us a bit about your system? What device are you using, what firmware & UI version? You mention UD Mobile, are you using Notification or node server, if so, on PG3, which version? Where is "Virtual Button" coming from - node server? After receiving many notifications, right click on the program and select status. Note the Activity, Status, Last Run Time, Finished Time.

Here you go, just make sure you meet the requirements:

That's the IoX Launcher, thanks for the clarification. I would suggest pressing the eisy multifunction button once, wait about 10 minutes, then open the Java control panel to delete files (check all 3 boxes). Next download a new start.jnlp from here: ISY Launcher After running the start.jnlp file, a new IoX Launcher should appear on your desktop. I know you stated you have done this, but it helps to make sure something wasn't missed to do it again. If the Launcher still doesn't find your eisy, make sure you disable any VPN and try the following steps from the wiki: Troubleshooting Can't Find eisy First and foremost, all VPN software block discovery of eisy on your network. As such, if you have a VPN software running, please turn it off. If you have a modern router, eisy advertises itself as eisy.local on your network. As such, and in most cases, you should be able to find eisy at https://eisy.local:8443/desc. What you need to do is: In IoX Launcher, click on the Add button Enter https://eisy.local:8443/desc into the dialog Click on the OK button If you are still having a hard time finding your eisy, it's best to check your router's DHCP client list and look for a device that has the same MAC address as the one the label at the bottom of your eisy. eisy's MAC address starts with 00:21:b9. Once you find the IP address for eisy, in this example, 192.168.1.122, then In IoX Launcher, click on the Add button Enter https://192.168.1.122:8443/desc into the dialog. Note 192.168.1.122 is an example. You should use the IP address for your eisy. Click on the OK button Let us know how you make out.

When you say you can not see it in IoX, what are you referring to? Can you access the admin console? Are you using the Launcher? After an update, you may need to reboot a second time and then clear your Java cache, including deleting the 3 check boxes and then download a fresh version of start.jnlp. After that, run start.jnlp and it will create the Launcher icon on your desktop. If eisy isn't showing up in the Launcher, that's a separate issue, so let us know.

Well worth the change for improved functionality all around and fantastic support.

I have 2 Polisy's running v5.5.9 at two different locations and do not experience random reboots. Have you opened a UD support ticket? They can't fix something they don't know about. Have you checked your event and error log? Also haven't seen other Polisy owner's reporting this, could be this issue is specific to your installation. Try changing the power supply.

That would probably be a very practical thing to do. If you want to try and hold on a bit longer, you could contact UD and ask. You can open a support ticket here: https://www.universal-devices.com/my-tickets/

You are not answering all of our questions. It is hard to help you like that. After upgrading back to v5.3.4, clear your Java cache being sure to check all 3 boxes when you delete the files. Then download a new start.jnlp at: https://isy.universal-devices.com/start.jnlp After it downloads, without unzipping, run the downloaded file and it will put the Launcher on your desktop. Afterwards, if you still have an issue then look at the links I posted above. If they don't resolve things for you, then reply back with answers and we can try to help.

Check out this page on UD website regarding ISY: https://www.universal-devices.com/byebye994/ Do you have a UD portal account? You can also try logging in to your account at https://www.universal-devices.com/ and see what is listed for your ISY.

Why did you downgrade firmware? Are you using the ISY Launcher to access your ISY? The reason I am asking is because your firmware needs to match your UI version. Do they match? Check your About page for both, along with access to network module. Did you clear your Java cache and and download the correct UI for 5.3.0? All of the modules are being retired in favor of node servers. Node servers for a lot of devices are being created by developers. There are several weather node servers available.

I believe the climate module was depreciated some time ago. Are you saying it was working until now? We would need some additional information about your setup: firmware, UI version, installed modules, active portal subscription, ect. Be aware, ISY is at end of life and support for it will be ending soon. You might want to consider upgrading to eisy. https://www.universal-devices.com/store/

That's my guess.....

Have you tried rebooting? What firmware and UI are you running? What is the version of ZWave firmware? What version ZWave, 300 or 500? ISY ZWave Version 300 or 500 Series Identifying 300 Series Z-Wave™ By The Protruding LED The 300 series will have an LED protruding out of the rear of ISY and may have an antenna mount as well. Identifying 300 Series Z-Wave™ By Version From the Admin Console select the Z-Wave™ menu at the top of the screen. Select Z-Wave™ Version. If the version is 4.55.00 the ISY has a 300 Series Z-Wave™ dongle. If the version is 6.81.00 the ISY has a 500 Series Z-Wave™ dongle.

You can open a support ticket with UD here: https://www.universal-devices.com/my-tickets/ If you want to try and force an update you can try running the following via ssh: sudo pkg install -r udi pkg Then open the log by entering: sudo tail -f /var/udx/logs/log When the log shows the update is finished, run the following to reboot: sudo shutdown -r now

I see the following in the log, could that be the issue? mqtt_port</code> - defaults to 1883, the example in the thread uses 1884

127.0.0.1 is a local hose IP and is correct. 10.10.2.20 is the network IP for eisy. So far this is as it should be. I think you need to look at how MQTT is configured.

On the Customization email page under the body, there 3 boxes to specify the type of email you are sending. They are Text, HTML, & XML. If you select Txt and list your device underneath each other, it should display fine in an email. Otherwise use HTML and specify the formatting HTML command.

One of the reasons not to use static IP addresses. If you give us a better picture of your setup, we might be able to help.

Try creating a new program set to run at startup. In the Then section add a wait x minutes. X will depend on the size of your system, try starting at 5 or 10 minutes. Next add run Query All (factory default Query program) program. After your X wait, this should run the factory default Query program and populate the Zwave devices, providing they respond to a Query.