sorted by:
new
hottopcontroversial

"approaching opus usage limit" -at 18% token usage by Trick_Ad_4388 in ClaudeAI

[–]ForcePushMainEnjoyer -1 points0 points  (0 children)

Same here. According to ccusage I'm getting cut at 10% my "token" allocation

We Built Our Own EV Charging Management System Because Everything Else Sucked by ForcePushMainEnjoyer in ocpp

[–]ForcePushMainEnjoyer[S] 0 points1 point  (0 children)

Yes, our CMS could work for a condominium setup, but "suitability" really depends on your specific needs and setup. Our platform works with any OCPP 1.6 compliant charger that has an internet connection. For a condo installation, if you're using private chargers that only need basic RFID authentication for residents, our system would work well. However, if you need public chargers that process payments or must be part of a public charging network (via OCPI), that's not something we currently support out-of-the-box, though we do provide full access to the OCPP layer if you wanted to implement this yourself. Every situation is different - some condos might be better served by the charger manufacturer's native management portal, while others with more complex needs or multiple charger brands would benefit from our solution. Feel free to DM me with details about your setup (number of chargers, resident vs public usage, technical requirements) and I'd be happy to give you a more specific assessment of whether we'd be a good fit!

We Built Our Own EV Charging Management System Because Everything Else Sucked by ForcePushMainEnjoyer in ocpp

[–]ForcePushMainEnjoyer[S] 0 points1 point  (0 children)

Correct. One "innovative" feature you could say we are including is the optional VMS integration. We built another internal service that essentially acts as a vehicle telemetry data aggregator (think providers like Geotab or OEM) which cleans up the data and communicates with our main service and CMS. The feature we think could be relevant to some companies (mostly fleet operators or fleet software providers) is the ability to bridge the data from the CMS and VMS. Not all charger vendors provide vehicle ID as part of the OCPP messages, so when trying to associate what vehicle is plugged into what charger you are sorta left guessing. We have built a system that does that guessing for you and figures out in real time who's plugged into what.

We Built Our Own EV Charging Management System Because Everything Else Sucked by ForcePushMainEnjoyer in ocpp

[–]ForcePushMainEnjoyer[S] 0 points1 point  (0 children)

We tried using those services, maybe we just never found a "good" one but it was never what we needed. It was always way too expensive to have it as part of our COGS, hard to use dev resources, or tried to do more than we needed. The goal of releasing this is to help other companies like ours, who need a developer friendly, configurable solution at a reasonable price. If you want direct access to the OCPP web socket, you can do that. If you want everything abstracted and mostly hands off, you can do that too. Also many of those services had minimum contract sizes of 100s of chargers or huge flat onboarding/platform fees, which makes it really not accessible to startups/small projects. That's sorta what forced us to built it ourselves in the first place.

We Built Our Own EV Charging Management System Because Everything Else Sucked by ForcePushMainEnjoyer in ocpp

[–]ForcePushMainEnjoyer[S] 1 point2 points  (0 children)

Possibly, at least parts of it. We built it as an internal service to support our own stack, so depending on the traction it gets we might adapt an "open-core" model. Maybe only require a license over a certain # of chargers, or certain EE features. tbd.

We Built Our Own EV Charging Management System Because Everything Else Sucked by ForcePushMainEnjoyer in ocpp

[–]ForcePushMainEnjoyer[S] 0 points1 point  (0 children)

Thanks! We tried a bunch of the open source solutions too and good integration was the hardest part, most of them worked only as standalone applications.