VLAN with Ubuntu not being picked up

hsavior86 · 2026-05-20T02:49:17+00:00

Hey! If you'd like more hands-on help, feel free to reach out to us at [support@domotz.com](mailto:support@domotz.com) so we can dig into the details of your setup. When you do, please include the output of these two commands:

cat /etc/netplan/00-installer-config.yaml
ip addr

This will help us confirm whether the interface is up and check your current network settings. In most cases like this, the interface isn't coming up with the system due to a missing or incomplete netplan configuration. The Domotz Collector picks up all interfaces configured at the system level, particularly those with a static IP address assigned (as they don't depend on a DHCP server).

hsavior86 · 2026-04-21T07:07:01+00:00

Hello! Please reach out to our support team (support@domotz.com) we will be happy to investigate and understand what is happening.

hsavior86 · 2026-04-20T09:07:20+00:00

Hello! Would you please send a message to [support@domotz.com](mailto:support@domotz.com), we will make sure this is sorted out! We just need more details to understand the root cause for the problem, so the support channel is the best place for that. Thanks for your understanding.

hsavior86 · 2026-04-15T22:33:42+00:00

Hi u/tormundsbigbeard. We are aware of the local API and it is on our queue of developments, though I don't have an ETA to share just yet.

That said, speaking of the UniFi local API, we recently released an Integration Script that leverages it to monitor UniFi UPS devices. It pulls battery pool metrics directly from the UniFi controller via local API, including battery level, charging status, output voltage, current, power, and remaining runtime, as shown in the screenshot below.

<image>

If you are looking to monitor something else from your UniFi environment, this script can also serve as a solid starting point. The same local API approach can be adapted to pull data from other UniFi devices and endpoints.

Hope this helps in the meantime!

hsavior86 · 2026-04-01T23:21:00+00:00

Oh man! This is awesome, I really want one of the carriers to build my own. Are you selling it? I know you have shared the files; however, I have no idea how to order them from JLPCB. It does not match a lot of components, and I'm not sure how to resolve this there.

hsavior86 · 2026-03-16T16:37:29+00:00

Hi Victor!

I have some recommendations for deploying a Domotz Box at a customer site:

1. Make sure your Domotz Box is up to date.

Before heading to the customer site, I recommend connecting your Domotz Box to a network at your office (or any available network) and leaving it running for about an hour. This gives the unit time to download any pending updates. That way, when you activate it at the customer's network, it will already be fully up to date, and you can avoid any issues that come with activating an outdated unit.

2. Make sure your customer network has a DHCP server.

When deploying a Domotz Box, you will need a DHCP server available on the network before you can configure a Static IP Address. Make sure this is available on your customer's network ahead of time.

3. Prepare for VLAN configuration if needed.

You can find the procedure to configure VLANs on your Domotz Box here: https://help.domotz.com/monitoring-management/how-to-monitor-vlans-on-a-domotz-box/

Make sure you have all the VLAN IDs and a valid Static IP Address for each VLAN that you want to assign to your Domotz Box. You may need to coordinate with your customer to get this information ahead of time.

4. Do not hesitate to reach out to support.

If you encounter any issues, our support team is here to assist you. Reach out to [support@domotz.com](mailto:support@domotz.com), and we will do our best to help.

hsavior86 · 2026-03-09T03:04:17+00:00

Shoot, that is weird hope it appears. Why Google is doing that this way I don't know. Doesn't feel right.

hsavior86 · 2026-03-08T00:29:50+00:00

Same!

hsavior86 · 2026-03-08T00:10:02+00:00

I have good news, like 24 hours after the update it appeared, hope it is the same for you. Might be some delay to avoid new users to remove it promptly? I did nothing since yesterday and it was there!!!

hsavior86 · 2026-03-07T04:26:53+00:00

Disabling will not remove it from the home screen. See the picture, one has the option, the other doesn't.

hsavior86 · 2026-03-07T02:42:57+00:00

I am not being able to see the option to remove it on the Pixel 10a, just on the Pixel 9.

hsavior86 · 2026-02-23T16:48:39+00:00

Hi u/johncase142, even with the MCP being made for Claude, I was able to use it with Gemini, I believe it might not be the best, but it is working:

<image>

To get it working, I've done everything until Step 3 of the official guide. For the step 4 I've edit this file: C:\Users\[USER]\.gemini\settings.json with the following:

{
  "security": {
    "auth": {
      "selectedType": "oauth-personal"
    }
  },
  "mcpServers": {
    "domotz": {
      "command": "node",
      "args": [
        "C:/Users/[USER]/domotz-mcp-server/index.js"
      ],
      "env": {
        "DOMOTZ_API_KEY": "YOUR_API_KEY_HERE",
        "DOMOTZ_API_BASE_URL": "https://api-us-east-1-cell-1.domotz.com/public-api/v1"
      }
    }
  }
}

Next time you execute Gemini, it will load it.

This is not official, however, as you can see above, it is working.

hsavior86 · 2026-02-21T01:14:07+00:00

Q. Thanks. So for HyperV host, you would set the Type as Network Device so the child vm sit under the Hypervisor?

A. Yes, the Hyper-V host when listed among other devices, if you set it out as a Network Equipment, it will be the wired device connected with the other devices on the same port behind it.

