skunkiechris

Assuming you mean try that literally? It did not work: 20:52:34.393 CMD: publish tasmota/stat/%topic%/STATE 20:52:34.409 MQT: tasmota/stat/%topic%/STATE = and it published nothing in explorer. If I'm being an idiot and that is not what you meant, feel free to chastise me. 😛

HI all, Thanks for the input. Since these are set up and working now, I'll stick with Tasmota for the time being. If anyone else uses these, the rule for making them report real time status for presence is: ON HPSensor#Human#Presence=Occupied DO publish tasmota/stat/DR_Occupancy/SENSOR {"HPSensor":{"Human":{"Presence":"Occupied"}}} ENDON Obviously replace DR_Occupancy with your own sensor name, but it's working perfectly. Thanks to @Goose66 for getting me here! Edit: Weirdly on all 5 of my devices, the unoccupied rule fires continuously, with no occupancy between, no idea why - maybe will look for help in the seeed forums. However, unoccupied isn't nearly as important, so I set the TelePeriod to 30 and turned the unoccupied rule off, so I'll get immediate occupied, and up to a 30 second delay for unoccupied - but since the lights wouldn't be turned off immediately anyway, not so important really. Granted I'd still like to fix it out of principle, however, not sure that will be possible. Seems like the unit is returning unoccupied constantly. I tried blocking one of them and it still constantly reports unoccupied. Shrug. Edit2: AHhhhh, Goose was right, these sensors report status constantly, so the rule keeps firing. Going have each rule disable the other one until it's no longer true. Solved! Edit3: Turns out Berry scripting has a built in "only run once on a status change" function, so all good to go even simpler!

In case anyone runs into issues with this, the above was correct, however one of my incorrect attempts knocked the plugin listener offline. So all I had to do was restart the plugin. One thing I can't find now, is documentation on what the trigger is that we need...I highly doubt anyone knows this, but I'm just not finding much documentation about the tasmota firmware on this sensor (which would presumably give triggers out). @EWhite looping you in to see if you have insight on documentation. Thanks!!

1. I did set the TelePeriod to 600 when I was testing to avoid that problem. 2. Tried with the command above, did not get a DON, presence change in the console. 3. Will do so now!

Okay I've posted a bunch of idea and they're all wrong. I can't figure out how to get the message in for Presence Occupied. I've tried every way I can think of, I've just been publishing from the console, but nothing changes IoX. Here are the logs from the TelePeriod: 15:54:40.406 MQT: tasmota/tele/DR_Occupancy/STATE = {"Time":"2025-04-18T15:54:40","Uptime":"2T02:31:13","UptimeSec":181873,"Heap":130,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":4,"Berry":{"HeapUsed":25,"Objects":420},"Wifi":{"AP":1,"SSId":"FCZWH","BSSId":"52:D9:E7:91:42:E2","Channel":6,"Mode":"HT40","RSSI":76,"Signal":-62,"LinkCount":1,"Downtime":"0T00:00:03"}} 15:54:40.418 MQT: tasmota/tele/DR_Occupancy/SENSOR = {"Time":"2025-04-18T15:54:40","HPSensor":{"Human":{"Presence":"Unoccupied","Body Movement Parameter":0,"Activity":"None","Motion":"None"}}} Based on other examples I've seen, I think it should be something like: publish tasmota/stat/DR_Occupancy/SENSOR {"HPSensor":{"Human":{"Presence":"Occupied"}}} It creates the following entry in MQTT explorer uinder tasmota/stat/DR_Occupancy/SENSOR { "HPSensor": { "Human": { "Presence": "Occupied" } } } Here's the SENSOR content for that device: { "Time": "2025-04-18T14:10:27", "HPSensor": { "Human": { "Presence": "Unoccupied", "Body Movement Parameter": 0, "Activity": "None", "Motion": "None" } } } This seems right-ish, but the status in IoX never changes when I manually put occupied in there. I may be way off base, or just putting it in the wrong place, but this was what I could gather from examples and documentation. I did try putting all parameters in there but it made no difference, still didn't work. As far as the trigger, I think I need to use status change on GIPO06 or 7? which appear to be the only active options... Any pointers/help you can give @Goose66 would be appreciated!!

Maybe I'm missing it entirely, I do not see a way to export the data....and there are (presumably) no status update messages as there is no /stat for these devices?

The occupancy delays is set to 0 on all of my devices. @Goose66 Can I send logs? I have MQTT explorer, just not sure what to send.

I've had zero problems with them....weird. The only two things I can think of is 1) do you have a strong zigbee network or are you adding it close to your eISY/Polisy? 2) My zigbee is on "on", no idea what the difference is though, maybe try flipping it?

Right, I wouldn't think that should go too low. Yes, I did see and set the teleperiod. I was just under the impression an event would trigger reporting, vs waiting for a time to come around. So that's (obviously?) not true then? Thanks!!

Hi @Goose66, I have two of these hooked up, but they are not reporting real time status changes. They seem to only update on short poll. Is there something I'm doing wrong? Edit: I set the console teleperiod to 10 again, and now I seem to get changes reported every time we hit the 10 second mark. Is this how it's supposed to work? I thought a device event should trigger a status change? Thanks!

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.) FYI these are half the price from Seeed directly vs Amazon. Pros: Easy setup following the guide posted linked above. Multiple parameters visible in IoX Cons: Form factor is larger and much thicker than expected. I cannot reliably get the node server to update on status changes from the device. I've tried two and the same results. It's immediate to detect/not detect on its web interface, but IoX update sporadically, doesn't always catch status changes and when it does, they seem to be very delayed. Edit: It seems the devices do not proactively report a status change, they wait for the MQTT poll. That's a big downer IMO. Final Edit: With lots of help, got these reporting real time sensor status changes, so all is well. Now that I've been using them, they seem to have some advantages over the Sonoff, such as they seem to be more selective over what constitutes human presence.... Ex these ones do not detect my 70lb dogs, nor do they react to the outside, but are still flawless at detecting presence. Final thoughts: We have at least two good options, liking both the Sonoff and the Seeed. Given their form factors, they have different advantages: The Sonoff is good for targeted applications. Such as when you need to mount the sensor in a corner, or other places than a flat wall, as it can be aimed. The Seeed is good for when you are placing it in the middle of a wall, as it has great detection at almost 180 degrees. If anyone has any questions on the above, please post or DM me! (Especially on setting up the Seeed/Tasmota sensors. I'd post a '"how to" to follow-up EWhite's to do, but it doesn't seem like there's much interest in using these with Tasmota anymore.

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!