brianp6621

Wow, great response, I just saw this now Wes, I'll test it when I get a chance.

Ok, I found a way around this. I just created a program that everytime that switch is turned off, it sets the on level back to 100%. However I noticed something else odd. When the device is off and I tell alexa to set or dim it to 50% it goes to full on first and I have to issue the command again. If the device is on first it dims to 50% on the first command. Why is that?

I am using the mobilinc portal but it seems the same thing applies there. I have always been trying percentages not just set to dim (I don't know what that would result in) so I'll try it later.

Thanks Wes, Well good to know at least that it is working as designed (did this ever change because I don't remember it being this way in my other house, in fact I'm almost certain it didn't as I used to use it in my bedroom all the time). I would strongly push for the dim not adjusting the ON level. To me if I want a specific light to have an on level less than 100% (like when I replaced my 6" incandescent cans with LEDs that were much too bright) the user should set that manually. But a temporary dim can be a completely dynamic request specific to that environment/needs at the time the command is given and shouldn't (IMO obviously) have a lasting effect.

So normally if I have a single device, I just leave it as a scene and give it a voice name. However when you have multiple switches in a scene (a 3 way setup) how would you then also go about dimming? You can't dim a scene so then you have to create a different name for the specific device/switch and dim it specifically, but then the other switches/status is not in sync (don't reflect the on/dimmed status) What is the best way to handle this?

Thanks Michel, does that mean they'll reply back here? Should I contact them directly? I wasn't sure if this was an Alexa issue, a mobilinc issue, a ISY issue...

I am a long time ISY/Alexa/Insteon user but hadn't messed with it in a while after the initial setup in the old house. Now I've completely rebuilt the system at the new house and I'm running into an issue I don't remember. I am using 2477D switches, alexa, and mobilinc connect. I have a single device for my whole bedroom. The issue happens when I try to dim. If I say "turn on bedroom to 50%" or "Dim bedroom to 50%", it properly dims the light but ALSO changes the local on setting of the switch to 50%. I can watch this in the admin console. This means that if I later just turn off the light and then turn it back on, either locally or through alexa, it does to the last dimmed setting. I don't want that. I don't ever remember my old setup doing that before. What's going on?

It seemed like it lost partial communication. I could still control all devices but I couldn't see programs, couldn't backup or upgrade the isy

Nevermind. It just required a hard reboot. Everything is back to normal.

And now after a reboot I can't access it at all. Ugh, any ideas?

Well that didn't go very far. It says "Upgrade failed: Failed uploading file (reported written size is invalid)" Now what?

I do have a 994i. I have tried clearing java and downloading the admin console again. I guess I'll try updating the firmware and see what happens.

I am running firmware v.4.2.30 and same UI. Everything has been working pretty well but I just noticed in the admin console that I can no longer see my programs/email notifications etc.They are still on the ISY as I can see them and run them from Mobilinc and they run automatically but I no longer see any of them in the admin console. I also keep getting a read/agree to the license agreement every time I connect to the admin console. What the heck is going on and how do I get back adminstration of my programs/notifications?

Got it.

So if a program disables itself and is still executing the then loop it can't later in the same then loop re-enable itself?