Hello!
I'm using the Monitor Edge and have caused an issue w/ the custom schema.
At first, I was attempting to just thin down the schema to what I needed, so I had uploaded a schema that removed modbus, io, and just left the barebones options.
This worked, and I was able to update my Monitor One device configurations easily. However, I noticed some odd behavior - the device would not sleep longer than 900 seconds. I could make it sleep less than 900 seconds by lowering the min/max location publish timeouts, but anything set above 900 (1800 // 14400) just seemed to be 900 again.
I thought I had made a mistake on the schema, I reset the schema to default using the provided tools, however, now I get the following error message:
"The adapter rejected the commit because it was invalid"
Two questions:
- How do I get my configuration schema working again?
- How do I get the min/max location publish to function above 900 seconds?
Try using the schema tool and explicitly setting the Monitor Edge schema v2. I think the default schema tool entirely removes the custom schema, which has the side effect of turning it back into a Tracker Edge schema instead of a Monitor Edge schema. I'm not 100% sure that's what's happening, but it's worth a try.
Hey @rickkas7 thank you for responding quickly.
I did that originally, no fix for the 'mis-sleeping'. I just did it again, no fix for the 'adapter error'
Additional info - I attempted to try configuring from 'configure fleet' option and that doesn't seem to do anything.
When I click 'save and apply' the button seems to freeze like its been clicked but it doesn't aesthetically update. See below:
Other devices in the product can be configured, just not this particular device. Seems the device itself has a misconfiguration on it locally and I can't remove it.
Have tried the following:
-> cmd reset_to_factory
-> created a new product and moved it over
-> cloned the source code for monitor edge and reflashed app+deviceOs
No dice.
Determined the cause of not being able to sleep longer than 15 minutes.
The location sleep publishing was working properly, however, the system schedules a wake due to line 474 in edge.cpp.
The system schedules a wake using lowBatterySleepWakeInterval.
