xlurkr

Manufacturer Name Aqara Model # FP300 Link to sales/availability site(s) Aqara Presence Multi-Sensor FP300: 5-in-1 Detection Key/desired function support Occupancy (must), Illumination (very important), Temp and Humidity (nice to have) This is one of those cool new mmWave occupancy/presence multisensors. It's battery powered and is said to have a multiyear battery life! I have one, bound to my Hubitat hub, but I'd love to see it supported on ISY. Here's a thread where we've been talking about it: Aqara FP300 Thread & Zigbee Motion Sensor - ZMatter - Universal Devices Forum -Tom

It is just that. I have one primarily because I wanted to start experimenting with Lutron lighting a few years ago, and it has by far the best support among general-purpose hubs for Lutron (until RA3, that is, because they refuse to support LEAP until they get permission and documentation from Lutron). I mention that because I'm not suggesting it as a solution to this specific problem. I happen to have one and already knew it can easily interact via REST with the ISY and is easy to program, so when I found through my searches that there was a skilled user working on full support for the FP300 (and all other Aqara presence sensors) I went that route. Support for this device could be just as good on the ISY - the missing ingredient is someone who has the skills AND the interest (especially self-interest) and motivation to fully integrate it. I'm going to add my own request to the Zigbee support request thread right after finishing this. If I may make a suggestion, for you I'd recommend either getting the Smilewolf sensor @JP commented on above, or another one anyone else has reported works with the ISY (if one exists) if your primary motivation is to experiment with a mmWave sensor. Or maybe return the FP300 to Matter/Thread mode and see if you can get it to work that way, somehow. From my searches it seems like it can reliably report presence that way, but it exposes fewer setting to tweak and has shorter (but still good) battery life. I like my Hubitat hub, but it seems like overkill and unnecessary additional complexity to support just this one item. -Tom

I finally got around to linking this thing (in Zigbee mode) to my Hubitat hub. It's pretty great. It will reliably turn lights on within 1 second of detecting motion (or presence, if you prefer), and off within about 15 seconds of detecting none. And it senses even small amounts of motion all the time, without turning lights off just because you're not moving frantically, i.e., no arm waving or standing up out of your chair required. And it has an ambient light sensor that seems to respond in about 1 second, and temperature and humidity. This is all with the default device and driver settings, which appear to allow for a great deal of tweaking. I could really see relying on this thing to completely control lighting in many of my rooms. I have it sitting on my desk pointing at me at the moment. In the coming days I will experiment with other locations, and some of the settings in the device and its driver. But so far so good! Count me in for begging UDI to provide support for at least one mmWave presence sensor - and this one seems to be a good candidate. -Tom

btw, another small difference is that the eisy has an HDMI port, so you can plug in KVM and tinker with FreeBSD, if you're into that sort of thing. You can also run a GUI on it - a GUI for FreeBSD, that is, not the eisy-ui discussed above. Not needed at all for the things most of us do, and frankly a little risky if you don't know what you're doing. -Tom

I doubt having the hub would help you much. A quick search turned up IFTTT and Home Assistant integrations for the hub, but no wide-open interface like the REST interface on the ISY. So you'd have to have a third layer, in addition to the Aqara hub and your ISY. I plan to use my FT300 with my Hubitat hub (one of the links I posted above) which has a well-documented REST interface that should allow me to control any lights on my ISY based on the sensor output. But we'll see. I will post my progress here. If it fails, I might try the HA route, but frankly I'd probably be in over my head. As far as direct support from UDI goes, it's probably too bleeding edge for them to worry about right now. But if these presence sensors work as well as many users are saying - truly allowing you to have a light on in the room whenever someone is there, leave it on even if their movement is minor, and turn it off immediately once they're gone - UDI will have to support at least one version of one of these at some point. Who knows? Maybe Insteon will make one... -Tom

btw, here are links to the two threads (I hope these are correct!) [BETA] Aqara Multi-Sensor FP300 (PS-S04D) - ⚙️ Custom Apps and Drivers / Custom Drivers - Hubitat Aqara FP300 Early Zigbee Setup : r/homeassistant -Tom

From what I have gleaned from the other fora, you do not need an Aqara hub. Also, in the other fora, there is a mention of a need for some modification to the existing drivers on the respective hubs (HA and Hubitat). The authors of these drivers are participating in the threads and making the changes. Therefore, I would expect that the default behavior in IoX will not be ideal at the moment. If we all contribute to this thread as we experiment with our FP300s, and maybe additionally make requests in the general Zigbee support threads here, the team at UDI will likely support this device as well as it can be at some point in the near future, as they have demonstrated numerous times in the past. -Tom

I've been following threads on the FP300 in HA and Hubitat fora. I have one on order. In both those threads, they talk about using the Aqara app on your phone to convert from Thread (default as shipped) to Zigbee before adding. Did you do that? -Tom

