mlritchie
commented
2 years ago When updating API Key on existing Container device for Hubitat Twillio Container, updated information is not persisted and all methods fail after that (no further SMS messages are sent).
dev:322022-08-28 05:56:48.612 pm errorgetValidated: Invalid API Credentials were probably entered. Twilio Server Returned: java.lang.NullPointerException: Cannot set property 'SID' on null object dev:322022-08-28 05:56:48.609 pm debugPhone list generated dev:322022-08-28 05:56:48.349 pm debugGenerating Twilio phone number list... dev:322022-08-28 05:56:48.347 pm errorgetValidated: Invalid API Credentials were probably entered. Twilio Server Returned: java.lang.NullPointerException: Cannot set property 'SID' on null object
This forces creating an WHOLE NEW container and devices with the correct credentials, and then updating ALL RULES AND APPS that pointed to the Twillio Devices under that old container to the new container's devices.
@SparkDustJoe I am not able to reproduce this in my quick test where I used a different Twilio account and phone number. I updated the Account SID and Auth Token and clicked Save. I then had to choose the phone number and save preferences again. Messages were sent on the child notification devices with no errors.
When updating API Key on existing Container device for Hubitat Twillio Container, updated information is not persisted and all methods fail after that (no further SMS messages are sent).
dev:322022-08-28 05:56:48.612 pm errorgetValidated: Invalid API Credentials were probably entered. Twilio Server Returned: java.lang.NullPointerException: Cannot set property 'SID' on null object dev:322022-08-28 05:56:48.609 pm debugPhone list generated dev:322022-08-28 05:56:48.349 pm debugGenerating Twilio phone number list... dev:322022-08-28 05:56:48.347 pm errorgetValidated: Invalid API Credentials were probably entered. Twilio Server Returned: java.lang.NullPointerException: Cannot set property 'SID' on null object
This forces creating an WHOLE NEW container and devices with the correct credentials, and then updating ALL RULES AND APPS that pointed to the Twillio Devices under that old container to the new container's devices.