Javi

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

Invalid url is the reason. Please copy the Admin Console URL from your ISY Portal Account. https://wiki.universal-devices.com/index.php?title=ISY_Portal_Admin_Console

I have a Mac M1 with no issues. How are you establishing the remote connection, ISY Portal or direct IP Address?

The node server resets the Module Address and Connector, so manually editing these values will have no effect. Could be the Node Server's parser. If I recall I only tested parsing with the default Global Cache Database values, i.e. 1:1. I'll update here when I have something to test for module address changes.

Hi @Ross, Subtitle text will be darker in Light Modes in the next update. This should change everywhere in the app, please let me know if you find somewhere else where text color change is needed. As for text size this is handled by the operating system. In both Android and iOS you can change the default font size and the app should adjust automatically. This has been tested on most screens, but if you find a screen not honoring these values please let us know.

I'll try to change the iTach NS to allow for Module Address change when I get some free time. So this should work for all of the GC IR Modules. I think the serial modules, or any of the other modules, would need their own Node Server. I own a GC serial device but I'm not sure if I'll have time in the near future to develop anything. If I remember correctly, the GC Serial modules can also publish incoming data which could also be handled by a NS. The iTach NS is open source so if anyone wants to use or modify the existing code they are free to do so without restrictions. My knowledge of Python is limited, so even the current NS could use improvements.

You can issue direct commands, If the nodes are missing from UDM please synchronize first. The app does not synchronize unless the app adds/removes the node. Programs are also an option but not required. Favorite Command With iTach NS Favorite command which also shows the status of a TV

Great! There is a character limit for nodes so the NS removes some chars. I have a IP2SL-232 but have not had time to try anything. Currently just using Network Resources > IP2SL-232 > Somfy RTS controller. The NS was designed with the GC-100 in mind however I was waiting until someone asked as I don't own the hardware. I believe the NS just needs to expose the the Module Address to users. This should allow control of any of the IR Modules. I try to get something to test when I get some free time.

Great, I like the eye icon, added to our issue list https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/47

If there is a plus sign then the systems are hidden. Press the plus icon for all systems and a minus icon will be shown. Then disable edits.

Did you happen to hide the system? Try pressing the edit icon at the top of the home screen which will show all systems including hidden systems. If there is a plus icon next to your system name then it was hidden so press the plus icon then press the edit icon to disable edits.

Hi @CNelson03, I reviewed the code and the time out is set to 3 seconds which may too low and possibly causing the issue. However I could only replicate "Unknown Module" if the url parameter was incorrect. Can you please verify the url is correct? You should be able to see the iTach's webpage at the same address.

If there is not a single device then something is wrong. UD Mobile lists all Nodes, Programs, Variables, and Network Resources with all available controls on the Home Screen. The Favorites screen will be empty until you add items to favorites. Please try synchronization if the controller is listed on the Home Screen by clicking the controller then pressing the synchronize icon at the top right. IF the controller is not listed on the home screen, then go to Settings-Tab > Systems > Your Systems, if everything is configured correctly the app will prompt to synchronize or will show connection errors. If you get errors during synchronization please let us know.

Hi @Jimini, Uploaded video with improved audio. It may be a hour before it is live. https://www.youtube.com/watch?v=9w-_8AZy4iQ

Hi @johnnyt, A bug preventing disable of all groups should now be fixed.

I'm the frontend developer for UD Mobile so I can say with confidence that UDM Notification delivery is stable in production. As of this week UDM Notifications now include notifications about Portal Service interruptions and system connection status. Notification Creation is stable using Network Resources (the only option if you have ISY994). For eisy and Polisy you can use the Notification Node Server. The Node Server route makes things easier for users to configure but does not render the Network Resource option obsolete. The Notification Node Server uses the same APIs as the Network Resource Example. See this topic for an example of setup:

Hi Dennis, Settings>Systems>Your-System>Disabled only disables subscription startup in UDM. Is this system listed on your Portal Account? If it is not then there should be no notifications about connect or disconnect. If it is listed but there is no subscription then remove from portal.

Looks like the app is using the Basic Remote Connection Port if Port was set when "Use ISY Portal for remote connections" was switched off. If you have a backup you can reload, switch off "Use ISY Portal for remote connections" delete port then switch back on. Added issue https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/45