ino file #5
Replies: 2 comments 7 replies
-
|
Well, there really isn't much to remove that isn't related to the ESP32 and its connection to the amp. The only physical components are really in the main loop where it watches for button presses and updates the LED display. Everything else is pretty much the process for remotely sending commands to the ESP32 via MQTT and having the ESP32 "translate" those codes into UART commands that the amp can understand and sending those commands over serial to the amp. I'm happy to try to help you out, but might need a little more info. I'd have to look into the code a little bit more, but I believe it could be used "as-is" without modification even if you aren't connecting physical controls. The only questionable one might be the SSD1306 display. But first, will the code compile 'as-is' without modification? If you are getting errors when trying to compile the existing .ino file, we need to look at that first, before we start making any changes. If you do get error(s) with the code as it is currently written, let me know what those errors are and we can start there. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, you are correct. The file compiled "as-is" and admittedly I should have tried that before asking for help. So the ESP32 is flashed and connected to the amp. Then I split the yaml package file into separate ones for sensors, switches, mqtt etc and uploaded to HA as part of "packages". I had to set the indentations for each of them and now I'm not getting any more errors from the YAML configuration checker. Now I need to educate myself on the mqtt topics, will report back how that goes. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, I'm back with an update. The last days were spent on working with the yaml files as I had to bring most of the code back to the main configuration.yaml file as splitting them would cause issues with indentations. In the end only the scripts, switches and inputs are separate from the main file. The automations you created and all buttons in the dashboard are working perfectly.
|
Beta Was this translation helpful? Give feedback.
-
|
I love the look of that clear enclosure! I have another amp sitting new in the box that I want to use to build DIY Amp v2.0. I know you don't have any need for local controls, but I'd like to integrate my touch display and after messing around a bit with FM receivers, possibly add one of those to the new version as well.... all integrated and powered by a single power cord. Don't know when I'll get around to it, but I'll try to post something here in the discussions if I add anything of interest. Yeah.. YAML can be a pain (especially with indentation) and it is almost always impossible to just copy/paste YAML from somewhere straight into Home Assistant. I'll have a video coming out soon on adding Home Assistant MQTT discovery to DIY projects so that all the entities are discovered and created automatically in Home Assistant without the need to manually enter all that YAML. I usually put a link to 'Buy Me a Coffee' at the bottom of my readme file for my repos, but I see I forgot to do that for this one! I greatly appreciate the offer and if you would like to say "thanks", you can do so here: https://www.buymeacoffee.com/resinchemtech Congrats again on your build. It looks really sharp! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I would be interested in the Amp 2.0 with the touch display, since most likely I will be getting another one of those, this time for the living room. I forgot to mention that mine came with the same fw version as yours did (36-30cb0ae0-6) so all of your code worked on mine too. Maybe Arylic doesn't update the fw on new iterations coming off the assembly line, who knows. |
Beta Was this translation helpful? Give feedback.
-
|
Well, right now I'm using an ILI9341 ( Amazon ) and I show how I use it in the last video of my amp series. This has a custom PCB and its own ESP32... which I'll likely have to keep if I stick with this display because of the number of GPIO pins required. But this would make my enclosure rather large. So I might go with a different display... or keep the display separate or figure out a way to attach it to the 'main' enclosure. The biggest thing for me is to reduce everything to a single power cord. Right now, the amp has a power cord (24V DC), the ILI9341 has a separate USB 5V connection, as does the current prototype of the FM receiver. In v2.0, I want to add a buck converter directly off the incoming 24V line and create a separate 5V bus for powering everything else except for the actual amp board. That way I also don't have to worry about the amp draw from the amp's onboard 5V pins (500mA max if I remember what Arylic told me)... as all other components will be powered via the buck converter, which will have at least a 3A capacity. I'll probably also make changes to the push buttons, as I find the only one I currently use is the MUTE. I'll probably add or alter buttons to connect to the ESP32 instead of the amp so that I can do things like scan through presets, etc. I'm just not sure yet, as I haven't really started on a new design... these are just things that I'd like to change based on about a year of using it. I haven't even taken it out of the box or fired it up to see if (hopefully) it has the same firmware version as well. I'm happy with the current version, but the amp went on a Black Friday sale for $62.99 and I just couldn't resist picking up a second one at that price! Again, not sure when I'll find time to really dig into it... but I'll post updates here at least when I do. And thanks again for the "coffee"! I really do appreciate it! |
Beta Was this translation helpful? Give feedback.
-
|
Hello good sir! I just got another Arylic Amp, this one will be used for the living room needs. I built it up with this "double decker" design this time around, where the Wemos D1 sits on the breakout board so it's easy to attach the wires into screw terminals and it looks good too. On the software front I replaced all "deskamp" entries with "arylicamp" for the new one in the Arduino IDE sketch, hoping that MQTT will pick it up nicely. I wanted to ask about the HA code for the configuration.yaml though. I don't want to make a mess so how do I proceed here, do I just copy and paste all the code I have so far and also replace "deskamp" with "arylicamp" and that's it? Thanks very much for your input!
|
Beta Was this translation helpful? Give feedback.
-
|
That's a nice design and it looks great! I still haven't started on my second version. I've decided I want to try to find an old 1940's era wood cabinet radio and replace the internals with my next amp build, based on a similar project one of my YouTube subscribers built. But I'm having some difficulty locating a radio that has all that I want (and at a reasonable price - I don't need the original radio to function). So my search goes on... As far as the Home Assistant side, you can give your entities any name you like. The important thing is that in the MQTT entity definitions, you assure any MQTT topics match what the amp is publishing or subscribing to. For example, if my YAML show a state topic of "stat/deskamp/source" but your amp is publishing on a topic of "stat/arylicamp/source", you obviously need to change the topics in the YAML to match. But as far as the "name:" property, those can be anything you want. If you want to change the input_number from desk_amp_volume to arylicamp_volume, you can certainly do so. But also remember to check the automations and scripts to not only update any MQTT topics, but also any entity names (like volume) that you might have changed. Hope that helps. Of course just let me know if you have any additional questions. |
Beta Was this translation helpful? Give feedback.
-
|
It does help a lot, thanks very much for your help yet again! I'll make sure that MQTT topics match what's in the yaml code and the automations for control and reading it's status. I have to say I'm very happy with how the first amp turned out and it's nicely integrated into my garage controls page in HA and it's easy to use and automate. So now it's turn for the one in living room, maybe I'll add some Z2M physical controls so wife can use it from the couch as well. What is the plan for the wood cabinet radio? Are you planning to integrate the dials and switches to control the amp's functions? Will it have the AM/FM frequencies dial selector? Please share an update on your YT channel once you have any updates, I'm very curious on how this will take shape. |
Beta Was this translation helpful? Give feedback.
-
Hello,
First of all thank you for the wonderful work you are doing with this, I appreciate it a lot! Say, would you be able to publish the INO file for the sketch, with only the elements that relate to the ESP32 board itself? It is the only thing I want to connect to the amp and I'm having trouble editing the existing file and having it validated. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions