Everything posted by dwengrovitz
-
Bug?: i3 4 button KPL showing 1 too many nodes
Thanks @nowandthen. I followed that same procedure and, while it was a bit laborious, it did end up fixing the problem I was having with a keypad button LED turning on/off when it wasn't expected to. I think the only thing I added to your process was viewing the device links, comparing it to what was in the eisy, and doing a restore device if the comparison showed anything other than "Identical". @Javi - I did find one odd thing in the UI when trying to configure responder settings in a scene. In some cases, the UI performed as though it didn't know what the settings were and, even after I updated them, it defaulted to something other than what had been previously set. I captured it in a short video to show what I experienced. Responder Settings Capture.mp4
-
EISY-AI "stuck" at Starting
Yes - the plugin requires configuration. There's additional info when you click on "More Info" on the Plugin About page in the Plugin store, including a working JSON example for integrating Claude. One thing that is a bit different for this plugin from several others is how the configuration parameters are setup. Best I can tell, the only parameter is "Configuration" and the full set of JSON with all of the additional config parameters gets put into the Values field next to that.
-
Bug?: i3 4 button KPL showing 1 too many nodes
@Javi Sorry for the delay in responding, but I’ve done some more testing and am still seeing some unexpected behavior with the I3 keypads. Here's the basics ... I have two I3 4-Button keypads that work in tandem to control two loads and several scenes together. Here is how the switches and associated scenes are set up: Keypad 1 (MBath Lights New) setup is: Button A (LOAD): MBath Lights New (Ctrl/Rsp) MBath Combo New (Responder) Upstairs Lights (Responder) Button B: MBath Towel Warmer (Ctrl/Rsp) Button C: MBath Combo New (Ctrl/Rsp) Button D: MBath Fan New (Ctrl/Rsp) MBath Combo New (Responder) Keypad 2 (MBath Fan New) setup is: Button A MBath Lights New (Ctrl/Rsp) MBath Combo New (Responder) Upstairs Lights (Responder) Button B: MBath Towel Warmer (Ctrl/Rsp) Button C: MBR Closet (Ctrl/Rsp) Upstairs lights (Responder) Button D (LOAD): MBath Fan New (Ctrl/Rsp) MBath Combo New (Responder) Scenes: MBath Lights New MBath Lights New (Controller) MBath Fan New A (Ctrl/Rsp) MBath Lights New A (Ctrl/Rsp) MBath Fan New MBath Fan New (Controller) MBath Fan New D (Ctrl/Rsp) MBath Lights New D (Ctrl/Rsp) MBath Towel Warmer MBath Fan New B (Ctrl/Rsp) MBath Lights New B (Ctrl/Rsp) MBath Towel Warmer (Controller) Shelly 1 Mini (Responder) MBath Combo New MBath Combo New (Controller) MBath Fan New A (Responder) MBath Fan D (Responder) MBath Lights New A Responder MBath Lights New C (Ctrl/Rsp) MBath Lights (Responder) Here’s the odd thing I am seeing: When I turn on/off button D on Keypad 1 (MBath Lights New), it should turn the fan scene on/off, but it also turns the LED for button B (towel warmer) on/off. It doesn’t change the actual scene that turns the towel warmer load on/off – it just affects the LED on that button. If I turn on/off button D on Keypad 2 (MBath Fan New), it should also turn the fan on/off, and it does, but it does not affect the LED for button B on Keypad 1. As far as I can tell, I don’t have anything configured for an interaction between Keypad 1 buttons B and D, but the system does show some kind of interaction there. BTW, I previously deleted these two keypads and associated scenes, and recreated them from scratch to go through the re-enrollment process for I3 devices on eisy (per the wiki). Also, checking the device Configuration --> Show Device Links Table for both switches shows all links as “Identical” when I Compare them with what’s in the eisy. I’m sure this is probably challenging to follow but let me know how I can best help if further info or logs would be helpful.
-
Bug?: i3 4 button KPL showing 1 too many nodes
I will do some more testing (most likely tomorrow) and will let you know if I encounter any issues.
-
Bug?: i3 4 button KPL showing 1 too many nodes
Yes - my Insteon environment is almost exclusively I3 devices, and after going through the rather painful process to delete and reinstall every one of them (per the info on the Wiki), the I3 keypads were definitely not behaving as expected. I may have incorrectly pointed to 1.4.8 as the fix for the problem, as I just updated all of the eisy code hoping to get some fixes for I3 devices even if they were still in the process of being developed.
-
Bug?: i3 4 button KPL showing 1 too many nodes
I have a bunch of I3 devices, including several I3 keypads, so I've been following this thread closely. I was having some odd behavior with two keypads not working quite as expected, so I tried the code from the staging repo (yeah - I know - the message says don't use that unless requested by UDI support). In any event, 1.4.8 does seem to make a difference for me with the buttons now controlling various loads/scenes and button LEDs turning on/off as expected.
-
eisy-ui 1.3.4 - Integrated plugins (Beta)
If I've migrated plugins from PG3 to eisy-ui, do I need to keep the ones that show as migrated on the PG3 Dashboard? Or can I just delete those?
-
I3 devices in AC
@DNewkirk I don't have a direct answer to your question about how well the I3 devices are supported under AC, so feel free to shame me for providing a suggestion, but I do have a good number of I3 switches on an eisy running beta code. From what I've seen, the I3 devices seem to be much better supported in the browser versus the old AC, so much so that I've stopped using the AC altogether. Given the AC is going away, and you also have at least one I3 device, I might suggest considering your migration to eisy-UI sooner than later. It takes a little getting used to, but it's pretty functional now and the I3 devices seem to be well supported there, especially with recent updates specific to the I3 (as shown in the release notes - see screencap below). Also - see https://wiki.universal-devices.com/Insteon_-_i3 for more details specific to the I3 devices.
-
Show PLM Links Table not showing any data
Yes - I've rebooted multiple times. The problem still exists for me on eisy-ui beta 1.4.2. The system looks like it's busy doing something, but no data ever gets displayed. See screenshot below ... eventually, the orange box goes away and the white remains, with no link data displayed.
-
System Time
Perhaps that's coming in a near release? I'm using the latest beta eisy-ui (1.4.2), and there is a Configuration Option under the System Settings that allows specification of location and display of time.
-
Show PLM Links Table not showing any data
@IndyMike Thanks. I opened the event viewer in the AC and it does see the links via in the Admin Console, but the new eisy-ui doesn't appear to show them.
-
Show PLM Links Table not showing any data
I tried Show PLM Links Table on eisy-ui (beta 1.3.11_1), but all I see is this ... should it be displaying actual data or are my links really hosed?
-
eisy-ui reboot requirements (and messages)
I'm running the latest eisy-ui from the beta repo. When we previously updated the device code via the Admin console, it almost always required a reboot. However, when updating the code via eisy-ui, it generally says the update is done (but doesn't say anything about reboot). Can someone clarify what to expect re: code updates and reboots when using the new eisy-ui? Should I reboot or not after an update, or will the UI always tell me when a reboot is needed? Also - if one elects to manually reboot - the status message displayed is yellow on a white background (when in light mode) and is pretty much impossible to read (as shown below).
-
Notification Notices: Profile rebuilt, restart admin
I'm seeing this same issue on my system. I haven't made any changes in PG3x, and I've restarted the eisy and Admin Console multiple times. I don't think this has anything to do with restarting after making changes.
-
Virtual Garage Door with Voice Control?
Yes ... this was absolutely the case. I ended up removing the Genie skill from Alexa to help minimize any confusion. We'll have to do more testing to see how that goes over time.
-
Virtual Garage Door with Voice Control?
After a few trial and error exercises, I ended up configuring up a virtual switch and setting that up as a device with open/close status via the ISY portal. That exposed the device to Amazon/Alexa for voice control (e.g., open or close the door), and the eisy integration for Home Assistant exposed the virtual switch there for initiating an automation, which successfully bypasses the requirement to verbally provide the PIN. Works great - thanks all for your comments and input!
-
Virtual Garage Door with Voice Control?
I am not entirely sure - it can open the garage door via the app UI (without a PIN) but the voice control I am using in HA is currently Alexa - and that seems to require the PIN. Thanks - it does. I am currently using a Genie opener, which has an integration for HA but not eisy (that I know of). I'm mainly trying to get around the commercial integration and what appears to be Alexa's requirement to provide a verbal PIN when opening the door by voice. Thanks, Guy - I'm familiar with setting up a virtual device and letting Alexa see it as on/off then triggering an automation of some sort. I just wasn't sure if the voice control would then have to be "turn on the garage door" vs "open the garage door" which seems a bit less natural for others in the house. I'll keep playing around with more ideas on this - but I appreciate you guys all providing some input!
-
Virtual Garage Door with Voice Control?
I'm trying to better understand if and how this plugin can assist in providing a virtual garage door that's easy to control via voice. I'd like to be able to ask my Alexa devices to open/close the garage door and have the door do that. I can currently accomplish this with the garage door integration that Alexa already knows about, but the Alexa devices want me to verbally state a PIN to take action (which I understand is for security, but the concept of me having to state my PIN out loud seems relatively insecure). Can I use this plugin to establish a virtual garage door device that Alexa knows about, and when I ask to open the garage door, the virtual device would trigger an automation in Home Assistant to control the real garage door (which HA already knows about)?
-
insteon motion sensor
I've had good success with Yolink sensors. They are reasonably priced, reliable, battery life is great, and there's a super developer (@Panda88) with a well supported plugin for eisy. You need a hub to go with them, but their hubs are also reasonably priced. Last I checked, a single sensor was about ~$45 on Amazon, ~$55 if you also get a hub, and ~$81 for a hub plus two sensors. Just a warning - they are kinda like that old potato chip commercial - bet you can't get by with just one [okay, so maybe the commercial was "bet you can't eat just one"]. I started with a couple but liked them so much I now have their motion sensors, leak sensors, vibration sensors, door sensors, temperature sensors, and even a few of their no-neutral switches in my environment. All integrated with eisy and Home Assistant.
-
New Release 1.8.45
A short press on each of the buttons did indeed update the status from Unknown to ON (DON). I'll experiment a bit more with that function, but it looks like the issues I was seeing are now resolved, thanks again! Still happy to send you a Flex Switch if you want one. :-)
-
New Release 1.8.45
Thanks for the update. At first glance, my temp sensors now all seem to work correctly. The Flex Switches also appear to work, but the status of the additional two button controllers appears as unknown in the Admin Console. I can live with that, as I don't really use that function, but if you'd like to fully support that just let me know and I'm happy to assist with logs, testing, and whatever else might be needed. Heck - message me your shipping address and I'll have Amazon send one to you to test with just to say thanks for the great community support!
-
New Release 1.8.45
@Panda88 - I tried sending you a debug log with some screenshots, but the UD message system just said "Panda88 cannot receive messages."
-
New Release 1.8.45
I am seeing some unexpected things since updating to the latest release. My Local hub now says "Alert" under "Supply Status" in the devices View, and in the Current State when listing devices via the Admin Console. I don't recall seeing that before (but perhaps just missed it) and am not quite sure how to address that if it's a real issue. The Current State and multiple other values appearing in the Admin Console device view show as "Unknown" for several devices and device types, including my Flexswitch devices (YS5709-UC) and some but not all of my temp/humidity sensors (YS8006-UC). If I manually update the device status for those devices via the Admin Console, the values seem to get updated but many return to show "Unknown" statuses again shortly after update. When updating status manually via Admin Console, I occasionally get "TCP client read response failed" messages (NS-70-YolinkLocal).
-
Can I get MyQ to work with eisy
I definitely agree with that statement. I had integrated MyQ with my ISY environment way back when and it really pissed me off when they shutdown access through their API, so much so that I eventually got rid of anything MyQ-related. I've had good success with YoLink as an add-on replacement, though I used their Garage Door Controller rather than their Finger Controller.
-
Status missing
I consistently have issues with status deltas across the various UIs, to the point where the only one I can really use is the Admin Console when logging in with my ISY credentials. Does your question apply to just the device status or also flag status? For example, in the Admin Console (login via ISY credentials), all of my devices and device flags have current states. In the Admin console (login via portal credentials), most devices are missing flag status. In eisy-ui, most devices are also missing flag status.