All Activity

Hi All. I've setup a physical insteon switch to trigger a state variable change. I've then exposed that variable to alexa Activating the switch successfully changes the state variable, and will sometimes run the alexa routine. It's very inconsistent and I can't quite tell where the failure is. Is this just a very slow configuration or should i be expecting a quick enough of a response such that switch is activated and light comes on? Any suggestions? Thanks PB

If the plugin does not poll the Elk, how does it find the state changes in the inputs and output? Also, why are there polling parameters in the PG3X configuration page of the plugin? Also, why does rebooting the eisy solve the problem (for a few days, anyway)? I changed the log parameters as you suggested. Again, this worked flawlessly on the ISY994 with the Elk module, so something is amiss. Steve

Is it an issue with multiple Roombas? I PM'd you the file as well (at the same time I posted it.)

Most likely the Zwave device doesn't support dimming rate.

@bmercier I have not had problems with Alexa so far. However I have not been asked or offered to upgrade my Alexa skills etc..

No, it's okay for my purposes, as I won't use that value in any useful way. I have a leftover WeatherFlow Air unit about fifteen feet away from this sensor that I use for home automation purposes/reporting. The motion sensor looks to be interesting. With early testing, the response to motion appears to be really fast.

Yes the new version seems to have fixed it.

Something new started today... Every command I give now responds with "The skill for <device name> hasn't upgraded to support the latest version of Alexa. You will no longer be able to use this device with Alexa starting November 4th". I think UD needs to create an updated skill ASAP that works with Alexa Plus.

I have upgraded to the new Alexa Plus service, and the existing skill named "ISY Optimized for Smart Home V3" will be discontinued by Amazon in less than a week. Every time I give Alexa a command for an ISY device, it executes it, but then says: "The skill for <device name> hasn't upgraded to support the latest version of Alexa. You will no longer be able to use this device with Alexa starting November 4th" How can we get an upgraded skill that is supported by Alexa Plus? I don't want to lose all my device control via Alexa.

I'm sure (hope) this is very simple but I have one program that has a dimming rate speed and another that doesn't and dimming rate isn't even listed as an option in the program. The one that doesn't have the dimming rate in the program is a Z-Wave dimmer and the one that has the dimming rate is an Insteon. I hope that doesn't matter but I'd rather give more info than less. How do you add the dimming rate? Without rate. With rate. Thanks! phil

Several times the audio player has stopped working. Started with latest updates. Just now after it stopped working I noticed that no node was listed. Restating the NS restored the node and allowed the player to once again work. Also multiple tries to play the audio will sometimes start it working again. The pattern is that it will stop working after a day or two. I turned on debug , so next time I should be able to provide more information. AP version: 1.3.8 Using audio output jacks. IoX version: 6.0.0 PG3x version: 3.3.22 Thanks.

That is how sensor reports it and I just did not mess with it, I can add a secondary variable so it shows Freedom Units as well if you like

I've had a UD product for ages and have always been happy with their attentive customer service and the quality of their devices. I've been very appreciative of the supportive environment on this forum and for the very dedicated core of experts who chime in quickly. I recognize that it is very challenging to integrate automation devices that are incompatible and that Blink and other companies appear to have little interest in integrations and playing nice with each other. But more and more I'm wondering how viable this model is. Are there enough people dedicated to maintaining something that needs continual work to make things work, and enough willing to pay hundreds of dollars to do so? I know $10 for a node server is not a lot of money, but if the node server doesn't work, then what? Also, we know there are a lot of alternatives. For example, there are dozens of people working on fixing the Blink integration for Home Assistant, and it appears a solution is coming soon. There are a lot of plusses with eisy, but is that enough?

Not working for me either. Doesn't like the old auth key and can't seem to prompt Blink to send a new one. -Xathros

I already have such a program and have had for several years.

@macjeff I think 3.4.0 fixes the issues on both UDM and eisy-ui. Remember to re-sync UDM after installing the latest update. Please let me know.

Glad it is working for you. I suspect the UPS and filterlinc are not passing the Insteon power line signals and the module is getting through on Insteon RF. The power supply in the I/OLinc probably can accept an AC voltage if yours isn't pure sine wave. Some do fine others get picky.

No luck with trying to set chrome to full screen. Chrome proprieties are not available for adding command lines . Found a tablet that runs win 11, so I my go in that direction. Thanks for your help. Found that the Hermit browser does exactly what I needed.

I got the three new nodes, all populating. The temperature shows as Celsius, and I'm in Fahrenheit territory. Any way to change it?

@EricBarish Thanks for the details. It does give me a better idea of where to look for the issue. This file is not available (so the forum says). So I still don't have a full debug log showing the issue.

Seems to be working for me. I also do see the dependency error in my install.log after installing it on a system with IoX 6.0. But it doesn't seem to cause any issues. As mentioned above, Server error 500 is coming from the Emporia server, it's not something the plug-in can do anything about.

I've lost track, but if each of your random ON has an associated REST command, then our deep dive into eISY / PLM communication will be of no help. If I recall correctly, your error log did not show a corresponding IP address which would seem to indicate a process internal to your eISY. Do you have any node servers loaded in PG3?

Try the command line option (on your Chrome shortcut) suggested here: Super UserHow to set Google Chrome to automatically open up and in...I have Dell Windows tablet (I think the model is the Venue 11 Pro) and when the tablet is turned on I want it to automatically open a specific web page (lets say cnn.com for example) using Google C...

My opinion, but I don't think our current discussion in any way helps with your issue. I view this as a Alexa/rest issue and I am not qualified to help in the matter. I do very much hope that you find a quick resolution. If we continue our current discussion we will be diluting possible responses/solutions.

From my buddy who consults for Insteon (caveat - older sensors might be different): For most EISY setups, “wet” corresponds to ON, and “dry” corresponds to OFF. The heartbeat node reports the sensor’s status to confirm communication, typically every 24 hours. The EISY will display “yes” when the heartbeat is received; if it hasn’t seen one in that period, it’ll switch to “no.” When the sensor detects moisture, wet → ON and dry → OFF. Once it’s been triggered (wet), you must tap the set button several times to manually reset it to normal operation. This is a safety behavior — the device won’t automatically return to “dry” after getting wet, since floating debris or position changes could falsely suggest the water issue is resolved. During testing, you may notice it doesn’t automatically reset — that’s expected until you press the set button to acknowledge the condition.