Replies: 8 comments 2 replies
-
|
Here is the output of the "complete log of this run" 0 info it worked if it ends with ok |
Beta Was this translation helpful? Give feedback.
-
|
check and see if z2m is already running, |
Beta Was this translation helpful? Give feedback.
-
|
That would the the IP of the LXC where z2m is installed? If I use that IP I get the following message: Firefox can’t establish a connection to the server at 192.168.1.252:9442. |
Beta Was this translation helpful? Give feedback.
-
|
It has started before, because it populated a |
Beta Was this translation helpful? Give feedback.
-
|
Well that's good to know, but I'm not sure what might be wrong currently or what I can do to trouble shoot. |
Beta Was this translation helpful? Give feedback.
-
That's what I don't understand |
Beta Was this translation helpful? Give feedback.
-
|
Yeah it's pretty confusing to me too. My girlfriend just came over, so I'll try to trouble shoot the network tomorrow. If I can get things to show up reliably then I'll see if I still have a problem |
Beta Was this translation helpful? Give feedback.
-
|
Ok well I'm still trying to learn more about the issue, but I figured I'd shoot you a quick update. After I messaged you yesterday my network started failing hard. Like, I could access the internet from some machines but not others. I couldn't get to my unifi controller sometimes, etc. I was able to get into my unifi controller for long enough and I tried to revert as many things as possible to default and/or less restrictive settings, but tbh I think the problem had to do with my adguard DNS server. I'm not sure how or why, because I don't think I touched anything with either Adguard or the DNS server, but once I turned off DNS things started working again (mostly). Actually, now that I'm thinking about it, if I was using the Adguard LXC as my DNS and if the router was having issues seeing the LXC as online, I would get no return for my DNS lookups. So that would explain why my entire network went haywire last night and why the general network issues resolved themselves after I moved my router DNS lookup back to 8.8.8.8. So I at least got back to stable, but I'm still having an issue with Containers that are definitely, 100% running on Proxmox not appearing on Unifi. For example, I can log see MariaDB running on Proxmox AND log into Adminer, while it is showing as disconnected on Unifi. This is consistently true of any/all cases where a Proxmox VM/LXC is connected and running, but not showing up on my router. I can ALWAYS access the VM/LXC by typing in the correct IP:Port. So these items are connected on my network and working, the router just can't see them. I did find another person who seems to have experienced the exact same issue. His solution was to eventually factory reset his network. His assumption was that something probably got messed up with the migration and IP changes and re-use. I'm not exactly sure how something like that would happen, but since both of our issues occurred right after a migration from a pi to proxmox it does seem very likely that the issue somehow stems from the migration. Since I've tried resetting everything else and I'm still having issues, it sounds like that is probably going to be the best solution for me. I'll try that out this afternoon and let you know how it goes. |
Beta Was this translation helpful? Give feedback.
-
|
OK so... I factory reset my (Unifi) routher, (Ubiquiti) switch and (Unifi) AP. I also created a brand new Unifi Controller on Proxmox, so I was essentially starting everything completely fresh. I got all of that set up without any issues. I was running JUST the Unifi Controller on Proxmox and the router had no issues. I figured everything was looking good, so I launched mariadb on Proxmox (at this point I had only launched the Unifi Controller and MariaDB, nothing else). The instant I launched MariaDB my Unifi Controller lost visibility of Proxmox, and MariaDB never showed up on my Unifi Controller. However, if I log into the Router at 192.168.1.1 I do see a DHCP Lease was assigned to the MariaDB LXC. And if I go to that IP/adminer I can access the adminer interface. I also see mariadb recognized on the MAC Table when I log into my Ubiquiti switch and it shows a hostname of "mariadb", but it does NOT have an IP Address listed in my switch. At this point I feel fairly certain that the issue has something to do with them all being on the same machine. But it could be an issue with the controller, the router, the switch, or how I have Proxmox setup. I do think it's interesting that this seemed to work perfectly fine when I had the Unifi Controller on a raspberry pi and only started becoming an issue when I moved the Unifi Controller over to Proxmox. Like the fact that the Controller is on the same machine as the other LXCs is causing the issue. This is supported by the fact that the Unifi Controller was working fine when it was the only LXC running, but ran into issues the instant I had 2 LXCs running. I guess the only remaining thing to "factory reset" would be the Proxmox machine. At this point I will probably try that since it really won't be much more work after everything else. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @gdneye , for what it's worth I'm also running Unifi hardware. I've been having major problems, but found that adjusting the MTU seems to "magically" fix the issues I'm facing. I set my MTU to 1200 on all machines, and they immediately start to appear on the unifi console, can be reached via hostname/IP, etc. Here's the command I run on proxmox: And here's the command I run on HAOS: You can see your interfaces with I hope this is useful. |
Beta Was this translation helpful? Give feedback.
-
Hey man...
I really appreciate that you've put together these scripts. So far Ive been able to use them to set up a VM for HAOS and LXC containers for Unifi, Adguard and Dashy.
I've been trying to get mqtt and zigbee2mqtt set up and I've been losing my mind for the last 3 days trying to figure out what I'm doing wrong.
My setup is a sonoff 3.0 that I successfully flashed according to these instructions:
https://www.youtube.com/watch?v=4jqQCxjlRDU
And proxmox is running on a Deskmini with 32gb ram, a 250gb m2 ssd and a 5700g with the containers I described. Nothing else is running on that machine. My comprehension level of this stuff is probably pretty low compared to most ppl who use HA. I'm not a programmer, but I really enjoy messing around with stuff and I have done a lot of programming adjacent things previously. I can usually sort of brute force my way through not understanding things with Google, but I'm not coming back with very many results combining Proxmox and MQTT. At least not very many helpful ones.
Also, after failing for a while I briefly set up ZHA just to verify that it wasn't an issue with my Sonoff Dongle and to see if I could get the passthrough working (even though the passthrough is different for a VM). I was able to get ZHA set up in no time and add a few devices, so I'm confident my Sonoff Dongle is working properly.
I've followed the instructions you give. I have removed the LXC's and reinstalled at least a dozen times and trying to tweak various settings, so I don't believe it could be a faulty install either and at this point I am very familiar with the instructions, so I don't think I missed any steps.
I'll try to be specific with any question. If you're willing to help any I greatly appreciate it.
I also think it is worth noting that even though the MQTT broker and Z2M containers are both running, neither of them is showing up on my router (although they have both shown up at least once in the past, because they do exist in my router, they just aren't online).
Zigbee2MQTT:info 2022-04-07 23:57:20: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2022-04-07.23-57-20' filename: log.txt
Zigbee2MQTT:info 2022-04-07 23:57:20: Starting Zigbee2MQTT version 1.25.0 (commit #6f1460e4)
Zigbee2MQTT:info 2022-04-07 23:57:20: Starting zigbee-herdsman (0.14.20)
Zigbee2MQTT:error 2022-04-07 23:57:20: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-04-07 23:57:20: Failed to start zigbee
Zigbee2MQTT:error 2022-04-07 23:57:20: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-04-07 23:57:20: Exiting...
Zigbee2MQTT:error 2022-04-07 23:57:20: Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
at SerialPort. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:146:28)
at SerialPort._error (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at /opt/zigbee2mqtt/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.25.0 start:
node index.jsnpm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.25.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-04-07T23_57_20_890Z-debug.log
And this is my config file. I've changed the pw bc that's what I've seen others do, but I'm certain the username and pw are the same as what I put into the MQTT LXC.
GNU nano 5.4 /opt/zigbee2mqtt/data/configuration.yaml
frontend:
port: 9442
homeassistant: true
permit_join: false
mqtt:
base_topic: zigbee2mqtt
server: mqtt://192.168.1.203:1883
user: mqqt_user
password: 123456
keepalive: 60
reject_unauthorized: true
version: 4
serial:
port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_30580edc0945ec118d9494fd6f14af06-if00-port0
advanced:
pan_id: 4546
network_key:
- 128
- 167
- 100
- 14
- 142
- 111
- 99
- 184
- 209
- 54
- 7
- 154
- 248
- 103
- 116
- 58
channel: 20
homeassistant_legacy_entity_attributes: false
legacy_api: false
legacy_availability_payload: false
device_options:
legacy: false
Any help would be appreciated. I'm fairly certain I've followed your instructions exactly, so I don't know where to go from here.
Thanks,
Tim
Beta Was this translation helpful? Give feedback.
All reactions