Hey guys newbie here,
I have a Nuvo p3100. Can i connect it with HA?
For now i am running HA on a mac using virtualboxVM with a VDI.
Do I need the cable , since i don’t have an rs232 port in my nuvo.
Hey guys newbie here,
I have a Nuvo p3100. Can i connect it with HA?
For now i am running HA on a mac using virtualboxVM with a VDI.
Do I need the cable , since i don’t have an rs232 port in my nuvo.
The p series Nuvo’s are a different product all together from what I understand. If there is no serial port, this integration will not work. If it’s network connected, you can explore that route. All we are doing here is emulating a person typing commands into a terminal. If your device has a similar command set that can be accessed via SSH, then you should explore that.
Thanks for the reply. @smilinjoe .
How to work on the network method.
If i enter the ip of my nuvo(each zone has one), i get
And if i go into diagnostics
how to proceed. Thanks in advance
Well I got it working. I used another method thats kind of a workaround. I took advantage of a plugin thats already written for nuvo serial port control in homebridge (HB). I will outline the steps I took and maybe it will help.
Requirements.
Steps
Pi running HB : Install Homebridge on Raspbian · homebridge/homebridge Wiki · GitHub
(There is other hardware HB can run on, google your preferred install)
OR
Portainer method : Tutorial: add Homebridge to Hass.io using Portainer
(no additional hardware is needed for this method)
Once you have homebridge running and can see the homebridge UI, then you are ready to move on. Scroll down to the number code on the HB front page under the qr code. You will need this later. Front page of HB looks like this:
Connect your nuvo amp with the cable to the device running homebridge.
In homebridge UI, click the menu at the top right and click plugins. In the “search for plugins to install” search bar type nuvo. Install the homebridge nuvo plugin. Once installed , click settings on the plugin and fill out the usb path to the nuvo amp and the number of zones.
Restart homebridge if prompted (from the top right menu, the power button looking thing)
Once restarted, click the top right menu and click accessories. You should see accessories created for each zone and each source (eg 6 zones with 6 sources = 36 accessories created). They will appear as lights. This is normal
If you click on one of these accesories you should be able to control on/off and volume. Depending on which accessory you clicked it will change the input (source). I verified this by standing by one of my keypads and clicking on the tiles to make sure they were turning on/off, switching sources, and adjusting volume.
IMPORTANT : At this point you want to go back to the plugin screen, on the nuvo plugin click the wrench and click bridge settings. Turn on the switch to initiate the nuvo-platform child bridge and restart homebridge again.
Once you have full control of your keypads through HB AND have the child bridge setup, time to go on.
Clicking on the newly installed integration you should see all 36 (or however many you have) entities created for each source and zone. They will still look like lights
You can optionally disable the sources you don’t use from the entity list and then go into customizations to change the icons to speakers for the ones you do.
SIde Notes:
Yes, the homebridge plugin adds the zones/sources as lights. So it appears in HA as a light as well. Customization basically fixes this. It may still say brightness when your adjusting volume but i dont care cuz its working Feel free to customize.
When turning on a zone the default volume is always somewhere around 50%. This is a safety feature of the HB plugin to not blast you with music when turning a zone on and protect your speakers. Very nice feature.
The homebridge-nuvo plugin works very well and credit goes here : GitHub - Willmac16/homebridge-nuvo: A Homebridge Plugin for Nuvo Whole House Audio Systems
He is very responsive and fixed an issue I raised when testing this method out.
I know this is a long read and also a departure of what this thread is working towards (native integration). But it is a working alternative I’ve been very happy with. Hope it helps someone.
Any luck on an integration for the p series?
I’ve created an integration for the Nuvo Grand Concerto and Essentia G models. It’s installable through HACS with the long term plan to get it merged into HA core. Details in the README GitHub - sprocket-9/hacs-nuvo-serial: Custom component to control a Nuvo Grand Concerto/Essentia G multi-zone amplifier via serial connection
For lower level config outside of HASS, the python library nuvo-serial · PyPI partly implements the serial control protocol for these amps.
Would be helpful to get some testers to kick the tyres and see how it runs for others
I have a Concerto not a Grand Concerto that I would be willing to test on. I have tried the HACS method but when configuring the add on it fails to connect after a long pause. The Essentia fails immediately so I am not sure if it is doing any type of model validation.
The older Concerto amp has a different protocol, so will not work with this integration, sorry
sprocket-9, I tried installing your new integration using a Grand Concerto. I was not able to get it to connect. When I added the integration and entered my serial port (/dev/ttyS0) I only got a spinning circle. I briefly looked through the code but couldn’t find where the baud rate is setup. I have some functionality working through Node Red, which I disabled when trying to add this, but am very interested in getting your integration up and running.
Is it still available in HACS, I don’t see it in the integrations?
As lleo has said, the Concerto model will not work due to protocol incompatibility.
There is model validation happening at connect time. For Essentia G it’s looking for a model number of “NV-E6G” in the response to the *VER command - does this match your Essentia’s model number?
Make sure your Node Red stuff is fully disabled and not trying to use the serial port, the integration needs exclusive use of the serial port and oddities will occur if something else is trying to read from it at the same time.
It won’t be a baud rate problem, this is set in the underlying library to 57600 for both models.
It could be serial port permissions:
ps -ef | grep -i homeassistant # find user owning the home assistant process, in my case it’s homeassistant
ls -l /dev/ttySO # find group name, in my case it’s dialout
groups homeassistant # check dialout group is in the list
sudo usermod -G dialout -a homeassistant # add homeassistant to dialout group
Reboot and see if it works now.
It is still available. If it’s not appearing for you, HACS might not be showing it as available if you’re running an older version of Home Assistant. The integration needs 2021.3.2 or newer.
Thanks for the response. It was a fresh install so it should be the latest version. It was a Virtualbox VM install. I saw lots of other integrations but I’ll check the setup again… new to this so could have quite easily missed something.
Looking forward to testing this
The model I have is a NV-I8DM.
OK that’s the older Concerto model which isn’t protocol compatible. I thought from your message you also had an Essentia G model, but doesn’t look it.
The two compatible models are:
Grand Concerto model NV-I8GM
Essentia G model NV-E6G
I am going to spin up a pi and check it out.
Thank you - I I have a Grand Concerto model NV-I8GM and, after some failed attempts to get this Nuvo integration setup manually as a custom component, came across your HACS install. I am running Home Assistant on an Odroid box and It worked beautifully first time. In addition to control by the cards I have tried some basic automation via Node Red and can now mute the Nuvo when the doorbell goes (a Shelly relay).
There is life yet in the old Nuvo system. Control via HA and the media player is much better than using the Music Port app. I have switched to Volumio as my main music source plus a Nuvo DAB tuner.
It worked first time for me. With the changes to HA this seems like the best course of action. I did have issues with unused zones and sources. They seem to populate even when you leave one blank. That could have been how I set it up (went with the defaults, then deleted the integration and started over). Editing zones and sources after install would be a nice feature as well.
Happy to hear it worked for you I have a doorbell Nuvo automation too, but I went a stage further than muting and use the Nuvo page service to play an mp3 of the doorbell through the zone speakers at the rear of the house where it is hard to hear the bell. Also have one to mute/unmute Nuvo zones when receiving/ending calls.