PapaSmurf74

Looks like we have the same problem with version 3.1 of the app. 3.0 did show up on the amazon app store but now the 3.1 version will not install on my kindle fires

The new control4 OS3 app is not compatible with my 2018 kindle fire. Seems like control4 needs to update the compatibility list on the amazon app store.

The Guide button is configurable to either go to guide or home. All I'm asking for is the menu button to be configurable as well.

Please add the ability to send the home command when pressing the menu key. This specifically applies to Shield TV. Thanks for an awesome product!

Any updates on getting pairing working again? I'm interested in getting the driver.

The new google home assistant will support IFTTT out of the box. That means this driver will be able to interact with a google home device as well. Woot!

The new proxy has the ability to set a default code for each partition. I expect the idea is that it will use this default code when you programmatically arm or disarm the system. Unfortunately, this does not seem to work. I've seen reports for multiple security panels stating that this functionality does not work. I assume the concord 4 driver has the same problem. I'm not sure if this is a proxy problem or a failure in the protocol driver to read the default user code if set. Since all the security panel protocol drivers are encrypted there is no way to be sure.

I'm always happy to beta test for you. I have 4 2477D 0x44 dimmers, but I don't have any other models. Oh and I confirmed that the second command functions the same. i.e 34 FC will ramp to full over 5 seconds. 34 7D will ramp to 50% over 2 seconds.

Ok I found it in the latest documentation for the led bulbs. It was changed from 0x2E to 0x34. I verified that the newer firmware dimmer "light on at ramp rate" command works.

This thread highlights the same problem. Post #9 indicates that firmware 0x44 changed the "light on at ramp rate" command. He was able to find another command code to implement the same command, but doesn't say what the command is. I'll keep digging. http://board.homeseer.com/showthread.php?t=172339

Oh, and something I learned through the documentation digging I've been doing. You could use port 25105 instead of 9761 and be able to be running HouseLinc and still be connected to the hub using your driver. You just need to get the authentication on the hub using the following information. http://support.insteon.com/customer/portal/articles/1379424-manually-setting-the-time-on-your-insteon-hub-1

Jackstone, There is nothing wrong with your driver. It functions perfectly. The new dimmers do not respond to the 0x2E ramp command you are using. By communicating directly with the hub I can turn on and off the lights with the following commands http://192.168.1.5:25105/3?0262396B9B0011FF=I=3 - For on http://192.168.1.5:25105/3?0262396B9B001300=I=3 - For off But http://192.168.1.5:25105/3?0262396B9B002E7D=I=3 - does nothing http://192.168.1.5:25105/3?0262257575002E7D=I=3 - Works (25.75.75 is a 0x43 dimmer device) The new dimmers do not accept the command. We can work around this by have the driver issue the 0x11 command for turning the light on to a specific level instead of the 0x2E command you're using now. I have a support request into the insteon developers if there is a workaround for the lack of 0x2E command in the 0x44 dimmers. I'm curious as to why you're using the fast off 0x14 command instead of the off 0x13 command which will used the preset ramp rate for the device when you turn off the light from an interface. You also use the 0x21 command for turning on the dimmer instead of 0x11 which uses the preset ramp rate. 0x21 is instant.

As a side note, for others using insteon and houselinc to setup scenes the 0x44 dimmer devices will not sync with the latest version of houselinc (2.10.25). You must manually hack the Devices.xml file as outlined in the following thread. http://forum.smarthome.com/topic.asp?TOPIC_ID=15846

It doesn't turn on at all. On a 0x43 firmware or lower dimmer it will ramp to the designated level in the designated time. When I try it on my 0x44 devices nothing happens, no change in light level.

I recently purchased some new dimmers to add to my system. The "Ramp to" programming functionality does not work with dimmers 2477D with firmware 0x44. The "Ramp to" functionality works fine with firmware version 0x43 and below. Not a huge deal, I have a workaround in place by setting the local ramp rate and just turning the device on and off. Just wanted to make you aware. Send buffer emptyFunction: SendToNetwork(6001, 02 73):Send buffer emptyReceived from Proxy: RAMP_TO_LEVEL on binding 2; Call Function RAMP_TO_LEVEL()Function: SendToNetwork(6001, 02 62 39 6B 9B 00 2E 7D):SendToDevice(1726, LIGHT_LEVEL)Last command sent OKHandleCommand():02 50 39 6B 9B 25 E2 12 20 2E 7DIM Command: 50Command 1: 2ECommand 2: 7DTo Address: 25 E2 12From Address: 39 6B 9BSendToDevice(1726, EXTENDED_GET)Message Flag: 20Extended Get receivedSend buffer emptyFunction: SendToNetwork(6001, 02 73):Send buffer empty