skunkiechris

Yeah, trying to keep everything withing PG3x/IoX, but those are awesome features! Yup, I reached the same conclusion about "on" events. Thanks for the info!

There are a variety of threads on this topic, with varying degrees of success, but no central place to look, and most of the posts are older, before much of the Zigbee support was added. I am testing and will report back on several units. Feel free to ask any questions, or suggest any other zigbee presence sensors to look at (or that anyone has had experience with!) - not that I can test every one out there, but I can probably do another couple of there are suggestions. Sonoff SNZB-06P Pros: Paired easily, provides one node for occupancy. Sensitivity seems great, I've tried to lie in a still position and I can never get it to go "unoccupied" as long as I'm in the room. Relatively inexpensive. Cons: Design looks a bit too much like a camera to be used in sensitive places. Latency is good, not great, I'll probably continue to use motions for triggering the "on" event. Detects my 70lb dogs as occupants (although this seems likely with all models from what I've read.) No extra fields like coming/going, number of occupants, etc. Haozee ZY-M100 Pros: Unobtrusive design Cons: Doesn't work with IoX. It is detected, and one "main" node is added with no content, the interview just times out. Tried repeatedly. I know it said requires Tuaya hub in the description, just thought I'd give it a try. @Chris Jahn if you want any info from this device for support, let me know - not sure how realistic that is. Aqara FP1E As expected does not complete the initial interview with IoX. This would honestly be going back anyway, as it has an attached USB-A cable....making it very inflexible with wiring solutions. Also a bit expensive comparatively. Seeed via Tasmota NS (thanks to @EWhite's write up here.) Arrives over the weekend. FYI these are half the price from Seeed directly vs Amazon.

Edit: @Michel Kohanim it does indeed work! I guess it just took a few to be ready. Thanks!

Was support for this device ever added?

I think I saw this elsewhere, but when I try to activate the free one month license it takes me to the UD portal and wants me to buy a license. Pretty sure I saw this reported elsewhere here, but for now, a no go @Jimbo.Automates

Awesome thank you so much @Jimbo.Automates, I am out of town today but will check first thing tomorrow!

It's this one. "Kasa Outdoor Smart Dimmer Plug". I wouldn't be trying to dim a non-dimmable module. Plus I wouldn't expect ISY to show the dimming capabilities if they did not exist, as they do not show for other on-off switches. That's the one. Happy to send @Jimbo.Automates one of these plugs if we can get it supported! Just let me know....

This is the Kasa forum, so I was referring to the TP-Link Kasa outdoor plug (which I'm trying to use indoors). 😃

Is it at all possible to add support for dimming the outdoor module? All the control are there, it just doesn't do anything. Thanks!

Hi, Wondering if it is possible to flag when an energy event is active. I see there is a DemandResopnse object, but it says available to utility and EMS accounts only. Since ecobee can receive and react to an energy event, it seems like it would be available, and maybe that qualifies as an EMS account? Thanks!

I have an old pg2 instance running LiFX, which I'm finally ready to move to eISY's polyglot. I am using a devlist.yml file, as auto discovery is not reliable. I've put my devlist.yml into the nodeserver directory and changed the owner, but every time I start the NS, discovery ends with this (different bulb/mac address each time): 2025-02-18 09:48:54.077 Thread-4 (_discovery_process) udi_interface ERROR lifx-poly:_discovery_process: discovery Error: WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateVersion'>] from d0:73:d5:75:67:e6 (Name: None) in response to <class 'lifxlan.msgtypes.GetVersion'> If I remove the devlist file, it attempts auto discovery (and gets some bulbs) - so it is seeing the file, but it's not working. My devlist file is fine, it's a direct copy of what is in production today. Help?

Getting the attached error message when attempting to execute any network resource via the app. I have synchronized a couple of times. It seems to happen with all network resources. Thanks!

Probably too soon for any subjective feedback, but wondering how much of the performance of IoX is disk based, vs processor & RAM. As in, @Michel Kohanim, is the upgrade worth it just for running IoX, or is this more of an upgrade that is useful for running other tasks (VM's, etc) on eisy? Thanks!

Haven't had the client stopped error a single time since the change....seems to be working!!! Thanks again!!

@DavidV I went through this exactly same thing a few months ago. Opened a ticket, and the suggestion was to migrate from zooz to zmatter. (I had zmatter, just wasn't using it due to migration issues the previous time I attempted it.) I did eventually migrate to zmatter, but one of the releases prior to that (5.7 maybe) seemed to completely solve it for me. It was very mysterious, in the end not entirely sure what exactly fixed it. But like I said, it was exactly the same symptoms!

First reboot, then power cycle after reboot, both resulted in being stuck on Initializing subscription.

Same as above, Vista 21IP, EnvisaLink4. And, same in terms of used to use the IP module for Total Connect, got rid of that part some time ago as well. The only shortcoming that I have hit is that the Vista panels stop reporting sensor activity when the alarm is armed in any state. So, night, stay, away...you won't get motion, door/window, etc activity reported to IoX. Not a deal breaker for me....the couple of spots that I needed that info I've just used insteon or z-wave modules to supplement.

A unplug/plug followed by IoX restart usually works as well.

Just curious as to the reasons behind that suggestion? (I'm not disputing it lol, just curious.)

Hmmm....I hadn't actually grabbed the log yet when it started working yesterday. I just went to look now and I only see a log from today in the logs directory. I guess logs are deleted on a daily basis?

Okay, so, I did absolutely nothing whatsoever. When I left it the main device in eisy was borked, and all my programs had not specified, no nodes in polyglot. Went away, made dinner, turned on the TV, and everything reacted correctly. Looked at eisy/polyglot, and things are normal. So, I guess disregard the above!

@Jimbo.Automates Hmmmm, it doesn't seem to work after the update. My hubs.json is still in the config director, I changed nothing....but it doesn't see the Harmony at all. 2023-12-19 15:35:26,909 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-12-19 15:35:26,909 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-12-19 15:35:26,909 MainThread udi_interface INFO __init__:<module>: User=0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b9026524_14 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: PG3INIT=<redacted> 2023-12-19 15:35:26,910 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-12-19 15:35:26,955 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-12-19 15:35:27,483 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-12-19 15:35:27,712 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-12-19 15:35:27,713 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-12-19 15:35:27,714 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.6 Starting... 2023-12-19 15:35:27,771 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.16 [ISY: 5.7.1, Slot: 14] 2023-12-19 15:35:27,771 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '172.26.18.3', 'netmask': '255.255.255.0', 'broadcast': '172.26.18.255'} 2023-12-19 15:35:27,772 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-12-19 15:35:27,772 MainThread udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-12-19 15:35:27,772 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026524_14.cert key: 0021b9026524_14.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-12-19 15:35:27,773 MainThread udi_interface INFO Controller:__init__: HarmonyController: Initializing 2023-12-19 15:35:27,773 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: harmonyctrl not found in database. 2023-12-19 15:35:27,773 MainThread udi_interface.interface INFO interface:addNode: Adding node HarmonyHub Controller(harmonyctrl) [None] 2023-12-19 15:35:27,773 MainThread udi_interface.interface INFO interface:setController: Using node "harmonyctrl", driver "ST" for connection status. 2023-12-19 15:35:27,819 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-12-19 15:35:27,820 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:24_14 - MID: 2 Result: 0 2023-12-19 15:35:27,861 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-12-19 15:35:27,943 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': ''} 2023-12-19 15:35:27,943 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2023-12-19 15:35:28,115 Thread-5 udi_interface.interface WARNING interface:checkProfile: check_profile: Force is enabled. Seems like maybe that warning line is something? Thanks...

Awesome, I've updated, will let you know, thank you so much!!!

With the move to ZMatter, my motion sensors have two motion nodes now, 155 Motion Sensor, which is what they've always had, plus 380 Binary Motion Sensor. They seem to activate exactly the same. Is there any difference between the two? Thanks!

Thirdreality multifunction motion sensor, illumination sensor, and multicolor nightlight. Currently works as multicolor light with on/off, no motion or illumination sensing. Model: 3RSNL02043Z Amazon: https://www.amazon.com/dp/B0C9LNXYLL