Esperyd?s Raspberry PI project

Unifi with raspberry pi and wifi is just the setup that i have seen the issues with. In worst case it kills local network on the raspberry PI. Dont ask me why though since i have not found it out but there are a couple of bugs out there regarding it. Yes i have seen it at home and i run Unifi myself ;)

Neither less you said running grafana on Home assistant? You installed it as plugin or what? What do that have to do with the Raspberry PI image i built some years back?
 
I installed the grafana plugin to see if I could use it as a work around to the lock up.

I'm going to have a play install the watchmonudp and build from the ground up.
 
I will publish a video tomorrow regarding installing Watchmonudplistener on Home assistant if thats interesting. :) If so stay tuned for that. Though im not going into grafana on home assistant. Never used it there myself since raspberry pi have limited resources.
 
Are you running a pure HA install or installed HA on raspberry OS?
 
Then you just need to install Portainer and have access so you can logon to it and edit the configuration afterwards. Then also install local Mosquitto.

Then if you want grafana graphs you install influxdb and Grafana on top.

Beware of that if you dont run this install on SSD or enterprise SSD card you will deteriate it quickly. It is alot of data :) So the slower SD cards will be slow or wear out fast im afraid.
 
I'm in the process of trying to move my home automation stuff to a docker swarm cluster and will be using ssd
 
Then it will work fine. WatchmonUdplistener is already dockerized so you can just install it. Note that it need to run in network host mode
 
This is not regarding the ISO as such but this is the first of several new Raspberry PI videos coming :)

 
@daromer.

i am attempting to deploy your watchmonUDPlistener on Home assistant, using portainer. I have followed your steps exactly, and even freshly re-installed home assistant. but for the life of me, I can not get it to start. it just keeps crashing. I know zero about docker, so I have no clue where to start to look to diagnose this. but looking at the log of the container, I get this:

Code: 
standard_init_linux.go:219: exec user process caused: exec format error
 
What hardware? And have you chnaged the config so it can reach the mqtt server and the influxdb? Currently it does not work without Them.
 
its a fresh home assistant install on a NUC
I have the influxdb image installed from the addons section, aswell as grafanna
I do not as of yet have MQTT installed. I will do this now.

I have set the volumes as per the video, and I have set the network to host. basically, i press:
Diff: 
Deploy The Container

and then it just crashes instantly in the logs with the following error
Diff: 
standard_init_linux.go:219: exec user process caused: exec format error

I haven't yet setup MQTT, nor the index for batrium in influx. I just expected the container to load and run.... and then any information from it would essentially go nowhere, as there is nowhere yet for it to go...
 
Ok. Your nuc is running Intel CPU right?
Though if you are using it from docker hub i guess it should work. Note that if the problem would have been MQTT or influx you would have gotten some other log-error and i think this is related to the architechture. I have only tested it on Raspberry PI im afraid :(

If i get time later this weekend or early next week i could take a look at it if you let me check the machine? I need access if so and all that. Note that i dont have any Home assistant bare OS running here so i have not fiddled so much with it but i would like to solve it so others can use it like that.
 
hey mate, sure thing. im happy to let you have ssh access to it etc... i can just VLAN it off from my primary network, and forward the required ports etc... if you want, im happy to do it live via a zoom session or similar, so i can learn a bit more about it.

yes, the NUC is intel x86 based. and im using the image from docker hub.

let me know what works for you. i will also be online for the next few hours if you wanted to do it then. but if not, im easy. just let me know when works for you, and i can arrange access.
 
i have been playing around wiht it today, on another system all together. and i managed to get the container to start in another linux sustem but it also doesnt work. i have a ttached a picture of the terminal.

i dont know how to get logs or anything though.

1615103929583.png


to get to this point, i simply did a git pull, modified the influxdb IP in the config, renamed it to config.jason and then ran

Diff: 
sudo docker-compose up

aswell as

sudo ./run.sh

however, still no joy.
 
Check the logs. As i said it will not start unless it can connect to an MQTT and InfluxDB service. Run docker logs on it and you will see.
 
Ol. I will have to work out how to get the logs. I know nothing about docker. So am trying to learn it as I go.

When watching your home assistant video though, you deploy the container before editing the configuration file. And you get some errors in your pertained logs. However, I don't get the same errors.

So the influxdb and Mqtt services need to be running? I have confirmed that the influxdb is operational but perhaps the configuration is incorrect. I will attempt to get the logs and see what they say.
 
Docker logs <pid>
Its the id to the left of your image :)
 
UPDATE! For those running Homeassistant Core and NOT running Raspberry PI you need to do below.

First of all you need to use daromer/watchmonudplistener:amd64 instead of latest
1615147099605.png

1615147203184.png
1. Check the logs. Look for that its started as in below image
1615147233531.png
2. start a console if you need to change the config by pressing the 2.
To edit the config file you can in portainer start a console using /bin/sh.
1615147273027.png
In the console you can then to "cd config" and you are in the config folder. There aint many editors in this container so you need to understand how to work with "vi"

vi config.json
and edit ahead. Dont forget that there are special commands to even work with it. Currently i dont have any better way but il figure something out unless you guys have a tip!!

Note that this way of having arm and amd64 support isnt the best way but someting i quickly made up so feel free to tip me on a good way forward.
 
You must log in or register to reply here.
Back
Top