-
Notifications
You must be signed in to change notification settings - Fork 17
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
Property value in the EPC_FUNCTIONS constant #67
Comments
nao-pon
added a commit
to nao-pon/pychonet
that referenced
this issue
Jan 30, 2024
nao-pon
added a commit
to nao-pon/pychonet
that referenced
this issue
Jan 31, 2024
nao-pon
added a commit
that referenced
this issue
Feb 3, 2024
* Property value in the EPC_FUNCTIONS constant Rel. #67 * Adjustment of status wording
nao-pon
added a commit
that referenced
this issue
Feb 3, 2024
nao-pon
added a commit
to nao-pon/pychonet
that referenced
this issue
Feb 23, 2024
rel. scottyphillips#67, EPC_SUPER_FUNCTION too process
nao-pon
added a commit
that referenced
this issue
Feb 23, 2024
rel. #67, EPC_SUPER_FUNCTION too process
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm working on including a property value in the EPC_FUNCTIONS constant.
It is possible to simplify the ENL_OP_CODES definition by referencing EPC_FUNCTIONS on the echonetlite integration side.
for example. . .
The text was updated successfully, but these errors were encountered: