tazman

When on commands work reliably and off commands do not you need to start looking at the loads that are being turned on for noise issues.

You need to select a device in the scene then configure what happens with the other device when it is activated.

You can not control the secondary buttons directly so the fix is to put the button in a scene then you can control the scene in your program.

On eisy 5 button presses reboots the device and 6 button presses shuts down the unit where the light will turn red and you can safely unplug the unit or press the button again to restart.

I just bought a ZEN17 800LR that I added to my eisy wit Zmatter board on IOX 5.8.4. I set parameters 2&3 to 10 for on/off and set parameters 10&11 to 0 to disable the input triggers for the relays. After Removing the device from eisy and adding it back in all the controls seem to be working fine but after trying 2 times there is only a Binary Sensor made for the first input that normally controls relay 1 but no Binary Sensor created for the second set of inputs. Is this what others are seeing when they separate the inputs from the relays?

I have a V3 that works just like the rest. Since the information is being pulled from Emporia I would bet the Plugin does not know the difference.

In your picture you are not showing the left column where you have to select your "Remote button" then select what happens with all the devices in your scene whe that activates the scene.

It's good you got it working! Hopefully a new power supply will get you all fixed.

You select the controller in the list which in my picture is the left circle a keypad button then under the responders you can pick each item and set what you want them to do.

When you trigger from Alexa it uses what is setup for the main scene but like I said you need to pick your controller in the scene and set the desired on level with that controller as shown in my attached picture.

I tried searching for Mele problems which basically what the Eisy is and only found one power button problem. I would connect a monitor to it and see if it displays anything. Unless someone else has an idea you might have to submit a ticket to get help from UDI.

Red light means it is powered down and one press of the button should cause it to turn on.

Have you gone into the scene and selected the Insteon device and set your on levels?

I have version 1.2.5 of the app for android and I don't see anything for WiFi inclusion. Am I not looking in the right place or is it not ready for everyone to try?

Correct the device will respond but the scene will not. You have to physically activate the switch for it to send the command to operate the scene and that is why it is best to operate the scenes from the admin console and in programs to keep everything in sync.

If you operate a "secondary" device from the admin console it is normal that it will not operate the scene.

I guess I should have stated I'm running strictly cloud based. @Panda88was able to identify what was going on and made a change so the solar is updating regularly again. Thanks for the quick fix @Panda88!

At this time I can not connect to the local IP Tesla is trying to figure out why my Neurios occasionally disconnect. So local access is required? I was running it without local access before and it worked fine but I know Tesla keeps changing things.

On the old TeslaPW version 0.3.69 the solar information loads but will not update unless I press the "Update System Data" button. The main other feature I use is "Battery Charge Level" which updates on it's own. I tried the new udi_TeslaPW2 and although I can not find the "Instant Solar Export" in the AC I assume because of the amount of data does not fit in the AC I did find it in UD Mobile but it shows a value of "99" for that value and a bunch of others.

I don't have anything ELK but from what I have read with it being in PG3 you will pick the node from your list of devices and not use the ELK button.

You could try Home Assistant.

If you just want to see the value you can see it in PG3 as Bob shows above or if you have UD Mobile it handle the nodes with more entries better.

I updated my installs Current Version: 3.0.1 [Production] Current Version: 3.1.0 [Beta]

@apnarthank you for your work on this! I downloaded the file and everything worked for me and I only change 2 lines HA_VM_MEM="2G" HA_VM_DISC="60G"

@apnar thanks for your work on this! I was giving mine 50G of space so that should not have been a problem for me. I will give it another try over the weekend.