-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request - Add Trident reagent levels #51
Comments
I don’t have a trident. Can you use the web client for the Apex, login, then manually visit the URLs for status and config, and share the JSON responses?
http://<yourneptuneipaddress/rest/status
http://<yourneptuneipaddress/rest/config
|
stauts:
config
|
You have quite the setup...
Are there controls associated with these levels, like a reset/refill or anything? If you want to jump the gun, you might be able to create a rest sensor for these values directly in HA. I believe the status URL can be fetched without logging in. |
You seem to understand the lingo... Can you use the developer tools to capture the http request to the config url when you reset these values? |
I assume you just want the api call it's making? I need refill the reagents on abaddr:7 tomorrow. I'll grab that. |
After looking at it a bit - the current integration doesn't really capture modules as sensors. You might be better off creating a rest sensor from the status url, capturing the level values from there. Are the reagents of fixed/known type? levels[0] is something specific, levels[1], etc. Or do you set what each reagent is somewhere? Like a profile or something? |
They are fixed known types which cannot be changed. Each trident(np) has three reagents in a fixed position. The "fill" just makes it go to 100% regardless how much you put in the container. Then they just estimate the levels based of number of tests run. Which is approximate at best given the pump tubing wears and fluid levels change over time as a result. Looking at the level numbers I can't wrap my head around them. They are odd. I am hoping once I reset the reagents the levels number will make more sense. So really per trident there should be three sensors for the different reagent levels. Then you could do a momentary switch for the reset. Personally I wouldn't bother the reset or prime, the level data I feel is more important to write triggers against. |
A few things:
1) The status response on my system does not have the same elements yours does, but you have the same version of system software - your type reports as AC5 - which Apex do you have?
2) You replace the reagents in packs, yeah? Or do you do each independently? I’m wondering if you only need one sensor… The replace times are in sync for a bunch of them.
3) Can you tell me what the reagent names are when you wrap your head around the level numbers? I also suspect there’s something like the amount of waste water as one of the values… (in case that goes into reservoir?)
4) I'm not at home this week, so I'm looking at my system through the fusion cloud, which may be different than in-person. I'm interested in how I can integrate this and improve the DOS/DQD integration as well, as they have some similarities, I think.
|
|
Reset the waste. Here is the API and Payload:
Payload:
TNP API:
TNP Payload:
Here are the before and after values for the levels.
After:
Looks like the first level number is the waste container, and it counts up. |
A before: API: Payload: B before: B After: API: C before: |
Looks like the container levels start at the furthest out for abc and its a count down. I am guessing the containers are 250ml and 0 is empty. It also seems like the reset payload for the put follows that same value slot as well. no idea what the second number from the right is though. Could do a get for the waste container size and that one is a count up. |
Not sure if in the API call's if you can grab the data for the reagent levels on the trident and trident NP. Would be great to setup custom level alerts in HA.
The text was updated successfully, but these errors were encountered: