Community

We are trying to autofill the Route Name into the stringValue whenever a certain document is created but cannot figure out how to do this. ``` { "dispatchJobId": 9002955259, "documentTypeUuid": "79b45b3b-6e73-40e1-ac72-3b7692475d4c", "fields": [ { "label": "Order #", "valueType": "ValueType_String", "stringValue": }, { "label": "Do you accept this load?", "valueType": "ValueType_MultipleChoice", "multipleChoiceValueTypeMetadata": { "multipleChoiceOptionLabels": [ { "label": "Yes" }, { "label": "No" } ] } } ], "conditionalFieldSections": null } ```

Hi,i want know if the eld hardware device is actually connected to the vehicle.

Afternoon. My signature capture service stopped working, when the UK moved to BST, as the times didn't match the 'created date' of the Proof of Deliveries. Is the timezone for the Proof of Delivery creation in UTC? Thanks in advance!

I have a Samsara ELD customer requesting to connect to the ECM remotely to troubleshoot issues on the road without having to connect from a laptop (which they do with a NEXIQ Box currently). In particular, they want to clear codes, reflash ecms,or regening the engines. Is this possible with Samsara or any other 3rd party products?

Referring to this endpoint: https://developers.samsara.com/reference/gettrailerstatssnapshot `reeferAlarms` in response body: alarm severity. Is this "1" by default? Will this update back to "1" once a "2 check" or "3 severe" alarm is cleared? Or is there some other way to know that an alarm is cleared?

Does Samsara offer an API attribute that gives us the odometer (GPS odometer) and a true odometer (Odometer + any odometer offsets due to equipment change/repair)? In some cases, it is called the odometer offset. Thanks,

When using the event feed, we only get a short blurb of the change made. We don't get the full event data from the feed so we can keep a 100% accurate internal database of our camera events. We tried using the "List all safety events" end point but it doesn't use the same timestamps as the feed. When adjusting them by 1 minute we get 0 results for something that shows up on the feed. This would be so much cleaner if we could use the unique ID for the "List all safety events" end point rather than a timestamp range. That way we could get a feed item, and then query the unique event ID to grab the current details.

I could post a picture, but there is a section where we can drill down on a driver and see their speeding events against posted speed limits. There is an event table and a way to retrieve all of these as they happen would be very beneficial. We can grab the current speed of a vehicle, but the speeding events are not available anywhere in the safety event feeds.

When called (v1/sensors/list) Get All Sensors how are we supposed to distinguish cargo sensors from temperature sensors? Right now we just have to run every sensor ID through the "Get Cargo Status" and "Get Temperature" calls to see if we get a response or not. This seems very inefficient

Hey all, I was able to filter get messages and sort it into a python dictionary that recorded all messages driver's receive or send. I know it might not be perfect but ideally we want to track how long drivers wait until anyone from our company responds to them. My code was going to be something like this for x in dictionary: if x[id] == driver j=0 if dictionary[x][id] == dictionary[x+1][id] //check if next message is same driver j++ elseif dictionary[x][id] != dictionary[x+1][id] //next message was dispatcher array[x+j][dispatcher] =array[x+j][dispatcher]+ [x+j][time] - [x][time] //shove it into an array of dispatchers to sum time that we average later else //pretty sure i'll fault if the next message doesnt exist pass I know there are a lot of problems. For example, if a driver and dispatcher had a conversation and a driver ended it with statement that doesn't require a response like "Thank You" Also some drivers ask questions in the middle of the night. My idea was to take the unix time and mod it by 86400 seconds in a day to get the hour. Then filter and ignore messages during specific times. Another possibility I thought of was if the disparity between response time was too high; just ignore it. If anyone got bright ideas that can help me out would be greatly appreciated. It might also be impossible to get any accurate or useful data but I thought it might be worth a shot.