We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Platform: RPI 4B Bookworm Board: Sequent 4rel4in v4 Latest nodejsPC and REM (recently installed) FYI, Chem Controller relay feed to NodejsPC works fine.
Following the directions from https://github.com/rstrouse/relayEquipmentManager/wiki/Generic-Devices#raspi-cpu-temp Relay 1 never energizes and REM throws the error below:
error: Sequent 4rel4in v4 error setting I/O relayState channel e out of range. verbose: Feed internal/Internal Devices sending relayState: {"id":1,"state":true} to i2c:1:2 debug: 14 - Sequent 4rel4in v4 Executed read command 0x03 byte read:0x00 debug: 14 - Sequent 4rel4in v4 Executed read command 0x00 byte read:0x00 verbose: Emitting: /chemController : {"acidPump":false,"id":50} verbose: Feed njspc/PoolController sending acidPump: false to chemController
I also posted this issue over at: https://github.com/tagyoureit/nodejs-poolController/discussions/938 and tried the different javascript code with the same results.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Platform: RPI 4B Bookworm
Board: Sequent 4rel4in v4
Latest nodejsPC and REM (recently installed)
FYI, Chem Controller relay feed to NodejsPC works fine.
Following the directions from https://github.com/rstrouse/relayEquipmentManager/wiki/Generic-Devices#raspi-cpu-temp
Relay 1 never energizes and REM throws the error below:
I also posted this issue over at: https://github.com/tagyoureit/nodejs-poolController/discussions/938 and tried the different javascript code with the same results.
The text was updated successfully, but these errors were encountered: