Using node-red-contrib-alexa-local 0.3.22 gives the message "light bri is null in storage" in the debug tab, as well in the console logging ([warn] light bri is null in storage).
This happens every time a "turn on" or "turn off" command is given to Alexa. The node works perfectly fine. When a command like "set light to 50%" is given the message doesn't occur.
Test case
When a command like "turn on" has been given, a new file located at ../alexa-local/persist is created with the following content:
{"key":"35a66de6dabb1a_state","value":true}
This command shows the message "light bri is null in storage".
When a command like "set light to 50%" has been given, a new file located at ../alexa-local/persist is created with the following content:
{"key":"35a66de6dabb1a_bri","value":127}
This command doesn't show the message "light bri is null in storage".
When a command like "turn off" has been given, the file from step 1 gets updated with the following content:
{"key":"35a66de6dabb1a_state","value":false}
This command doesn't show the message "light bri is null in storage"!
When a command like "turn on" has been given, the file from step 1 gets updated with the following content:
{"key":"35a66de6dabb1a_state","value":true}
This command doesn't show the message "light bri is null in storage"!
Then after deleting all files from ../alexa-local/persist, the message doesn't show for the specific node!
Conclusion/workaround
For each newly placed alexa-local node a "set to 50%" command should be given to avoid the message "light bri is null in storage".
Using node-red-contrib-alexa-local 0.3.22 gives the message "light bri is null in storage" in the debug tab, as well in the console logging ([warn] light bri is null in storage).
This happens every time a "turn on" or "turn off" command is given to Alexa. The node works perfectly fine. When a command like "set light to 50%" is given the message doesn't occur.
Test case
When a command like "turn on" has been given, a new file located at ../alexa-local/persist is created with the following content:
This command shows the message "light bri is null in storage".
When a command like "set light to 50%" has been given, a new file located at ../alexa-local/persist is created with the following content:
This command doesn't show the message "light bri is null in storage".
When a command like "turn off" has been given, the file from step 1 gets updated with the following content:
This command doesn't show the message "light bri is null in storage"!
When a command like "turn on" has been given, the file from step 1 gets updated with the following content:
This command doesn't show the message "light bri is null in storage"!
Then after deleting all files from ../alexa-local/persist, the message doesn't show for the specific node!
Conclusion/workaround For each newly placed alexa-local node a "set to 50%" command should be given to avoid the message "light bri is null in storage".