csteenwyk

@Geddy I do have scenes created, but within the "room" I have a few "My Scenes" defined. I do see them listed out during discovery, but none of the "Set scene" calls seem to actually find the scene. I was trying to poke around in the python to understand what the node thinks of as a "Scene". Perhaps what I think is a scene and what the node things is a scene are different, or there is a small translation bug somewhere in the node code. I may take some time to dig into the source a bit this weekend and see if I can figure it out. My use case is to control the light colors via scenes defined in the Hue app/hub.

Are Hue scenes supported? I am trying to use "Set Hue Scene" on a group, and it keeps giving me "does not seem to have scene index X" in the log

I see that Jim is actively working on updating the library to work with newer firmware and whatnot. Probably just wait for that to be released.

To double check that, I deleted the node and installed it into a different slot. Same issue. Some examples of the messages that are being spewed in the debug log: 2024-11-20 03:00:51.254 Thread-11 (run_forever) kasa.discover ERROR discover:error_received: Got error: [Errno 64] Host is down ... 2024-11-20 03:00:51.727 Thread-4638 (handler_poll) udi_interface WARNING SmartDeviceNode:shortPoll: I: Already running ... These messages are appearing every 20ms or so. I was wondering if my poll values are incorrect? Any ideas on what they should (typically) be? Also,my versions: PG3x Version 3.2.27 Plugin 3.1.4

When I enable the kasa plugin, it appears to absolutely flood the system with log messages, lagging the entire system and preventing me from logging into the pg3 interface. Any ideas?

I am also getting the situation as @gviliunas where when adding a ZWave device (in this case an Aeotec gen7 Repeater) it just seems to time out on the interview stage. The device is connected to the network (I can exclude it again) but doesn't show up in the device list. Here is some output from /var/isy/FILES/LOG/ZWAY.LOG after including it: [2022-12-15 09:52:49.983] [I] [...] Saving configuration data to ./FILES/CONF/ZYCFG/zddx/c016c849-DevicesData.xml [2022-12-15 09:52:50.031] [E] [isy] [Device 2] Interview not complete: numCC=14 numCCDone=1 numCCAttempted=2 [2022-12-15 09:52:50.031] [I] [isy] UYZSyncManager: [Device 2] Guess Interview Done false : numCC=14 numCCDone=1 numCCAttemp When I go to exclude the device, it completes successfully very quickly. I've attached the zwave log of me including then excluding the device mylog.txt

I am still working through the ticket to try to understand why it isn't using the proper lock node in the ISY software, so I can't speak to how well it worked. I have the 500 series version, it worked well but seemed to miss messages occasionally, I am hoping the 700 series does better.

When I try to add the top level node, it is added as a "Responder" and the "Controller/Responder" button is greyed out.

Hello all, I have a few Insteon devices that are dying, so I am replacing them with ZWave. Because of that I will need scenes that have ZWave controllers and Insteon responders. In this specific instance, I am trying to control in Insteon device using the Zooz ZEN77 ZWave dimmer. I have a scene created, but I can't get the ZEN77 to be able to turn off the scene. Here are the nodes that were created for the switch. I have set parameter 13 to 1 (See Zooz documentation) to enable scenes Of those nodes, only the "Button 1" and "Button 2" ones can be added to my scene, and when I look in Event Viewer, those nodes always send "ON". I am using a Polisy on firmware 5.4.4. Any ideas or suggestions would be appreciated!

I am trying to include the new yale AYR-MOD-ZW3, which is the 700 series zwave module for their smart locks. The primary node in IOP is detected as a light, not a lock, so I can't control the device. I have tried adding and removing it, as well as resynchronizing it from the admin panel. Any ideas?

I have two hubs manually defined in the config that aren't being detected. It's almost as if the config isn't being read in from PG3. Any ideas?

Thanks for the response about heal. I am still having issues. I have a number of Aeotec Range Extender 6. If I am right next to my ISY I can add/remove devices. If I add a range extender I can communicate back to my locks but I can't add/remove a device near my locks. It's as though the range extenders won't chain anymore. Ideas? Update: It looks like network wide search for add/remove was turned off, I think that was my issue

So I upgraded and my Aeotec Siren 6 went a little wonky. I tried to exclude it from the network and that didn't work, so I factory reset it and then removed a failed node. Now I can not add it to my z-wave network. It just sits there "waiting for z-wave devices to add". Any ideas? On a side note, where did the "Heal" option go for z-wave?

Hi all, I recently switched from Amazon Alexa to Google Home and thought I'd share a pointer with you for dimming scenes. First, a bit about my setup. I pretty much replaced every light switch in my house with Insteon switches and tehn used the ISY to group the various devices into Scenes that represent a room. For example the light switch, a few lamp controllers, etc are all grouped together into a scene (e.g Family Room). Then, on the UDI portal I exported that scene to Google Home so I can say "Turn on the Family Room" or "Turn off the family room" What I can't do is dim a scene. This was explained in a few other forum posts as well as listed on the ISY Google Home Portal Integration. However, using IFTTT and shortcuts I was able to make this work. On the UDI Portal I enabled IFTTT integration and then created a separate "Inbound" event for "Dim" and "Brighten". This then provided me with two URLs like https://my.isy.io/api/ifttt/family_room_brighten/key/... https://my.isy.io/api/ifttt/family_room_dim/key/... Then in IFTTT I created two new Google Assistant actions and gave the command "Dim the family room", "Dim the family room lights", etc and then used the web hooks action to the URL above. Works great!