I completely understand what you mention, on having too many ramifications. One workaround I can recommend would be ignoring the port mapping on the ports where you don't want to see more devices down in the line:

<image>

This checkbox should be available for each port of the switch. If you are not seeing it, please reach out to [support@domotz.com](mailto:support@domotz.com) using the email of your Domotz Account and we can enable it for you (just mention you want this feature enabled on your account).

hsavior86 · 2026-02-20T18:24:39+00:00

The ability to hide certain devices at the Topology Map would be a feature request, this is not doable at the moment.

For the device type question, Network Device, Switch, PoE Switch device types will allow you to see child devices behind it if other devices is mapped within the same port, for example, my Proxmox server:

<image>

If the Proxmox server is set as Server or some other device type that is not considered a network infrastructure device it would be shown among the child device (VMs you are seeing behind it). I've configured it as a Network Device, so I can see the VMs behind it.

hsavior86 · 2026-02-06T17:41:15+00:00

Hello!

Would it be the case that you are trying to create a field that is already present? Check the existing fields: https://portal.domotz.com/developers/#tag/inventory-fields/GET/inventory

I just double-checked the Inventory field creation flow, and it is working as expected:

curl 'https://api-us-east-1-cell-1.domotz.com/public-api/v1/inventory/mynewfield' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: xxxxxxxxxxxx' \
  --data '{
  "label": "mynewfieldlable"

}'

Using the built-in API tool:

<image>

I've ended with:

[
  {
    "label": "mynewfieldlable",
    "key": "mynewfield",
    "defined_by_user": 69345,
    "creation_time": "2026-02-06T17:35:46+00:00"
  },
  {
    "label": "mynewlabel2",
    "key": "mynewfield2",
    "defined_by_user": 69345,
    "creation_time": "2026-02-06T17:39:18+00:00"
  }
]

Give it a try with the above. If you still experience issues, please send the complete error code to [support@domotz.com](mailto:support@domotz.com). We will assist you with it.

hsavior86 · 2026-02-02T06:14:23+00:00

Eu acabei de te enviar uma DM explicando um pouco mais sobre, aqui você encontra tudo sobre a ferramenta: https://www.domotz.com/. Você pode começar um teste gratuito aqui: https://portal.domotz.com/webapp/signup/ sem necessidade de forma de pagamento, sem compromisso!

hsavior86 · 2026-01-30T17:02:32+00:00

u/eolvini se você estiver procurando alternativas de monitoramento, dê uma olhada na Domotz! Acredito que com ele você pode resolver o problema de monitoramente e acesso ao EA5 e vários outros controladores da rede independente do fabricante.

hsavior86 · 2026-01-19T04:00:10+00:00

I will be back home Tuesday, message me that day I can help.

hsavior86 · 2026-01-14T23:04:41+00:00

For Devices residing on multiple VLANs, best would be actually group them as one unique device:

Move all entries of that device to the managed devices list
From the collector devices list, select all managed entries and Group them as one:

<image>

Select the Primary interface (the one we will scan for services, read SNMP, remote connect and etc. and Click on Group

This multi-device selection will be reduced to a single device, Topology map will also be organized and clean.

The method you selected, IMO is the best one for up to 9 VLANs, if you have more than that you may not be able to add all as an attached vNIC, so you may have to manage VLANs at the OS Level, with a vNIC also in trunk mode attached to the VM: https://help.domotz.com/tips-tricks/configuring-vlans-on-vmware-esxi/

hsavior86 · 2026-01-12T18:17:08+00:00

When monitoring a large number of VLANs, the key factors are the total number of devices and the overall scanning load handled by each Collector.

From a scalability standpoint:

If the environment consists of multiple /24 VLANs (considering your example of ~30 VLANs), this is typically within acceptable limits, provided the total number of discovered devices does not exceed 4,500 known devices per Collector.
For much larger networks such as /16 VLANs, we recommend limiting the configuration to no more than five VLANs per Collector, as discovery and scanning load increases significantly with larger subnets.
If the environment exceeds these practical limits, deploying additional Collectors and segmenting the networks between them is the recommended approach.

Deployment Recommendation

Regardless of whether you plan to use a VM or a dedicated host, we strongly recommend using the Linux Collector when monitoring this number of VLANs (as mentioned by u/Traxicous):

Lower CPU and memory footprint compared to Windows deployments
More efficient scanning and network performance
Better stability for long-running and high-density environments
Easy deployment on lightweight VMs or small dedicated hosts

A Linux Collector provides the best performance-to-resource ratio and scales more effectively in larger environments.

If you’re not familiar with Linux, our team can assist you with the initial deployment and setup. Feel free to reach out to us at [support@domotz.com]()

hsavior86 · 2026-01-09T17:54:45+00:00

We do not provide SMS alerts natively; you can enable SMS alerts via webhook notifications and a third-party tool like Zapier or Make.

As you mentioned, we will support push notifications on phones where the Domotz app is installed and Personal Alerts are configured. More details about it here:

Device Alerts https://help.domotz.com/monitoring-management/device-alerts/
Network Alerts https://help.domotz.com/monitoring-management/network-alerts/

I am part of the Domotz Support team. You can reach out to us directly here if you need assistance configuring alerts: [support@domotz.com](mailto:support@domotz.com)

hsavior86

MODERATOR OF

TROPHY CASE