-
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
IOTA pump is not exposed #13
Comments
Could you please provide a copy |
Not strict JSON, but should do. It is a control value as well. |
Thanks for the output I can see your Sicce pump in the outputs. What exactly can you control on it from HA.
I'd need to work out what TBL and the "75" value are. I'm guessing "75" is the pump intensity. |
I think TBL is the schedule indicator. I’ll see what else I can set, but 75 is the pump setting (75%).
… On Aug 24, 2022, at 7:03 PM, itchannel ***@***.***> wrote:
Thanks for the output I can see your Sicce pump in the outputs. What exactly can you control on it from HA.
"TBL",
"75",
"OK",
""
]```
I'd need to work out what TBL and the "75" value are. I'm guessing "75" is the pump intensity.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
I changed it to not use the wizard, just a "Set 75". The status changed too (I also changed the pump name).
|
Thanks. Out of interest how did iOTA represent this entity in HA. I'm thinking a sensor showing intensity (Service to change intensity) and a switch with current mode. Other alternative is to use a fan sensor to represent the pump (if doable) |
I never got IOTA to work. HA removed the "official" integration and I haven't found another. I was really hoping for it to be exposed here. ;) I think it can be exposed exactly like a variable. How are you reverse engineering the REST interface? There must be a way to send the actual program numbers to the interface. |
I'm not even bothering with a proxy just using network tools in the browser as it's a simple json rest API. I'm going to guess that adding the ability to set variables is as simple as sending the same json as toggling outputs but adding in the percentage variable. If that is the case then it's fairly easy to add. If you have 5mins could you use dev tools/network in your browser and send me the output of the post request that is sent to the controller when you change the intensity of your pump. |
Request URL: http://apex.local/rest/config/oconf/3_1 Payload: Response: |
Confirmed I can turn the switch on an off like an outlet. Next is testing whether the set variable service works on it too. |
Using the developer tools, I tried to call set variable on the pump and it does not work ("unknown error" is reported). The log contains: Traceback (most recent call last): Would you like me to enable logging and try again? This is important because I don't run the pump at 100% (on/off). I run it at 50%-75%. |
The problem seems to be that the did for this object is "3_1", which is getting converted to an integer somewhere in the read from the setup. Adding quotes around it in the call solved that. |
The only problem now is that the IOTA pump is not included in the sensors list (excluded by line 22 of sensor.py?). Since I am controlling the pump via an input_number, it's not really material, but it would be nice to be able to verify that the pump is actually set to the value I requested. |
Interesting little bug, looks like HA auto converts inputs to integers and strings depending on whats input. I'll just cast the input always to a string and that should fix that use case and avoid the quotes |
I can add it back as a sensor if it would be of use. Also as mentioned I am looking at putting pumps as a proper sensor type like a fan 👍 |
As a test I changed line 22, and I have the sensor value showing up now, so it really is that simple. I'm debating whether to try to set my input number if it changes, but I'm worried about some sort of backlash effect. I'll try it. |
HA no longer has an IOTA integration, so I hoped my Sicce pump would be exposed through the Apex. It shows up in the rest interface, but I imagine that will require some custom coding to control it.
The text was updated successfully, but these errors were encountered: