Everything posted by nowandthen
-
Inconsistent options when programming keypad buttons
At first I thought this was just an i3 issue. When programming a button, it always defaults to i_relay (sometimes i_dimmer) to which I have to change it to Insteon and continue programming the button. But... I'm creating a group (scene), it has 3 "regular" Insteon 8 button KPLs. Number of KPLs is irrelevant (I think). Most of the time when I program a button it offers Insteon and On/Off and number of retries is already set to 1. Fine. Easy programming. But... same KPL, same group, just moving down the list of button settings, and seemingly randomly when I program the button it offers i_relay, to which I have to change to Insteon in order to turn it off, then I have to set number of retires. What the heck is i_relay? I have no use for it, but I will assume others want it. For a "regular" Insteon KPL 2334-2 (and probably others) why am I getting "i_relay"? Does anyone want i_relay? Beuhler? I don't. My .02.
-
Bug?: i3 4 button KPL showing 1 too many nodes
Every time I set a responder setting, it always shows i_relay or i_dimmer even though I set it to Insteon earlier. It would be nice if it showed the settings that were last setup. To me, the key is if the "don't make changes.." pop out comes out on the lower right side, if it does it is updating. If it doesn't, I am guessing that it was already set to Insteon, 1 retry, etc. Showing the current settings when you open the responder would be nice. It would make it a lot easier to see what it was previously set to, rather than having to set them again with the hope that it was previously not set correctly. But it's not that big of a deal for me. Once I finally get the keypad working correctly, which is the real issue here, I'm unlikely to come back to it.
-
Bug?: i3 4 button KPL showing 1 too many nodes
@ dwengrovitz Of course follow Javi's suggestion first. What I was seeing was the programming of some buttons did not get written or didn't take by the switch. I ended up going through each button in the scenes and watched to see if the "Do not make changes..." message pops out when I make a change to the button (basically re-entering what showed to be already there). On some of my "problem buttons" (two or more leds lit at the same time), the message popped out. After that, the buttons behaved correctly. Throughout this process, I also deleted scenes, deleted devices, air gap reset devices, and created new scenes. I still had to do repeat passes through the buttons in the scenes to get them to take. But I did get them working correctly.
-
Bug?: i3 4 button KPL showing 1 too many nodes
I just noticed we have moved on to page 2 and didn't your post. Look at the previous post which I changed to state what I believe is the issue, at least on my computer (Windows 10 using Firefox). I also cleaned up the post before that, since so much of that was trying to figure out the problem. I have both new i3 keypads working as intended. Thanks for hanging in there with me.
-
Bug?: i3 4 button KPL showing 1 too many nodes
Summary: I am using the staging repo 6.1.2_14. i3 buttons seem to be fixed. The issue I believe is when changing a button in a group (scene), for example to be off, the eisy shows off but the device doesn't always get programmed. Watch for the side pop-outs saying system is busy. If it doesn't show the side pop-out then it didn't get programmed into the switch (my belief at time of this writing). Several rounds through each member of the group eventually got the switch programmed and the switch is working like I wanted. And by the way, I did not put button 1 in the group, just buttons A, B, C, D. But all buttons are in the eisy nodes list.
-
Bug?: i3 4 button KPL showing 1 too many nodes
Removed the contents. See next post.
-
Bug?: i3 4 button KPL showing 1 too many nodes
For the sake of others (and me) , you loaded the staging repo? Only the IoX under staging repo specifically says it fixed i3 keypad issues. 1.4.8 doesn't by itself address the i3 issue, meaning if you load 1.4.8 under production repo it does nothing to fix the i3 issues.
-
Bug?: i3 4 button KPL showing 1 too many nodes
For the sake of others (and me) , you loaded the staging repo? Only the IoX under staging repo specifically says it fixed i3 keypad issues. 1.4.8 doesn't by itself address the i3 issue, meaning if you load 1.4.8 under production repo it does nothing to fix the i3 issues.
-
Enhancement suggestion: Collapse All button
Collapse ALL and Expand All buttons added to eisy-ui 1.4.8. Thanks UDI!
-
Bug?: i3 4 button KPL showing 1 too many nodes
Are you saying I should try the Staging repo? That's the only package that shows "fixed i3 button issues". I guess I'm under the impression 1.4.8 ui fixed it. Sorry, I'm not a programmer so understanding all this is a learning experience for me.
-
Bug?: i3 4 button KPL showing 1 too many nodes
Yes. I rebooted, logged out and in. deleted the device, air gapped it, no luck Firefox seems to have some problems, in Chrome the red exclamation point goes away. So better there. However, for the life of me, I cannot get the buttons to respond as exclusive,, meaning only one button on at a time. Under some buttons, there is no Off or On option, only Link Type: Command, Default, Ignore and Command: Query, backlight, write changes. I used to be able to select each button, one at a time and set all others to off. I can this for buttons B, C, and D but not 1 or A. Initially they show "On" but once you select Query or backlight, or write changes, it accepts the setting but you can't go back, and those settings are not what I need. I need On and Off. Can we go back to the older version for this device? That one worked really well. I'm afraid to make any changes to the i3 keypads already in use for fear of breaking them. :(
-
Bug?: i3 4 button KPL showing 1 too many nodes
I updated to eisy-ui version 1.4.8. Was 1.4.6 Production repo. Get this error message when i click on any button of the 4-button i3 keypad. The keypad has a red exclamation point. Says query and/or power cycle. Did both. No love. Air gap reset. removed added, rebooted eisy. Nothing helps. :(
-
Waits and Schedules Before/After times not updating
Almost always, setting a number of seconds or minutes to 'Wait" does not update in the program. It simply shows "Wait" in the program. I keep trying, sometimes it will save, often not. Same with Schedules. For example, setting a time before or after sunset does not save. It will save as Sunset or Sunrise but offsets will not save in the program. I rebooted the eisy but problem persists. Edit: I use Firefox. If I open in Chrome they seem to save okay. So Firefox issue? I don't like using Google.
-
Bug?: i3 4 button KPL showing 1 too many nodes
Javi, As I am sure you know, production repo has not changed. Are you saying I should try Beta Repo (only eisy-ui updated) or even staging repo (more updates)? It says staging repo not to be used unless instructed by UDI. Edit: If I do try one of the others, can a user roll back to Production if something isn't working right?
-
Bug?: i3 4 button KPL showing 1 too many nodes
Working on Sunday!!! Unexpected dedication! Thanks!
-
Eisy UI programs not running at standard time
I believe this is an annual issue with IoX. Perhaps the same for Eisy UI. Programmed lighting did not turn on at correct time (standard time). I manually turned lights on this evening (first evening on standard time). I do not see settings for time zone or daylight savings time, but perhaps this interface uses local computer time? Yet it did not turn on lights at correct time. Maybe tomorrow it will catch up. ???
-
Bug?: i3 4 button KPL showing 1 too many nodes
Hi Javi, Is the next release posting soon?, Thanks.
-
Bug?: i3 4 button KPL showing 1 too many nodes
All are v .58. More information: I have been watching the LEDs on the face of the switch. Thinking they reflect the state of each button in the eisy, but they do not. I started watching the state (ON or OFF) in the eisy browser window. In the browser window; as I clicked each button, one by one, the state of the buttons are behaving as programmed, the button that is pressed shows ON and all others show OFF, however, the LEDs on the face of the switch are not reflecting the state in the eisy, they are staying on (well most are not behaving, button C and D work between each other but not with button B as programeed). When I query any button that is ON but the eisy thinks is OFF, the eisy then changes that button to ON. Am I missing a setting somewhere? There are a lot of settings for these switches, in a lot of places. I compared the FLAGS settings of a switch that stays in sync between it and eisy to the switch I am trying to add, which does not stay in sync. The settings are the same. I don't see a "write updates to device" or perhaps more importantly "restore device". Edit: To make sure I didn't have a defective switch, I added and set up the other "new" i3 keypad. Same behavior, switch not responding to what eisy thinks it should be/do. And buttons C and D function correctly on both switches.
-
Bug?: i3 4 button KPL showing 1 too many nodes
I'm sorry but this is not working as before. Here is my group (scene). As you can see, when button C is activated, button B and D are set to off, yet button B is still lit. I didn't add the goofy button 1 that seems to be the same as button A in this new version of i3 programming code. And when I go to check the setting for button B, or any button for that matter, it always shows "i_relay" whatever that means. Previously I changed it to Insteon so I have the option to set the button to On or Off, and set the number of retries (which historically has not mattered to me). But when I go back. it shows "i_relay" which does not allow any settings with respect to on of off. Is anyone asking for the latest i3 firmaware? suggest to go back to the previous version until the bugs are worked out on this version. Something is not right with this firmware. I have tried and tried and can't make the 13 KPL behave like the other 10 I already have up and running, added under prior version of eisy/Insteon firmware. This is painful, as I have 12 of these keypads at $80 each. I think Insteon has given you bad code or bad instructions. I'll send you a KPL and my code if that helps. Or... it's an Eisy Ui issue. I don' believe I have added and set up an i3 KPL using Eisy UI, only Console.
-
Bug?: i3 4 button KPL showing 1 too many nodes
I have 10 i3 KPLs already in the eisy. They all correctly show 5 nodes, 4 buttons 1, B, C, D and 1 Flags. These where added before I started using Eisy UI. But!!!, I think I added one on the eisy ui before the latest update and it was correct. Current firmware: Tonight I added another i3 4-button KPL and it keeps coming in with 6 nodes: 1, A, B, C, D, Flags. Nodes 1 and A respond the same as seen in the ui. It should show 1, B, C, D and Flags. I have not yet made scenes (groups) from the recently added KPL as it is not right. I have deleted it, rebooted the eisy via menu, factory reset the KPL, yet it didn't fix it. I also unplugged eisy and let it come back up, factory reset the device again, still didn't fix it. The newly added KPL keeps coming up with one too many nodes. Wrong: The other 10 already in my system are fine, 1, B, C, D, Flags. Correct: Too see if I have a bad kpl, I added another i3 4 Button KPL, but the result is the same, 1 too many nodes. All KPLs where bought at the same time (a year or so ago), so I think it's an isy issue not an Insteon issue. But I could be wrong. :/
-
Enhancement suggestion: Collapse All button
I saw a comment in another closed thread in one of the replies about possibly adding a collapse (all?) button. I would love to have this button. When in the Nodes or IoX (very similar) views, it would be nice to click one button and collapse the tree. Thanks for consideration.
-
Pg3 migration causing problems.
Sadly, I am still trying to get my ratgdo's to display and work correctly after migrating from PG3 legacy (garage door and gate in my case). I spent a few hours this morning fussing with them, but had to work on other things. Just saying, it's not always a straight forward migration, so plan to spend some time fussing to get things to work again. :( At the moment I deleted them, then managed to get them back in PG3 Legacy where they work but do not display correctly in UD Mobile. Maybe I have to delete anything and everything to do with them, then try to load directly into Eisy Plugins. Posting in case anyone else has experienced similar, and can offer advice. Otherwise, maybe tomorrow.
-
Feedback: "Mean Status" at top of IoX list?
Why? It's not something I look at and say "Oh! Something is not right." For me, wasted screen space. There are so many devices in my system I can't possible discern any value from this. What am I missing?
-
Feedback on new web based UI
How many "other users"? I for one, like color. "Other users" must like 1955. I like 1966 (and beyond), The Wonderful Wold of Color. KISS. Easy to see, easy to comprehend. No column sorting, it's just there. Please reconsider keeping color for on/off and % on. Anyone else?
-
Pg3 migration causing problems.
Thanks mmb Reboot from system menu worked. I see notification in UD Mob1le that PG3 server started. I now see a menu item pg3x (legacy) whereas before it was just PG3. PG3 devices loaded. I now see my ratgdo devices in the nodes tree. I should know to reboot by now.