Need help - Input for Circuit (getting started)

[nalekra]

Getting started with njsPC. Got my Hayward Tristar communicating with RS485, looking to add my next step:

I want to take a digital signal from my heater (which I'll use that native heater app control), which energizes with calls for heat. I have a heater bypass valve that I'd like to open to allow flow to the heater.

This is what Im working on (not sure if right)
So: Digital Input to REM -> Turn on a Circuit (HeatCall) -> Valve for HeatCall Linked to RelayOUT -> Valve opens to allow heater flow. No schedule involved

I have REM working, my Inputs and Relay names are making to njsPC for selection. But no matter what I do, when I trigger the input, I can't get the circuit to enable. The input is showing triggered in REM

Im not sure if Im on the right path, or if i need to work with Triggers in REM? Any help or point to the right direction would be appreciated!

(using Home Automation 8-Layer Stackable HAT for Raspberry Pi)

[tagyoureit]

A few things here... typically you would have njsPC (or any OCP) initiate the call for heat. This would then turn on the heater and you can assign circuits to turn on based on the heater status. But, if you want to continue to have the heater as the source of truth in this case, you should check the following:

1. What do you have as a feed from HeatCallActive TO njsPC? This is likely the missing part (or at least the screenshot is missing). The trigger
2. You do NOT want a connection from njsPC -> REM for either the heatcall circuit OR the valve. Remove the connection/device values from both of those. You do correctly have the HeatCall circuit set as the trigger for the valve. This is completely within njsPC and correct.

Also, pull v10 of njsPC and REM. There was a small bug in njsPC that needed to be fixed on this code path.

[nalekra]

Thanks for the reply. I think Feed is what I was missing. But still not able to get it to work.

One thing to note, you mentioned removing links to REM in both the Circuit and Valve. Right now with the setup I have pictured above, except I change my Circuit to not have REM connection, but leave the Valve connected to REM HeatBypassON (Relay 1). I am able to trigger the feature on/off via the homepage manually. When I do this, the relay activates the valve successfully. (this is without any feed setup in REM). So njsPC is controlling my relay as expected on the valve side.

If there is a reason to do this setup in REM vs njsPC, that would be interesting to know since it's partially working..The options are there, and seems logical to set there as a newbie.

I am able to replicate the same thing by deleting the REM connection in the Valve, and set up a Trigger in REM for the relay. So now I have what you suggested, but still failing to get the Input to toggle the circuit.

If i mirror your Feed image above

(Only When Changed OFF)
Circuit on (manually) -> Input OFF (no change of state) -> Circuit turns off immediatly
Circuit off -> Activate Input -> No Change (expect to turn on)

(Only When Changed ON)
Circuit on (manually) -> activate input -> Circuit turns off (opposite of what I'd expect, Id expect it to stay on)
De-energize input, no change
Circuit Off -> Activate input -> no change (circuit stays off)

So I can't get the input to turn on the circuit with any feed combination that I've tried

I did pull v10 and node v22. All testing above is on that

Again appreciate the help and the work you're doing!

[tagyoureit]

You are close. You want the state of the input, not the object.

And you can do...
Digital input (heater, REM) -> circuit 5 (njspc) -> valve (njspc) -> valve relay (rem)

Or you can do either of below with feeds or triggers:
Digital input (heater, REM) -> circuit 5 (njspc)
Digital input (heater, REM). -> valve relay (rem) -> valve (njspc)

You have options, but getting the digital input state instead of object should get you there.

[nalekra]

That was it, thank you so much! Seems so simple once you know!
I only see Digital.State 1-4 in REM, even though my HAT has 8 digital in's.. I guess I'll figure that out some other time!

Again, thanks so much! Looking forward to building more!

[tagyoureit]

Added the extra inputs 5-8. They were missing from the JSON definition file.