UD2)17rrh

Thanks so much. Very helpful. So I have the scene set up in the portal and the spoken word identified. Now what I get from Alexa is "dining room is not responding. Please check its network connection". Nothing happens with the lights upon the spoken word. Frustrating as all the other spoken word command's function well.

Thanks for the reply. At the moment, I only have the scene active in my IoX admin console. In my Alexa app, I’ve had the UD “ISY Optimized for Smart Home V3” skill enabled for years, I've also run the device discovery command. Not sure if that helped. Voice control of the scene worked fine when it included just one switch. However, after adding a second switch, it's that second switch that does not respond, while the first continues to work as expected. Since there’s usually a considerable gap between when I use the admin console or add new switches, I don’t always remember the optimal setup process.

Thank you for the reply. This keypad is at least that old, likely a few years more, so this well might be the situation as everything else with the keypad works well. I'll tag this keypad for an upgrade.

I have two Insteon on/off lights in the same room. Using the admin console, I created a scene with both lights in it. In the notes section for the scene, I designated a spoken word. Only one of the Insteon lights responds to an off or on command, spoken via Alexa (using with the set spoken word of course). I do need both to respond. Anything obvious I am missing? Do I need to refresh the Alexa app? Thanks.

I have an Insteon 6 button keypad. The main on/off switch is controlling a kitchen light. Elsewhere in the kitchen are other lights all on their own Insteon On/Off switches. I programed a scene for button B on the key pad to turn off all kitchen lights. All the single Insteon on/off switches respond perfectly every time but the keypad's own on/off switch never responds. All switches, including the keypad on/off switch are set up as responders to keypad button B. Why doesn't the keypad on/off switch respond? Thanks for any help.

Thank-you @dbwarner5 and @firstone for your help. So I am afraid to say (aka embarrassed) that this was operator error on my part. I pressed the Hue Hub button and immediately restarted the plug-in. Within a few seconds everything populated. Thank-so much for your help. I also see all my Hue bulbs in my admin console, and I am happy to start programming.

Thanks @dbwarner5 for your help. Currently running PG3x v 3.2.27. IoX running 5.8.4. It has been for a while. I previously did delete the plug in and reinstall. I did not get the request though to press the button on my hub. I also tried starting and stopping the plug in. No success at this time. Here is a portion of the error log...thanks again. 2025-01-18 22:16:33.799 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2025-01-18 22:16:33.800 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026579_3.cert key: 0021b9026579_3.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2025-01-18 22:16:33.800 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: huebridge not found in database. 2025-01-18 22:16:33.800 MainThread udi_interface.interface INFO interface:addNode: Adding node Hue(huebridge) [None] 2025-01-18 22:16:33.800 MainThread udi_interface INFO hue:__init__: Started Hue Protocol 2025-01-18 22:16:33.801 Interface udi_interface.interface INFO interface:_startMqtt: MQTT keepalive is 300 seconds. 2025-01-18 22:16:33.850 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with Reason code: Success 2025-01-18 22:16:33.850 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:79_3 - MID: 2 Result: 0 2025-01-18 22:16:33.892 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Successfully for Message ID: 2. Reason codes: ['Granted QoS 0'] 2025-01-18 22:16:33.975 Thread-2 (parameter_handler) udi_interface INFO hue:connect: Saved bridges information is not found 2025-01-18 22:16:33.975 Thread-2 (parameter_handler) udi_interface INFO hue:connect: No bridge configuration found, trying discovery... 2025-01-18 22:16:33.976 Thread-2 (parameter_handler) udi_interface INFO phue:connect: Attempting to connect to the bridge... 2025-01-18 22:16:33.976 Thread-2 (parameter_handler) udi_interface INFO phue:connect: Error opening config file, will attempt bridge registration 2025-01-18 22:16:34.008 Thread-2 (parameter_handler) udi_interface INFO phue:get_ip_address: Connecting to discovery.meethue.com/ 2025-01-18 22:16:34.055 Thread-2 (parameter_handler) udi_interface ERROR hue:connect: IP Address OK. Node Server not registered.

The state did not change to 0 when I unplugged my Hue hub.

Thanks. Here is the log: 2025-01-18 12:30:54.604 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-01-18 12:30:54.606 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-01-18 12:30:54.606 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-01-18 12:31:09.615 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-01-18 12:31:09.616 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-01-18 12:31:09.616 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-01-18 12:31:24.622 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-01-18 12:31:24.622 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-01-18 12:31:24.622 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-01-18 12:31:39.631 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-01-18 12:31:39.631 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-01-18 12:31:39.632 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-01-18 12:31:41.796 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2025-01-18 12:31:41.796 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2025-01-18 12:31:41.796 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS longPoll message {} from Polyglot 2025-01-18 12:31:54.641 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-01-18 12:31:54.641 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-01-18 12:31:54.642 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-01-18 12:32:09.647 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-01-18 12:32:09.647 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-01-18 12:32:09.647 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-01-18 12:32:24.653 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-01-18 12:32:24.653 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-01-18 12:32:24.653 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-01-18 12:32:39.657 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-01-18 12:32:39.657 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-01-18 12:32:39.658 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-01-18 12:32:41.800 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2025-01-18 12:32:41.801 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2025-01-18 12:32:41.801 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS longPoll message {} from Polyglot

@dbwarner5 yes, my Hue iOS app sees all my Hue bulbs and accessories. @oberkc Yes, Hue installed and not the emulator. Thanks for helping.

Thanks for the reply @dbwarner5. So I see the Hub just as the screenshot above shows (yes, State (ST) is a value of 1). But no Hue bulbs. I removed the plug-in and reinstalled it. As above, everything looks good (ST = 1) but still no bulbs.

Hi. Bringing back an issue I had some time ago but did not resolve. EISY and Polygot 3 show that the Hue install was successful. That is, I see a green "connected" status in Polygot. However I do not see any Hue devices added when I review my admin console. I tried a reboot of the system along with several attempts with "re-discover bulbs". Any thoughts? Anything obvious I am missing? Many thanks.

Thanks for the replies. The current fan light/fan control (all in one) is not Insteon. I might need to investigate the optional wall mount.

I have a room where the combined fan/light control switch is the other side of the room from the door. I'd prefer to also control the fan and its light at the point of where I enter the room. I have an Insteon based system. Without cutting into joists and drywall and running a wire from a new additional switch at the door to the existing, is there a better way to do this? I suppose the easiest could be a remote control at the point of entry to the room? But I'd like a switch if possible. Thoughts welcome! Thanks.

Thank-you and bookmarked the how-to guide. Thanks for sending.

Thank-you!

Thanks for the thoughts. I will give the latter idea a try. Does it matter at all if the tag continually senses motion and keeps sending an on signal to the switch? Would use of a variable program help here?

I think I have it correct. The Wireless Tag motion senses motion and the light turns on. All good to this point. But the light does not turn off. Why is the code wrong? Thanks for the advice. Utility Room Motion If 'Wireless Tags / Utility Room Sensor' Event State is Detected Movement Then Set 'Basement / Utility Room' On Wait 15 minutes Set 'Basement / Utility Room' Off Else - No Actions - (To add one, press 'Action')

Thanks @Goose66 and @Techman for the replies and fixed.

Did the upgrade. Cannot log in to admin console as the system wants me to use admin console 5.7.1. Where do I find that?

EISY and Polygot 3 show that the Hue install was successful. However I do not see any Hue devices added when I review my admin console. I tried a reboot of the system along with several attempts with "re-discover bulbs". Any thoughts? Thanks.

Thank-you @Geddy for your reply. I didn't get the red light so proceeded to pull power and restart. I now have access to Polygot home page so all seems well.

Hang on, trying things from here....

I transferred my programs successfully from my ISY to EISY. When I try to launch polygot v3 from the admin consol or IoX finder I do get to the polygot v4 login screen, then enter my login ID and password but program does nothing from there. I have rebooted to EISY. Anything obvious I am doing wrong? Thanks.

Thank-you larryllix. Very helpful.