The debugging log was so large, it was getting confusing where the Error was getting generated, but I think this made it clearer.
- Code: Select all
Jan 21, 2024 at 7:04:22 PM
Trigger ringmqtt Trigger (MQTT Client)
Ring MQTT Warning About to call fetchQueuedMessage
Trigger ringmqtt Trigger (MQTT Client)
Ring MQTT Warning About to process camera snapshot image message
Error XML Parse Error: not well-formed (invalid token)
Error In client packet stream
Error On character 481 of line number 1.
Ring MQTT Warning About to call fetchQueuedMessage
Ring MQTT Warning About to process camera snapshot attributes message
Ring MQTT Warning About to call fetchQueuedMessage
Ring MQTT Warning About to call fetchQueuedMessage
So it looks to me like it's when I go to update the indigo device state and/or write out the file, this is the code right after "Ring MQTT Warning About to process camera snapshot image message"
- Code: Select all
device.updateStateOnServer(key="snapshot_image", value=payload)
test_file = open('/Users/darrylscott/Pictures/testimage.jpg','wb')
test_file.write(payload)
test_file.close()
So I commented out the following line and the error is now gone:
- Code: Select all
device.updateStateOnServer(key="snapshot_image", value=payload)
And the externalized file is storing the image correctly.
Are you still updating the states with image? Should I have been able to update the states or is that the issue you're asking the indigo developers about?
I don't think I need to update the states with image, what I needed was to be able to store the snapshot in place that where I could using a refreshing url on a control page.
Darryl