Javi

Great! Just awaiting Apple's Approval.

@mbking, Do you happen to have an app backup file? This looks like something in Favorites are causing the crash. It will be much easier to locate if I have the setup. Edit: Replicated issue and removed from test flight. I think you can downgrade the version, but only attempt if you have a backup file...I have not attempted this before so am unsure if it is destructive. Edit 2: Should be fixed in version 1.0.30

I think I see your crash report. Looking into this now. XCode (iOS development) was updated and required dependency updates also which may be the cause.

Fixed in Android 1.1.4 and iOS 1.0.29

Hi @MBell, Thanks for the report. I tried but cannot replicate the issue. Are you using the Z-Matter module or Zooz USB stick? Update: Replicated. Looking for cause

Server version is usually updated a few days after the forum posts, think of this as a staggered release. Force Upgrade from app will still upgrade to latest version even if it is not known to the app. I was just informed there is bug in the semantic version comparison if you upgrade before server version is updated. This is causing the app to show Firmware Update Available when you have a version greater than known current version, even though there is no upgrade available. Will be fixed in the next version.

Hi @CNelson03, May be an expired remote access subscription, please go to UD Mobile > Settings-Tab > Systems > Your System and the app will attempt to diagnose connection issues. If you prefer local only access without portal see: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Local_Connections_and_Local_VPN

Added "response", as this was the context.

There is no way to set variables using Network Resources response. You could try the AV Remote Node Server which shows Denon support in the description. Another option would be to use UD Mobile to trigger the the volume change in IoP instead of a direct connection to the equipment.

Beta Version 1.1.2 This version re-enables local connections to PG3/PG3x and remote connections to PG3x. Please report any issues in the UD Mobile sub-forum. Note that Local Connections require Local Connection Settings are enabled and valid for your System (Settings-Tab > Systems > Your System > Local Connection Settings). Local Connection Settings requires location permission and your WiFi SSID. Polisy will require manual upgrade to PG3x for remote connections, eisy was shipped with PG3x. Added PG3 Remote Connections for PG3x. Changed MQTT Library for local connections and re-enabled local PG3 connections. Added PG3 Notification Options. Added darker gray color for cell subtitles. Fixed click listener for favorite folders with variable display node. Bug fixes

Are you using the Z-Matter USB stick? Does the Address of the Z-Wave device match? ISY had ZW prefix to Z-Wave Addresses, Z-Matter prefix is ZY.

Hi @fustesj99, While the app does have custom scheme urls most of them will not work with chrome, see link below, although I believe could use the intent anchors listed on the same page. https://developer.chrome.com/docs/multidevice/android/intents/ https://developer.chrome.com/docs/multidevice/android/intents/#syntax https://developer.chrome.com/docs/multidevice/android/intents/#examples See the following post for intent to launch UD Mobile from tasker for the parameters. https://forum.universal-devices.com/topic/32544-favorites-set-as-default-first-screen/?do=findComment&comment=312306

If not already tried, the alternate code in the Node Server may work. Sometimes GC includes 2 codes for the same command.

Hi @peterathans, Glad to hear it has been working Great! The "Beta" version is now in production. The only reason I left the beta label was because I was hoping any users having having issues would report if it had that label. The beta label will likely be removed in the next version, any modifications in the future should not affect existing Geofences.

Hi @CNelson03, Glad all is working. The Error messages for the iTach node Server was likely due to improperly formatted IR command. The database removal message is due to nodes/commands no longer existing. Most of the time this is safe but if you had a favorite with one of the deleted nodes the app will also remove the favorite due to database constraints. So if favorites are removed you could import the backup and point the favorite to the new node if needed.

HI @LFMc, Thanks for the report. Fixed click listener for Favorite Folders with Variable display node in version 1.0.36.

Just eyeballing this but it looks like the Global Catch hardware may not need the #setstate..... in the command. Also my commands have "<cr>" for the carriage return. Finally I am using Raw Text not C - Escaped.

Hi @macjeff, Nobody here is attacking you, we are simply trying to debug. I have also authored many bugs, finding and fixing them is what makes you "good". We are saying the likely issue is your programs or the Notification Node Server. We have already narrowed down the possible causes but we cannot go any further without the logs from the Notification Node Server when this occurs and/or running the tests I suggested. IoX program execution is not linear. A program can stop executing if the conditions (IF) are re-evaluated. So we need to know if the Notification Node Server is receiving a new command for each notification in the loop or if the Notification node server is not getting a response from Portal and attempts re-sending the notification.

Hi @macjeff, I think you misunderstood my post. The likely cause IS in your programs. Less likely, but still possible, is an issue with the Notification Node Server. We have no other user reporting duplicate user generated messages. The issue is NOT with Portal as the timestamps when Portal received the requests to send notifications are different. The issue is NOT with Apple Push Service as portal IS sending these messages.

Hi @macjeff, The timestamps on your notifications are different so they are unique not duplicated by the app or by Portal. There is the possibility that the Notification Node Server is looping, but if this was the case it would likely happen for all notifications not just a few programs which command the Notification Node Server. You can check the NS logs to see if this is occuring. You state that when you run the program the loop starts. This indicates you have something causing a loop somewhere. The same command can be sent from the Node Server itself outside of programs. My guess is that if you send the notification directly from the Node Server, not from a program, there will be no loop. This would eliminate the Node Server as the issue and leave us with issues in programs.

If you post the network resource someone may be able to see the issue. Usually a rest error for network resources is because the resource failed or responded or responded with something that could not be parsed by ISY.

Hi @Ross, Add issue to our list. https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/48

Yes.....No need to apologize, it was not properly documented. 😊

If it works in the past, then verify the variable is changing. Apple recently started giving apps generic device names which appeared to cause the same issues for other users using automatic variable definitions. UD Mobile now has geofencing if you are interested in an updated app. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Geofencing

Hi @Jimini, Added the following to our wiki, please let me know if you have additional questions. UD Mobile Notification Groups are used to send notifications to a single device or group of devices. To send to a single device only enable the the device which should receive the notification in the group. A group is used for single devices to make device replacement easier. When replacing your mobile device enable the new device in the group, there is no need to edit network resources. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Group_Setup