Javi
-
Posts
2006 -
Joined
-
Last visited
Posts posted by Javi
-
-
Thank Guys, I had a few reports of this issue but could not find a Firebase crash log. @Geddy 's Apple report actually came through with the crash log. I don't even check there often as the reports usually fail to include the crash log.
-
1
-
-
It's still on our list, but can be done from the Admin Console.
Scenes in version 5.x are much more complex than Scenes in 4.x (see the 5.x fan example). Also for insteon the Scene information is written to the Controllers/Responders so may take some time depending on the number of changes.
Each Scene-Controller-Settings has an on-level setting for each responder in the Scene. The Scene-Settings also has an on-level setting for each responder in the Scene. So changing the on-level for each Responder manually may not be intuitive or may not work as desired without changing many properties.
So, if you set the Scene-Settings on-levels' for each responder, it will only work if you trigger from eisy. Setting on-levels from a Scene-Controller-Settings will only work when triggered from that Controller.
What are you trying to do? There may be another way to accomplish the same without getting too deep into the settings every time a change is needed.
-
Should be fixed in the next version Android 1.2.28 and iOS 1.2.6.
From what I can tell this is only an issue with displaying the formatted value, the mapping should still work.
-
Understood, and yes the numerical IP is more reliable than eisy.local. We have encountered home networks which stop routing to dot local and Mobile devices which stop routing to dot local. Usually corrected by restarting the Router or the Mobile device.
With regards to reset local credentials: They are managed by iOS keystore so loss of local creds should correlate to lost remote creds. The app will use "admin" for local username or password if it cannot obtain a stored value from iOS keystore.
iOS Keystore may (but not always) loose values or the app may lose the key if the app is uninstalled, backup is imported (if the controller ID is not the same), or the controller is recreated (deleted then added) in UD Mobile. Being as keystore is managed by iOS there are a few reasons (such as corruption or security related change on the device) that keystore may fail to return a value, but I think this a low probability.
So there are a few ways keys or values may be lost. My guess is one of these things happen and the app prompted to re-enter remote credentials (i.e. login) at some point in the last 2 months. This is the only report I have for this issue without the user changing something, so I'll keep an eye out. Let me know if it happens again without an import or reinstall.
-
1
-
-
Based on the screenshot it does not appear the app lost local connection settings. There was a new setting (switch) added which produces that error message. If you try to enable automatic detection but have already defined a WiFi network then the app will show an error saying you need to remove defined networks for Automatic Detection.
Note that it will always be more accurate and faster if you have a reserved ip and a defined WiFi network in UDM. If no wifi network is defined the app may still use the remote connection when Automatic Detection is enabled.
The likely cause for connection error is the app cannot connect to the eisy.local address. My suggestion is to add the numerical IP address in the app with an IP reservation in your router.
If permissions were changed, it was the user or iOS which changed the setting, the app cannot change iOS permissions.
-
1
-
-
We have updated examples on creating and modifying notifications. These new examples show both the AC and UD Mobile at the same time.
Setup: https://youtu.be/KSmx-XIquAw
Sending to a specific Group or Device: https://youtu.be/z4pquLcI2Es
Creating your own notification content: https://youtu.be/KSmx-XIquAw?t=165
FYI: there is a bug in custom content prior to 5.9.1 which will not show customizations after a missing ID (sequentially). This can be fixed by adding a new customization until all the gaps are filled.
-
1
-
-
-
Do the logs show any errors? Currently on android there is not copy, just screenshots. I recommend deleting before leaving or entering the boundary then checking the log for an error message. If there is an error message it may be self explanatory, if not let us know what it says or share the screenshot, but paint over any sensitive lat/long data.
-
Found issue, fixed in next version.
-
1
-
-
iOS or Android?
-
Reference https://github.com/JavierRefuerzo/iTach_IR_Node_Server?tab=readme-ov-file#general
Only one configuration is needed per device (not per code). Please post the value input into the node server, it's possible they changed the format so the Node Server cannot parse. Being as there is only a single value the delimiter between codes may not match, if I remember correctly it is a double space or maybe a double new line.
-
Not in app, currently only at the top of Admin Console. Is on our very long TODO List.
-
2 hours ago, EJones01 said:
The GPS has worked flawlessly for months. 3 days ago it stopped. I see in my Android settings that the app is still requesting the location but its not triggering the GEO fence anymore. The UD Mobile logs do not show updated locations anymore so I'm presuming there's a disconnect between the ask for location from the App and then not getting it. App still has full permissions. Was there an update?
Not changes, and I use android and it triggered this morning. Have you tried restarting the Android Device?
Also verify Location is enabled on Android Device. UD Mobile has location permission. And the Geofence inside UD Mobile is enabled.
There is also a bug on some android devices/versions which requires the "(Experimental) Force Geofence updates.." to be turned on. So you may want to turn this on to see if it starts working
15 minutes ago, Geddy said:@EJones01 can't help directly as I'm an iOS user, but if you have the geofence area on the app at the bottom there should be an option to "Trigger Enter Command" and/or "Trigger Exit Command" (it shows on my app - again iOS). If you manually trigger the geofence does it do anything?
As for the logs are you looking in the "My Geofences" area? I still have a log icon (looks like a dog-eared piece of paper) that does tell me when I've entered/exited for the last few days.
This was never implemented on Android, still on my TODO list
-
1
-
-
14 hours ago, tmorse305 said:
Sorry, Yes I did.
Ok, thanks.
-
On 3/13/2025 at 12:32 PM, tmorse305 said:
Hi @Javi, I enabled developer mode on my iphone to see if I could get any further. I did get past the error above but the commissioning just blows out and I'm back a regular UD screen. UD lost communication with eisy. The admin console would not load, so I had to reboot eisy to regain control. Tried it again, same result. Third time I brought up the AC first and enabled the Matter log capture. Commissioning still crashed but the AC stayed up and I captured the resulting log file. I'll attach it in case it's of any value. Let me know if you want me to try something else. Thank you
Thanks for the information, I was not aware that enabling developer mode allowed commissioning to move forward. Did you install a developer profile also (this is a file import you would know if you did it) ?
As for the crash, please open a ticket. This is likely not related to the app itself so will need to be handled by someone else.
-
On 3/5/2025 at 7:59 PM, tmorse305 said:
Hi @Javi, I'm not sure what you mean by this. My matter plug is WiFi not Thread. Is there a way to commission it without using BLE? I only see the BLE choice in UD Mobile.
Currently not with iOS, only Android.
-
On 3/8/2025 at 7:48 PM, joeria said:
I'm at the end of a very long 9 hour migration saga and can't get past this last item. Migrating the plugins did not work so I wound reinstalling and reconfiguring 12 plugins. In a support conversation, the rep had me migrate licenses to get the plugins working. Then when I got to the step to migrate UD mobile I had could not clear the UUID since it show as expired. BTW the UD Mobile migration instructions keep referring to System under the setting tab, which doesn't exit, so I have been on the controller settings.
In order to try to follow the directions, I purchased a one year license for the Polisy on the portal, but still no joy in clearing the UUID, yet it functions fine on remote. If I delete the Polisy and add the eisy and then do a restore from my backup it deletes the eisy and adds the Polisy.
I'd really like to be able to migrate as I did a lot of work to my favorites look and act as I want.
For now, I'm back on the Polisy. Anyone have any thoughts. I did also open a support ticket
Thanks!
Was this resolved in the ticket?
Notes: Cancel any alerts/warnings/sync-request in controller settings. Scroll to the bottom and press clear UUID. Be sure to update Remote and Local URLs to point to the new controller.
-
14 hours ago, BRMeeke said:
I have 2 Scheduled programs that eisy says are not found. It suggests that I should synchronize but even after that, the programs are still not found. The cursor is empty.
can someone tell me how to delete these zombies from the listing? I have tried a long press but nothing seems to work.
thank you
Please post a screenshot of the error message
-
8 hours ago, 737simguy said:
I went ahead and did the “Update Packages” from within the Admin Console and it did update something, now all looks normal again and still on 5.9.1.
I also did a sync in the UD Mobile after the update. It shows an error as in the attached pic but everything seems to work fine. I have no Matter devices yet.
The UDM Synch error is fixed in the next app update. It can be ignored until that time as it is only stating there are no matter devices.
-
The notification is generated from the box itself, so there is an update. The app does not know the version, it pulls the version from a server, but looks like server was not updated with the current new version.
-
try the Plugin Notifications (PG3). I think the system are only for connect and disconnect from portal.
-
UD Mobile > Notifications Tab > Menu > Mobile Devices/Groups > Groups > System Notifications.
-
Updates:
We are working on a couple of issues.
The "rendezvous" error in UD Mobile is firmware related for some, but not all, users and we hope to have a new build in the next week.
The "Could not write characteristic" error is being encountered for all users on iOS devices for Matter BLE Wi-Fi commissioning. iOS is blocking communication to Bluetooth for a characteristic (UUID) used by Matter devices. We are looking into the issue with Apple. So, currently BLE commissioning for Matter devices from an iOS device will not work, but Matter should work for IP, Thread, and previously commissioned WiFi devices.
-
2
-
-
App quits unexpectedly
in UD Mobile
Posted
Issue should be fixed in iOS app version 1.2.7. Usually takes apple a couple of days for review before going live. Thanks