I find the Victron App cumbersome when Im driving my RV. So, I created this simple MQTT iOS fully local app. One click on this iPhone app/icon and everything I need to see while im driving is right there. No clicking around, no logging into online systems, no clicking “open Portal”, just the immediate info I need. MQTT info populates very quickly.
Its exactly the same info and layout as their app, but when it opens all the data is right there. And it stays there.
Victron could do exactly the same thing with a “Use Local LAN access only” toggle switch if they so chose…
I also use the kiosk app, the issue I have it we have multiple PV systems on our mesh. I have to go in and change the host name of the VenusOS devices in order to be able to reach them using the machine URL vice the IP. Sure wish they would make that easier to do. All of these systems are DC only systems so they are simple. I am starting to get request from EOC’s and Fire departments that want a PV powered microwave link and perhaps some radios solar backed. I generally run the dc buss at 24vdc any equipment that needs 12vdc I put a buck converter on each 12v device. Be nice to be able to have say 4 pv sites on a large screen at a NOC. For these sites the MPPT 75/15 works great. I will have to look into the MQTT thing.
I’ll see if I can figure out the “external” invite on TestFlight this AM. I got internal testing working (me) and went to battle with it for a couple hours last night before finally giving up and turning to good bourbon for relief. For all their ease of use in everything else, Apple does NOT make app distribution easy. It’s a Royal PITA. Even my AI had trouble…
And that is one of the challenges, at least you disclosed it. Technically that contravenes our policy of AI-generated content, but that is now impractical to try police.
It is now a wave of people “writing” applications where it is really all done by a coding agent and very little understanding of what actually has been coded, any bugs, security features etc.
It is a fine line that needs to be carefully negotiated and why we will continue to be very selective on AI use.
In the hands of a capable dev team, it is a powerful tool, in the hands of someone where the ability does not go much further than the prompt it can end badly.
That said, modern coding agents tend to produce better code than a beginner/diy dev.
We just have not encouraged it here.
Members should also exercise good judgement when trying anyone’s code, the forum was never intended as a distribution platform for apps, but as a place to share and foster ideas.
Finding a balance isn’t easy.
When these topics appear we tend to ask members to publish their code on github, which allows anyone, outside this forum, to go there and collaborate, log issues, or simply fork the code for their own use. It is the best place for it.
And we thank you for making your platform open.and stating clearly where you stand in all this. FWIW, I’m not a beginner by any stretch. I was coding in 8088 assembler in the 1980’s - yup I’ve felt pain like very few have.
I also have nothing to hide or apologize for. The new coding tools mostly generate solid code. MQTT is straightforward and your implementation is rock solid. It’s one reason I’m a huge supporter.
I will absolutely push this to GitHub. Anyone wanting it can grab it from there and do with it as you please you can also find my email there and ask to be invited to my TestFlight to use the app as it sits.
code is here as is my email for a testflight invite
pls respect Nick and Victron’s stance on this and post any issues or questions about this on my github under Issues or discussions
