-
Notifications
You must be signed in to change notification settings - Fork 16
feat(test): Add soc_multilevel_sensor app #135
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
base: main
Are you sure you want to change the base?
Conversation
Only one app per type is supported, it may be improved later if needed Origin: SiliconLabsSoftware#135 Relate-to: SiliconLabsSoftware/z-wave-engine-application-layer#76 Signed-off-by: Philippe Coval <[email protected]>
Ror the record, I have been running this test during 24+ hours, no issue observed, except a wrong homeid after inclusion (see TODO), This will need to be investigated. Origin: SiliconLabsSoftware#135 Relate-to: SiliconLabsSoftware/z-wave-engine-application-layer#76 Signed-off-by: Philippe Coval <[email protected]>
84ecdad
to
f12df7d
Compare
A loop feature was added to run endurance tests, It was tested for 24+h along the next commit for sensor and an issue has been observed, it will need deeper investigation, check related tickets. Only one app per type is supported, it may be improved later if needed Origin: SiliconLabsSoftware#135 Relate-to: SiliconLabsSoftware/z-wave-engine-application-layer#76 Signed-off-by: Philippe Coval <[email protected]>
Ror the record, I have been running this test during 24+ hours, no issue observed, except a wrong homeid after inclusion (see TODO), This will need to be investigated. Origin: SiliconLabsSoftware#135 Relate-to: SiliconLabsSoftware/z-wave-engine-application-layer#76 Signed-off-by: Philippe Coval <[email protected]>
f12df7d
to
ac2ea53
Compare
A loop feature was added to run endurance tests, It was tested for 24+h along the next commit for sensor and an issue has been observed, it will need deeper investigation, check related tickets. Only one app per type is supported, it may be improved later if needed Origin: SiliconLabsSoftware#135 Relate-to: SiliconLabsSoftware/z-wave-engine-application-layer#76 Signed-off-by: Philippe Coval <[email protected]>
Ror the record, I have been running this test during 24+ hours, no issue observed, except a wrong homeid after inclusion (see TODO), This will need to be investigated. Origin: SiliconLabsSoftware#135 Relate-to: SiliconLabsSoftware/z-wave-engine-application-layer#76 Signed-off-by: Philippe Coval <[email protected]>
ac2ea53
to
def310f
Compare
controller_cli_ H | ||
controller_cli_ n | ||
|
||
log_ "net: $command: Use controller: $contid" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
polish: ensure that $contid
is set?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea, can do same with homeid
testing could be improved on each steps
I will think about it in later change (i dont want to divert too much to the origin)
|
||
local command="add_node" | ||
log_ "net: $command: Node should not be included: $nodeid ($node)" | ||
node_cli_ "$node" H |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue: shouldn't be n
? H
will not set nodeid
and the following validation will never fail?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think i am updating homeid because it is used later in unid (along nodeid)
sleep 1 | ||
case $1 in | ||
h) | ||
echo "node: Should display help" | ||
echo "node: ${node}: Should display help" | ||
;; | ||
d) | ||
DSK=$(grep 'DSK: ' "${node_log}" \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
piggyback on this PR?
DSK=$(grep 'DSK: ' "${node_log}" \ | |
local DSK=$(grep 'DSK: ' "${node_log}" \ |
local app="$1" | ||
[ "" != "$app" ] || app="soc_switch_on_off" | ||
local app_file=$(realpath \ | ||
"${z_wave_stack_binaries_bin_dir}/ZW_zwave_${app}_"*"_REALTIME"*".elf" \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question(non-blocking): is it possible to mix applications in debug and release? Not a big issue if we assume that there's only one binary per application. If the assumption is true, then head -n1
may not be needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can add an envvar to select the build mode
log_ "$task: broker is ready, operating for ${duration} mins" | ||
local args="" | ||
[ $CONFIG_PLAY_LOOP ] || args="$args -W $((60 * ${duration}))" | ||
mosquitto_sub -v -t '#' $args |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"$args"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unsure on it did you try ? it is not a single option
Co-authored-by: Laudin Alessandro Molina Troconis <[email protected]>
Change
Checklist