Javi

Try clicking the chevron icon to the left of the folder to expand.

I think you are close, the packets look similar. As @kzboray mentions If this is your first time using WireShark, you are doing fantastic! The telnet packet shows an \r following the command "ASPECT 30 \r", so this must be replicated in ISY. As @mwester mentioned the packets from the ISY are reaching the device but the ISY can not read the response, which is not necessarily an issue unless the command is not functioning. Finally as Michel mentionions when using binary you will need to encode "\r". Have you tried another mode with "ASPECT 30\r" , "ASPECT 30\n" , ""ASPECT 30 \r\n", ect. I did a quick search of the forum for telnet and this came up this which may help.

Hi @dbencivengo, Unless you are routing the ISY connection through the computer running Wireshark will not pick up direct connections between 2 other devices, i.e. you computer is not part of the conversation between the other 2 devices. There are some exceptions to the previous statement, but this is generally how packets are routed. I only mentioned Wireshark to capture the raw data being sent from the program on your computer to give insight to what is actually being sent by terminal. The possibly using the capture to to replicate a raw or binary resource.

It is likely that one of the commands is not terminated or being encoded properly. This can be operating system dependant, so something that works in terminal may be different on a different OS The easiest way to find the raw string would be to sniff using Wireshark. Filter to the IP address of the device then send the command from terminal on the same computer. Click the packet, usually the first if filtered, others may be response or acknowledgements. On the bottom window scroll to the bottom line. The last line usually contains the raw request.

Beta 0.7.7 Fixed Insteon liking when started/stopped by another client/instance when app has multiple ISYs. Zwave progress dialog will now show when started/stopped by another client.

try \r or \r\n or \n

I added setup instructions to the Wiki. https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration#Firmware_5.x

This already works well, the issue is manual control of the FanLink from Alexa/UD-Mobile and keeping the KPL in sync.

This allows users to select the fan motor as the device for alexa, so it has native fan controls. Also syncs UD Mobile if controlling the fan motor.

Due to how KPLs and insteon communicates, this does require a work around. The first issue is KPL buttons are only controllable by a scene. Second is we need to keep buttons in sync, and finally the limitations of Alexa. If using the V.5 method with one scene for physical control, then do the following. This method is tested with rapid button presses so things will not get out of sync ? Create 3 additional scenes, one for high/med/low with all kpl buttons as responders in each scene, ISY should only allow responders if the V.5 method was setup correctly. For each scene set the the corrisponding high/med/low kpl button to action ON (default) and the other buttons to OFF. This will keep things in sync. DO NOT add the fan motor to the scenes. Create 4 programs one for high/med/low/off. For the high/med/low In the IF condition monitor Motor Status and a single KPL button status, i.e if fan is low and KPL button corresponding to low is OFF, set the low scene ON. For the off program monitor motor status off and (kpl high is on OR kpl med is on OR kpl low is On). Then set any one of the scenes created above to off.

@cwagner2401 The Elk Node Server is local on PG3 (Polyglot V3). Node Servers are similar to an apps which allow non-native device/service to run natively on ISY. If your Universal Devices hardware is a Polisy, PG3 is already installed and you can download Node Servers from the PG3 Store. I'll skip the details as there are many forum threads and documents explaining setup and installation. If you have specific questions we will be happy to assist. Thanks @apostolakisl, maybe Jim can add this as a feature request if it doesn't already exist.

@apostolakisl Thanks. Do you know if tasks are these available using the Elk Node Server? @cwagner2401, not sure if you are using the Elk Node Server, but I believe it has greater functionally than the Elk Module. All Node Servers should be compatible UD Mobile, modules are not supported.

What is shown when selecting "add"?

Assuming this is for a Favorite, change the Favorite Type to Command. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Commands Example: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle

Production 0.142 Added Insteon Inclusion. Fixed remove node. Added Zwave include/exclude progress descriptions. Rebuild subscription parsing. Added saved state for non database actions.

Thanks @DennisC, Yes please open a ticket.

@DennisC, If that does not resolve the issue please send me an email. The app gets the formatted values from the ISY so this is very odd that it would show in the AC but not Mobile after reboot.

Hi @oskrypuch, I added variants of your request to our issue tracker, we have a few higher priority items in the works, so it may be some time. https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/30 https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/31

Currently Insteon linking is available on the iOS variant of UD Mobile. Insteon linking on Android, including Amazon devices, should be live by the end of next week.

Production 0.141 Fixed onboarding. Onboarding will now show list of ISY instead of first found.

If this is a PLM have you tried to changing the cable between Polisy and PLM?

Port forwarding is not needed for ISY Portal, the ISY/Polisy will call out to the portal to establish a connection.

Ok thanks. Must be a firmware bug, will look into it soon.

Thanks, that eliminates the Frontend/UI issue. Is the ISY editable from the app, or is this where the error is encountered? Edit: Just saw the image, if you save first, can the system be deleted? UUID is automatically input from ISY credentials, so it is not user editable.

If you have an Android device, UD Mobile now on Android contains the PG3 frontend. You should be able to delete from the app