Sounds like you’ve discovered issues with APEX I saw a couple of years ago.īTW, there’s a lot you can do to easily mitigate the risk of Power fluctuations on a Pi, starting with REALLY GOOD USB Power cables. If you already own an Apex, you can take a crack at parsing their status feeds, but it’s unfortunately not worth my time anymore. I know there has been some other interest in this, but between the closed nature of the Apex ecosystem and Neptune Systems disregard for the security of their product, I would advise you look elsewhere. Neptune Systems is all marketing gimmicks. While their app’s user interface might not look as pretty, the system’s reliability is far higher, and I have met several people who have had nothing but praise for them. Their platform has support for MQTT, meaning you can instantly tie it into Home Assistant with zero effort. They are also standalone devices, but they’re also completely open source. If you haven’t already, look into the Reef Angel systems. Neptune Systems’ decision to sweep this under the rug has led me to discontinue supporting their business. This is why now it sits in it’s own dunce corner VLAN, isolated from the rest of the network, and the only thing it gets access to is their AWS IPs for ApexFusion. (This also means their power strips are wired to be normally open, which is a really really bad idea in this case.) While testing my hypothesis, I could fairly reliably replicate the behavior. This led to all of the relays on their power strip flipping on (meaning my heaters, lights, pumps, everything turned on at once), and the controller completely locked up until I manually power cycled the unit. Without disclosing too much, the vulnerability that I discovered is essentially a flaw in the network stack of AOS where it simply cannot handle certain types of traffic and crashes the kernel. While I completely agree with you, and prefer to have hardware dedicated to a task that does a good job of just that one thing, the Apex is not that box. The probes that the Apex uses are just re-branded Milwaukee Instruments probes that can be bought for a fraction of the price, and there are plenty of other options available, though. You could use MySensors to pass the data to Home Assistant and use an Arduino instead, which is far more reliable. Power fluctuations will corrupt an SD card in a heartbeat. Well, a Raspberry Pi is only as reliable as it’s power source. However, I’d like to figure out if there is a XML or JSON parsing method that would be preferred. I’ve found the Development 101 documentation, and it’s given me a place to start. So, I’d like to be able to create a custom component for this, and hopefully build it up to the point that I could push it to the dev branch of Home Assistant. The contents of this file looks like this: I’m not entirely sure which would be easier to use. There are both XML and JSON formatted files located at /cgi-bin/status. The simplest way to go about this would be to pull from a status file located on the device itself. I have a Neptune Apex on my aquarium, and I’d like to look into how to integrate the two by creating a new component for this device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |