-
Notifications
You must be signed in to change notification settings - Fork 19
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
Show irrigator status #35
Comments
Hi, I don't think this is possible. The SmartPort is like a TV remote, as it is only one way. |
is there extra cables that can be added/soldered to the board that can add this type of functionality? thanks for all the great work!! |
Maybe, but I'd leave this to someome with much more expertise than me... |
Ok, now it's clearer, unfortunately I don't know SmartPort very well. I try to make another hypothesis, do you think it would be possible to use ESP8266 board as a notifier? For example, by passing the cables of the various irrigator channels on the esp and notifying if 'pass current'? It's just ideas, I hope you didn't say stupid things :) |
I think the best way to know it would work would be trying it! Tbh, I'm not an expert on this area either... |
You didn't mention what controller do you have, but if it is Hunter X-Core (rev 3.11), you can tap out the bases of triac driver transistors. There are convenient test points on the back of the PCB so soldering wires should be easy. See the schematics on my github: |
Hello, I have been using your integration for some time and I have to say that it works great. However, I would like to know if it is also possible to receive notifications when the irrigator runs a program automatically. The scenario is: I schedule the execution of a program directly from the irrigator, it activates the area and sends a notification (on a queue or on another). This way you can use both the rest api to turn on / off and its programming by keeping the controller (i.e homeassistant) always up to date. Do you think that's possible?
Thanks.
The text was updated successfully, but these errors were encountered: