Javi

I just updated our Troubleshooting guide to account for some Mac Security and Privacy Preferences which may cause this issue. https://wiki.universal-devices.com/Main_Page#Unidentified_Developer_Blocked

There is no guarantee this will work with MobiLink, so may want to wait for confirmation that this works. Likely better if user switches to UD Mobile if they have Node Servers. See https://github.com/search?q=org%3AUniversalDevicesInc-PG3 hint&type=code for a few examples. If I recall the following documents may have conflicting information, so I'm not sure which, if any, are used by MobiLinc. https://wiki.universal-devices.com/index.php?title=Node_Hints_Documentation https://github.com/search?q=org%3AUniversalDevicesInc-PG3 hint&type=code

Try to find the Hint (sometimes Type is equal to hint) for a similar device from rest/nodes, then add the same value to the Node Server Node. I think sensors are 7.0.0.0, but may require the second position also, i.e 7.X.0.0 https://wiki.universal-devices.com/index.php?title=Node_Hints_Documentation Below is an example for thermostat with hint added by Node Server developer. <node flag="128" nodeDefId="HwhF"> <address>n006_48a2e687e1a9</address> <name>Home - Hallway</name> <family instance="6">10</family> <hint>5.0.0.0</hint> <type>5.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n006_48a2e687e1a9</pnode> </node>

I believe MobiLinc uses its own static "profiles" for device types. So it may not work well with custom profiles provided by Node Servers. If the node conforms to a static profile then setting the Hint may allow the device to work with MobiLinc. Hints can be set by users if needed using ISY Portal (there is a local API also but no UI). If the hint works the Node Server Developer can set this as the default. Motion Sensor conformance would likely require the Node Server have same status and command IDs as an Insteon Motion Sensor.

Uninstall would likely not change anything as My Geofences is a UD Mobile Feature, not related to eisy. If encountered again, please post a screenshot of the second screen which requires tap as I cannot replicate.

Uninstall will not change anything. I do not understand Are you seeing 2 geofence screens? While the "My Geofences" screen content may change the title should remain the same if on the same screen.

When this happens is the title at the top of the screen "My Geofences"? My guess is My Geofences is the only tile for a brief second, then registers the click for the wrong tile taking you to the My Geofences Screen instead of My Devices. If the tile is different please share a screenshot.

If a device is not writable then eisy cannot communicate with the device, this can affect any scenes with the device, so likely all related. Try air gapping the device (pulling tab out until it stays) waiting some time then reinserting the tab. Or factory reset the device.

If this is showing outside of UD Mobile's Geo fencing, please post a screenshot of the location so we can try to resolve. The screenshot above is in "My Geofences" and working as intended for "when using" permissions level as always is required for Geofencing.

As far as I know it is a standard USB cable. I have not see reports stating otherwise.

While not exactly what you are looking for, the bulb can be set manually using UD Mobile in the Device's Dashboard (coming soon to favorites). Click the menu next to the Hue and/or Saturation properties and select the Hue or Saturation Sliders as the View Type.

Pinouts on generic USB -> RJ45 adapters do not match for Insteon PLMs so they will not work. The options are to build your own cable (instructions are posted somewhere on the forum) or purchase one from UD.

Are you seeing this outside of a Geofencing Screen? If only seeing this in a Geofencing Screen it is expected as the app cannot function without Always permission. The likely cause is the app previously requested that the user "allow always location" but either (1) the request was denied or (2) iOS may periodically alert users an app is using allways location which and give then the option to revoke. If the request is denied or revoked user must manually change this permission in iOS Settings before Geofence screens are shown in UD Mobile.

Great! The "Beta" is because it was installed from the "Non-Production" Store. I think you would need to copy the parameters then delete the Beta Version, then install the Production version in the same slot and replace parameters. I think if done like this it will preserve programs, but have not tried.

Might be related to the version, I've corrected in the database. Please try again....if it does not work reboot may be required first.

The preceding zeros in 2023.01.09 were causing issues with PG3 so they were removed. While I don't think the version is the cause of "Unknown Error" I think you can fix this by selecting the Plugin from the Non-Production Store (Beta), clicking install under "purchase in "Available Purchase/Install Options". Then next to "iTach-IR 2023.1.9 is already installed in slot X" select "reinstall here". For the "Unknown Error (see Logs)" there should be a few logs in the iTach Node Server. The error is likely prefixed with "ERROR : ". Download the iTach Log after and error is encountered then attache here for review. If this happens with the same commands then it it likely invalid formatting. If this happens randomly then it is likely a network issue, is this a WiFi iTach or hardwired?

Look Looks like a parsing error possibly caused by an invalid character. Please open a ticket and include eisy's UUID.

Some of the Favorite Types require that the Display Status is linked to a command, i.e. toggle needs to know status to send the opposite command. Command Type doesn't require a Display Node or Display Status. If need the Display Node Can be removed by clicking Display Node then pressing delete (top right) on the Node Selection Dialog.

We are working on a production version with (future) browser support. So I recommend holding any charges until released to production.

Great, no way the remote connection would have shown connected. My guess is the phone was connected to WiFi and was using the Local Connection Settings. The Local Connection Settings had the Local IP Address of an active system. So UD Mobile did connect just to the wrong system. In this case an error is only shown during synchronization when the UUID is validated.

Highly unlikely, more likely the system name does not match the UUID fo that system. Check Settings tab > Systems., Click the name of the system, check the UUID. If the system is no longer used it can be deleted or disabled (system settings at bottom of the same screen).

The toggle failure is likely related to the "Unknown" Status. My guess is UD Mobile issues the command but the status does not change or there is a communication issue with the Node Server. Assuming the door is closed when "Unknown" is encountered, does the status change if you click the tile's menu (3 dots) to go to the Device's Dashboard, then click the command to "Close"? If it does not change try pressing "Open" on the Device's Dashboard, does status change? Does the door open? If there is no status change and/or the door does not open then there is a communication issue try checking the Node Server Log or opening a topic in the Ratdgo subforum. If the status changes when pressing open form an "unknown" state then the default UD Mobile Toggle implementation will not work when the status is "Unknown" as it appears value for "Unknown" is higher (as an integer) than "Closed" so UD Mobile will send the close command when "Unknown" is encountered. If the last statement was true then there are a few options. Issue a direct command by pressing the tile's menu (3 dots) then trigger a direct command, i.e. "open". Create a custom toggle, our example is very similar to this situation. See https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Examples Create 2 favorites command tiles which trigger open and close. (Beta) Create a custom tile. We will add a favorite type to remove the toggle indicator for these situations in a future version of UD Mobile.

Sounds like 2 separate issues. Status icon/color mismatch: Do you have a screenshot showing the mismatched icon/status? Commands not executed: An activity indicator (circular progress) should show on command execution. Do you see the indicator? Does it stay on the screen? Circle in Upper Corner (Toggle indicator): This should correlate to status. Normally filled is ON and empty is OFF. The toggle indicator should only appears on devices which have a Status named "Status", and both an On and Off command. While this works with most device types it is possible Status does not have a relationship to On and Off. In this case "default will not work" The app should allow users to switch the type to "Standard" for this unusual case, however I just noticed it fails on both Android and iOS wo will need to be fixed.

Thanks, please try upgrading UD Mobile to version 1.1.54 which should fix the Firebase dependency crash. Version 1.1.54 was approved for production release this morning and beta yesterday.

Please share a screenshot of the error or the error report. Not all functions were tested on Mac so it may be a compatibility issue. P.S. Also please upgrade UD Mobile to version 1.1.54 as 1.1.53 was crashing due to outdated dependency