I don't have time to read this now, but I love it already. I'd love to learn more details.
Van automation (Technical Discussion ONLY)
As I have hinted in other threads I have been working on an automation and control system for the van. The 3 phases of this project are:
1. Single pane of glass control of all devices (to include vehicle controls as well)
2. Sensor and data collection; local and internet
3. Automate various tasks based on sensor data
Step 1 involves turning most of your disparate 'dumb' devices into relays which can be controlled by the MCUs. Some things like the MaxFan and the CnC AC are pretty straight-forward. I haven't started on the Espar yet, but I imagine I'm in for a load of fun. As for vehicle controls, they're pretty well documented, and for the most part I will render the physical vehicle controls inoperable. This also includes relay controls for lighting, pnematics, and really anything else that needs a power switch.
Step 2 is gathering the values which will be needed to make the automation workflows. Throughout the van there will be sensors that I will install such as temp/pressure/contacts/lidar/ultrasonics, etc. In addtion, the CerboGX has a ton of data on the electrical system, and there are also various APIs I can pull from online, such as weather data. I also have OBD-II data feed and the vehicle status outputs from the High Specification Vehicle Interface Connector.
Step 3 is the fun part. Most of automation will revolve around lighting and environmental controls. I will be able to write logic using any of the sensor data collected to make these tasks as intelligent as possible. For example, the solar panels might only extend if the vehicle is off, distance sensors detect no obstructions, the weather report says winds are less than 50 mph, and the system SOC is less than 90%.
All of this is accomplished with various MCUs around the vehicle collecting sensor data and controlling relays. This data is all sent to an MQTT server where other MCUs can act on the information. This is a fairly common and well documented method of DIY automation. I'm using Teensy 4.1s because of the built-in ETH PHY along with the extremely beefy (for an MCU) hardware specs. For example my panel code is already using 200 Kb of RAM whereas your standard Arduino Uno only has 2 Kb of RAM max.
The panel is an 800x480 capacitive touchscreen and is essentially stateless like all the other MCUs. I'm making a few more at the moment for the inside and rear of the van. On powering up it pulls all the MQTT topics which describe relay status and other variables and is able to immediately represent the status of the system. This happens anytime the topic values are updated, whether it's another panel changing something or automation code.
As with everything in the van, the current status is "temporary working example". I'm not particularly fond of the GUI I came up with, but I did just refactor all the backend code to make additions to the system very easy. It's really down to building proto-boards at this point in order to bring everything up.
![Communication Device Tablet computer Gadget Mobile device Output device]()
![Circuit component Electrical wiring Hardware programmer Passive circuit component Electronic engineering]()
![Passive circuit component Circuit component Hardware programmer Electronic engineering Electrical wiring]()
![Passive circuit component Circuit component Automotive tire Bumper Electrical wiring]()
![Circuit component Hood Gesture Finger Hardware programmer]()
![Product Tablet computer Communication Device Gadget Output device]()
![Output device Communication Device Gadget Mobile device Portable communications device]()
BONUS pic of electrical system...
![Motor vehicle Vehicle Trunk Automotive design Mode of transport]()
1. Single pane of glass control of all devices (to include vehicle controls as well)
2. Sensor and data collection; local and internet
3. Automate various tasks based on sensor data
Step 1 involves turning most of your disparate 'dumb' devices into relays which can be controlled by the MCUs. Some things like the MaxFan and the CnC AC are pretty straight-forward. I haven't started on the Espar yet, but I imagine I'm in for a load of fun. As for vehicle controls, they're pretty well documented, and for the most part I will render the physical vehicle controls inoperable. This also includes relay controls for lighting, pnematics, and really anything else that needs a power switch.
Step 2 is gathering the values which will be needed to make the automation workflows. Throughout the van there will be sensors that I will install such as temp/pressure/contacts/lidar/ultrasonics, etc. In addtion, the CerboGX has a ton of data on the electrical system, and there are also various APIs I can pull from online, such as weather data. I also have OBD-II data feed and the vehicle status outputs from the High Specification Vehicle Interface Connector.
Step 3 is the fun part. Most of automation will revolve around lighting and environmental controls. I will be able to write logic using any of the sensor data collected to make these tasks as intelligent as possible. For example, the solar panels might only extend if the vehicle is off, distance sensors detect no obstructions, the weather report says winds are less than 50 mph, and the system SOC is less than 90%.
All of this is accomplished with various MCUs around the vehicle collecting sensor data and controlling relays. This data is all sent to an MQTT server where other MCUs can act on the information. This is a fairly common and well documented method of DIY automation. I'm using Teensy 4.1s because of the built-in ETH PHY along with the extremely beefy (for an MCU) hardware specs. For example my panel code is already using 200 Kb of RAM whereas your standard Arduino Uno only has 2 Kb of RAM max.
The panel is an 800x480 capacitive touchscreen and is essentially stateless like all the other MCUs. I'm making a few more at the moment for the inside and rear of the van. On powering up it pulls all the MQTT topics which describe relay status and other variables and is able to immediately represent the status of the system. This happens anytime the topic values are updated, whether it's another panel changing something or automation code.
As with everything in the van, the current status is "temporary working example". I'm not particularly fond of the GUI I came up with, but I did just refactor all the backend code to make additions to the system very easy. It's really down to building proto-boards at this point in order to bring everything up.
BONUS pic of electrical system...
1 - 20 of 84 Posts
That has to be the most impressive Victron setup I've ever seen! If you ever decide to sell your vehicle, I imagine Victron would love to take it off your hands for road shows 
You wouldn't happen to have any wiring diagrams (even sketches) would you?
I am of the same mindset (and similar plans) on automation. I don't want a wall of thermostats and controls, just give me automation based on battery condition, driving/parked, outside temp, tank levels etc. Like others have mentioned, my plan of attack is ESPHome + Home Assistant. FYI, MQTT control is still an option with HA, so you could integrate the work you've already done. There's also a Victron integration as well. ESPHome is especially nice for the climate controls.
Do you have any details you could share on the Cruise N Comfort AC wiring (and the Maxxfan)? I reached out to them for details and got nowhere (they won't even provide a manual for their wifi thermostat so I have no idea what capabilities it has). Undermount AC at least publishes their wiring diagrams, but they don't offer a true 24 volt system.
You wouldn't happen to have any wiring diagrams (even sketches) would you?I am of the same mindset (and similar plans) on automation. I don't want a wall of thermostats and controls, just give me automation based on battery condition, driving/parked, outside temp, tank levels etc. Like others have mentioned, my plan of attack is ESPHome + Home Assistant. FYI, MQTT control is still an option with HA, so you could integrate the work you've already done. There's also a Victron integration as well. ESPHome is especially nice for the climate controls.
Do you have any details you could share on the Cruise N Comfort AC wiring (and the Maxxfan)? I reached out to them for details and got nowhere (they won't even provide a manual for their wifi thermostat so I have no idea what capabilities it has). Undermount AC at least publishes their wiring diagrams, but they don't offer a true 24 volt system.
I don't have enough info to be actionable, but here is what little I think I know.
The bottom coil of the harness in this picture is the analog bus that can be used with the earlier generation controllers. In the current generation heaters, that branch is unused, just protect the ends from shorting and tuck it away.
In the diagram below, c2 is the analog bus pictured above. Mike mentioned that the red & yellow wires on the analog bus is what folks were using to accomplish the remote control of the heater.
My caveat is that tons of info was going back & forth during the multi-hour troubleshooting session with lots of off-topic tangents like this one. Please don't take this as gospel.
You are not alone.
It is fun to read the posts about automation. There are some very talented people here who have abilities that far exceed mine.
Each of us have a different idea about how to do a conversion. What is interesting is the range of ideas that appear.
I have no need for automating but that does not mean that it is not important to someone else. I do like my two dial microwave that automatically turns off after a set time.
Being a Luddite has its advantages. Just sold a 2017 Porsche and one of the reasons was all the automation. I prefer a car instead of a computer on wheels. I also prefer a conversion that is as simple as I can make it.
I also prefer a pocket watch instead of a cell phone. Not normal but we are all different.
1 - 20 of 84 Posts