Regardless of how you might want to use the Polisy in the future, I highly recommend you upgrade it to the latest version. There was at least one upgrade case in the past that required reimaging the device. Some day in the future it will probably be impossible to have UDI support such an upgrade. And if you do decide to spend some time on it now, you could always run one or more of the free plugins on it, just to keep up-to-date on the biggest differentiator between Polisy/Eisy and the ISY99 (well, maybe tied with the Zigbee/Matter support, but that isn't really fully baked yet). -Tom

Makes sense. But what is the smallest drive ever shipped with a Polisy? Both of mine are 32G, so why not have that be the default partition size? -Tom

I think - not sure - that the image I flashed was already 6.0. It was definitely FreeBSD 14.3 based on the name (though it was misspelled "poilsy" as @larryllix correctly documented.) That's why I said it didn't seem like the upgrade packages that I did after the reimage actually did anything. Also, I think I had a 6GB partition from the start. Perhaps Michel is creating these on the fly as each request comes in, and basing each new one on lessons learned from the last one. I know that the link to my image was time-limited, because it timed out and I had to ask for another. Meant to prevent sharing of images, potentially "bad" early ones? Or maybe it's tied to my UUID somehow, for the purpose of tracking portal subscriptions? -Tom

Thanks. I found your older post and just did this on my Polisy. In addition to the zudi substitution, I had to "sudo" the autoexpand command. It looks like it worked. Two additional comments: I'm not sure the update packages that I ran after reimaging did much, if anything. And it probably all fit in the 6G original partition because this is an empty Polisy. Now, I'd love to hear from anyone who has run upgrade packages on a Polisy and had it work correctly. I still have not upgraded my working Polisy, and I don't want to without more confidence that it will work correctly. -Tom

I saw this, but I can't find it. can you repost? Thanks. @Michel Kohanim your image did get me going again, but I'm concerned about the disk image size. Should I be? Is there a reason that the total disk space is so much smaller than before, and the used amount (capacity) is so much higher? -Tom

Looks like I got a small partition. This is a 32GB SSD. Everything is working, but not a lot of free space. I'm going to check out the video. -Tom

Fortunately, this is a spare unit, and it had no devices, programs, etc. So I guess I'll reimage, check the size of the image, and try to upgrade again. I might as well reenable the portal subscription, too: it doesn't cost much, goes to a company with great support, and would allow me to do more kinds of tinkering if I leave this unit in service. -Tom

The one I was upgrading had a lapsed portal subscription, but I hope that didn't have anything to do with the failure. btw, Michel got back to me and told me to flash it. I have the USB device from back when they all had to be flashed if they had the old FreeBSD version, but I'd rather try anything else first. Anyone have any suggestions? -Tom

OK. While the Launcher has at times failed to find one or more of my Polisy automatically, it has never failed when I used the add button and put the address in manually. Until now. And never have I had to use portal credentials to log in. -Tom

@larryllix: I saw you mention this in another thread. In what place and at what time are you referring to this login? As I said above, I plugged in my Polisy, the Launcher found it, and I clicked on its entry and attempted to launch the AC. Without any login request appearing, it told me that I needed to upgrade to 6.0. As I wrote, the first time I clicked no, and it terminated. The second time I clicked yes, and it threw up a dialog warning not to interrupt it. I dismissed it and my Polisy beeped a few times. Since then, I can't get Launcher to find it, which I assume is because the isy service isn't starting. Where can I log in with my email address? -Tom

btw, I should document for future posterity that your modified command for getting a new (different) dhcp lease did work for me, but since I was connected via ssh on a Polisy and not keyboard/monitor on an Eisy, as MIchel's instructions assume, I lost the connection, had to get my router to tell me the new address, establish a new connection to be able to restart udx again, only to still find that the isy service didn't start. Kinda illustrating my point about how we Polisy owners are a bit of an afterthought. -Tom

No offense, but I think I'm going to wait for a response to my ticket at this point. I promise I'll come back and post whatever I learn from UDI about what the problem was and how they fixed it. Looking at my old posts, and some of yours and larryllix's I get the sense that they have a tendency to leave out a step or two in their automated upgrade procedures for Policys. Understandable, if all they have and use these days are Eisys. -Tom

I just tried it again. The "pkg install" command doesn't have any error messages and installed one package - the rest were already there. It's the udx restart that has the error messages - something about needing to use the -H flag when running pip via sudo, and a pkg named "serial" not found. isy service still not running. According to Michel's recovery instructions, it must start for the Launcher to find my Polisy, and let me launch the AC, and finish the upgrade by clicking on upgrade packages? -Tom

Posts crossed. Yes, I did all those steps, and thanks for explaining the re0 thing. I'm assuming that just clears up IP addressing problems, but my Polisy has maintained the same address the whole time, and I have always been able to reach it via ssh. Many messages scroll by when doing the pkg install and udx restart, and some of them look like error messages. -Tom

I have a ticket in, and it wouldn't surprise me if UDI intervention will be required. The system is responsive via ssh, it's still on FreeBSD 14.1, I don't think there's any upgrading going on, and for some reason their documented recovery steps don't get the isy service to start, or the Launcher to let me launch the AC. So for the moment, it's a fully functional FreeBSD computer and a fully useless Insteon and home automation controller. But I have faith. At least it's more than a brick! -Tom

Nothing is happening, and since I can't launch the AC, I don't know how it would tell me to reboot. -Tom

I doubt this has anything to do with the "small image size" issue. I really don't understand why I was asked to upgrade to 6.0 when I connected via the launcher. I haven't read anything about that anywhere. And why doesn't it do that with my main Polisy? The release notes suggest that the upgrade requires manually clicking "upgrade packages" in the AC. -Tom