Hey. I got a few monitor ones to begin testing with and have been digging in to get the features we need working more. One of the features I'd like is the modbus one, which I'd like to begin testing via the documented cloud comms as I'm having continual issues with getting the built-in library working.
I created a new product for the monitor ones and followed the steps in the monitor-edge-firmware page to clone and flash the firmware on the device.
When I'm in the console, however, I get the same gateway settings limited as if I was using a Tracker one. I have a different product for tracker ones, but created one separate for the monitor, of which it is the only device in the product group. Marking it for development doesn't change anything.
I imagine it's something basic, but I've danced around with it for hours now trying things. Thanks for the help.
You need to set the product configuration schema to Monitor One. You can do this with the schema tool.
2 Likes
Hey @sengsberg have you updated the schema to a Monitor One variant?
1 Like
While I didn't know the schema tool Rick linked existed, I did use the one baked in to the monitor-one firmware page. It gets hung on "Saving backup schema..." and stops moving forward. I can get another product to change the schema, but not the specific one I'm using. I swear I got it to save at one point in time, but I could be mistaken.
I'll see if creating a new product group doesn't help and will update if it fixes everything, thankfully I'm in a spot where it's not too cumbersome to switch things over.
Edit: Creating a new product hasn't fixed it. The schema update doesn't work on the new one "with no products associated" or the existing one, which has a device in it.
Edit (Again): After giving the system some time and coming back to it later, a schema upload worked on the remainder of the products I had created. It immediately created a new change for the Monitor one. Thanks both of you!
