Hey, I was wondering if anyone has any of the issues I'm experiencing with the Monitor One for Fleet Management. Specifically: I'm unable to change any of the gateway settings, both on a device assigned to development and from a fleet standpoint. I've shrugging it off since I had been using custom firmware for some time, but I'm leaning into the bulk OTA update side and need to fix things now.
When I try to update a 'development' device, it gives an error that the 'adapter rejected the commit because it was invalid'. When I try to update my fleet settings, it says "The following settings modules were sent by this device but are not supported by your schema: rgb". The modbus settings are visible, so it's not like I've uploaded a tracker-one schema. I've only got one device in the product at the moment, so we shouldn't have any major conflicts.
I've since downloaded a fresh copy off of the github, both the active release and the 'v2 release' off to the side on the github page. The only change that I've made is to update the product revision number from EDGE_PRODUCT_VERSION to 3,4,5... historically using the Tracker One in a separate product, I had to have a certain version number (all mine are v19 at the moment). Maybe that's the issue?
I've tried using the 6.1.1 toolchain and the 6.2.1 toolchain to no luck. I'm trying to create a protected product, so I'm limited to using the >6.1.X now.
I've also searched around the firmware itself and it seems to use a few RGB resources, but it seems pretty integrated.
Anyone have a fix to the default provided firmware that lets it play nice with the v2 monitor-one cloud schema? Thanks
It is probably not a toolchain or firmware issue. The rgb panel exists only on Tracker One, not Monitor One. The error message indicates that a device has rgb settings, which means it's using a different schema (Tracker) than is currently configured in the cloud (Monitor One v2).
It can be a little tricky to get out of this situation. The first step is to reset config to factory by sending a command OTA to the Monitor One. This alone may solve the problem. Changing the firmware on the device does not change the configuration settings.
If the device is a development device and has a per-device configuration, you may need to reset that as well. You can use the per-device configuration tool.
Unfortunately, if you have a fleet of devices, it could be any of the device in the fleet causing this issue.
3 Likes
The tools look good. I tried the reset to factory and it allowed the device to work and update the config for development, which is an improvement.
However, I still get an 'rgb' error on the fleet settings. I made a fresh new product and uploaded the v2 firmware and got the message. No devices added at all, past or present, in the product.
I noted when using the per-device config tool that the 'Restore Product Default" (different than 'restore-to-factory') it gave me a config with:
"rgb": {
"type": "tracker"
},
It also defaulted to sleep-enabled, which was a little frustrating.
Upon download of the schemas, this 'rgb' json object was also present. Interestingly, I also got errors when trying to 're-upload' the code with and without the json, where it said gave me:
- should NOT have additional properties {"additionalProperty":"rgb"}
- should be integer {"type":"integer"}
Removing the rgb solves that one, but I wasn't able to find the 'integer' error cause. Regardless, there weren't any modbus specific configs in that section, so it appears that my 'product default' is still a tracker in spite of changing the schema.
