Comments (5)
Here is a log:
[May 09 06:54:12:695917] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:696077] pilight-daemon: DEBUG: protocol dht22
[May 09 06:54:12:696120] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:696299] pilight-daemon: DEBUG: protocol dht11
[May 09 06:54:12:696334] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:696375] pilight-daemon: DEBUG: protocol bmp180
[May 09 06:54:12:696406] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:696452] pilight-daemon: DEBUG: protocol generic_webcam
[May 09 06:54:12:696487] pilight-daemon: DEBUG: protocol generic_weather
[May 09 06:54:12:696527] pilight-daemon: DEBUG: protocol generic_switch
[May 09 06:54:12:696562] pilight-daemon: DEBUG: protocol generic_screen
[May 09 06:54:12:696596] pilight-daemon: DEBUG: protocol generic_label
[May 09 06:54:12:696627] pilight-daemon: DEBUG: protocol generic_dimmer
[May 09 06:54:12:696667] pilight-daemon: DEBUG: protocol xbmc
[May 09 06:54:12:696699] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:696732] pilight-daemon: DEBUG: protocol wunderground
[May 09 06:54:12:696759] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:696805] pilight-daemon: DEBUG: protocol sunriseset
[May 09 06:54:12:696853] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:696889] pilight-daemon: DEBUG: protocol program
[May 09 06:54:12:696941] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:696981] pilight-daemon: DEBUG: protocol openweathermap
[May 09 06:54:12:697008] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:697055] pilight-daemon: DEBUG: protocol lirc
[May 09 06:54:12:697084] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:697115] pilight-daemon: DEBUG: protocol datetime
[May 09 06:54:12:697140] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:697167] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:697204] pilight-daemon: DEBUG: protocol cpu_temp
[May 09 06:54:12:697230] pilight-daemon: DEBUG: stopped protocol threads
[May 09 06:54:12:697263] pilight-daemon: DEBUG: protocol x10
[May 09 06:54:12:697298] pilight-daemon: DEBUG: protocol tfa30
[May 09 06:54:12:697323] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:697360] pilight-daemon: DEBUG: protocol tfa
[May 09 06:54:12:697385] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:697430] pilight-daemon: DEBUG: protocol teknihall
[May 09 06:54:12:697456] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:697495] pilight-daemon: DEBUG: protocol techlico_switch
[May 09 06:54:12:697529] pilight-daemon: DEBUG: protocol tcm
[May 09 06:54:12:697556] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:697595] pilight-daemon: DEBUG: protocol silvercrest
[May 09 06:54:12:697628] pilight-daemon: DEBUG: protocol selectremote
[May 09 06:54:12:697661] pilight-daemon: DEBUG: protocol secudo_smoke_sensor
[May 09 06:54:12:697691] pilight-daemon: DEBUG: protocol sc2262
[May 09 06:54:12:697722] pilight-daemon: DEBUG: protocol rsl366
[May 09 06:54:12:697757] pilight-daemon: DEBUG: protocol rc101
[May 09 06:54:12:697793] pilight-daemon: DEBUG: protocol quigg_screen
[May 09 06:54:12:697830] pilight-daemon: DEBUG: protocol quigg_gt9000
[May 09 06:54:12:697869] pilight-daemon: DEBUG: protocol quigg_gt7000
[May 09 06:54:12:697907] pilight-daemon: DEBUG: protocol quigg_gt1000
[May 09 06:54:12:697945] pilight-daemon: DEBUG: protocol pollin
[May 09 06:54:12:697979] pilight-daemon: DEBUG: protocol ninjablocks_weather
[May 09 06:54:12:698005] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:698042] pilight-daemon: DEBUG: protocol mumbi
[May 09 06:54:12:698076] pilight-daemon: DEBUG: protocol logilink_switch
[May 09 06:54:12:698110] pilight-daemon: DEBUG: protocol impuls
[May 09 06:54:12:698144] pilight-daemon: DEBUG: protocol heitech
[May 09 06:54:12:698178] pilight-daemon: DEBUG: protocol ev1527
[May 09 06:54:12:698208] pilight-daemon: DEBUG: protocol eurodomest_switch
[May 09 06:54:12:698244] pilight-daemon: DEBUG: protocol elro_800_switch
[May 09 06:54:12:698280] pilight-daemon: DEBUG: protocol elro_800_contact
[May 09 06:54:12:698312] pilight-daemon: DEBUG: protocol elro_400_switch
[May 09 06:54:12:698350] pilight-daemon: DEBUG: protocol elro_300_switch
[May 09 06:54:12:698386] pilight-daemon: DEBUG: protocol ehome
[May 09 06:54:12:698419] pilight-daemon: DEBUG: protocol daycom
[May 09 06:54:12:698455] pilight-daemon: DEBUG: protocol conrad_rsl_switch
[May 09 06:54:12:698490] pilight-daemon: DEBUG: protocol conrad_rsl_contact
[May 09 06:54:12:698520] pilight-daemon: DEBUG: protocol cleverwatts
[May 09 06:54:12:698557] pilight-daemon: DEBUG: protocol clarus_switch
[May 09 06:54:12:698591] pilight-daemon: DEBUG: protocol beamish_switch
[May 09 06:54:12:698626] pilight-daemon: DEBUG: protocol auriol
[May 09 06:54:12:698651] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:698687] pilight-daemon: DEBUG: protocol arctech_switch_old
[May 09 06:54:12:698725] pilight-daemon: DEBUG: protocol arctech_switch
[May 09 06:54:12:698765] pilight-daemon: DEBUG: protocol arctech_screen_old
[May 09 06:54:12:698801] pilight-daemon: DEBUG: protocol arctech_screen
[May 09 06:54:12:698837] pilight-daemon: DEBUG: protocol arctech_motion
[May 09 06:54:12:698869] pilight-daemon: DEBUG: protocol arctech_dusk
[May 09 06:54:12:698899] pilight-daemon: DEBUG: protocol arctech_dimmer
[May 09 06:54:12:698940] pilight-daemon: DEBUG: protocol arctech_contact
[May 09 06:54:12:698982] pilight-daemon: DEBUG: protocol alecto_wx500
[May 09 06:54:12:699009] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:699060] pilight-daemon: DEBUG: protocol alecto_wsd17
[May 09 06:54:12:699087] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:699119] pilight-daemon: DEBUG: protocol alecto_ws1700
[May 09 06:54:12:699145] pilight-daemon: DEBUG: ran garbage collector
[May 09 06:54:12:699185] pilight-daemon: DEBUG: protocol process
[May 09 06:54:12:699213] pilight-daemon: DEBUG: garbage collected protocol library
[May 09 06:54:12:699879] pilight-daemon: DEBUG: stopping socket thread
[May 09 06:54:12:700118] pilight-daemon: DEBUG: stopped thread socket, 3 threads running
[May 09 06:54:12:710393] pilight-daemon: DEBUG: stopping ssdp thread
[May 09 06:54:12:710646] pilight-daemon: DEBUG: stopped thread ssdp, 2 threads running
[May 09 06:54:12:720997] pilight-daemon: DEBUG: stopping sender thread
[May 09 06:54:12:721216] pilight-daemon: DEBUG: stopped thread sender, 1 thread running
[May 09 06:54:12:731547] pilight-daemon: DEBUG: stopping broadcaster thread
[May 09 06:54:12:731771] pilight-daemon: DEBUG: stopped thread broadcaster, 0 threads running
[May 09 06:54:12:742052] pilight-daemon: DEBUG: garbage collected threads library
[May 09 06:54:12:742499] pilight-daemon: DEBUG: garbage collected dso library
DEBUG: garbage collected log library
[May 09 06:54:12:750055] pilight-daemon: DEBUG: garbage collected lua library
from home-assistant-addons.
same place as you. some help?
from home-assistant-addons.
I couldn’t get this specific add on working but I got pilight to run if your willing to mess around with docker containers and images. I installed Portainer from the community addons. Then I went to images and build new image and named it something like pilight:8.0.2. I think that new versions of pilight may have broken things so I installed 8.0.2.
Add this to the dockerfile section:
FROM resin/rpi-raspbian:stretch
RUN apt-key adv --keyserver keyserver.ubuntu.com --recv-keys \
CC28DD82EF4C718C \
&& echo "deb http://apt.pilight.org/ stable main" > /etc/apt/sources.list.d/pilight.list \
&& apt-get update \
&& apt-get install -y \
pilight=8.0.2 \
pilight-webgui=8.0 \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*
CMD ["/usr/local/sbin/pilight-daemon", "-F"]
Then build it, you might need to do this twice to get it working. Then make a new container with this image. Open port 5000 and 5001. Add /dev/mem as a device and add SYS_RAWIO permissions. Then deploy the container and it should work in the background. To edit the config, go into the console, write apt-get update
, apt-get install nano
, nano /etc/pilight/config.json
, then exit the console. Now you can commit the changes by creating an image with the same name as the image you created then "Duplicate/Edit" container and re-deploy.
from home-assistant-addons.
Inspired by your comment @Priva28 , i made my own addon. https://github.com/m2hofi94/my-hassio-addons/tree/master/pilight. Since hass.io allows for images to be built locally, I don't think it is necessary to jump through the loops with portainer as you described. (https://developers.home-assistant.io/docs/en/hassio_addon_publishing.html#locally-build-containers)
You can just copy my repo (or this) to your local addons folder and modify everything to your hearts content.
Just wanted to leave that here, if anyone else needs help.
from home-assistant-addons.
I can get the addon to work. But I can’t access it from home assistant. Any suggestions?
from home-assistant-addons.
Related Issues (20)
- Conflict with new HA BlueTooth Integration (since 2022.08.0) HOT 3
- Flicd not working with secondary bluetooth device HOT 2
- Does this work over esphome BT proxy? HOT 1
- Cannot add repository HOT 2
- [feature request] support the new bluetooth proxy feature in home assistant HOT 3
- flicd: /run.sh: line 8: /usr/bin/flicd: No such file or directory HOT 5
- [zabbix-agent2] missing postgresql/mongodb plugins HOT 3
- keepalived working fine on vm install but not on raspberry pi 4 - maybe missing #!/bin/bash on top on sh file? HOT 3
- [zabbix-agent2] Server IP configuration being used for both passive and active checks HOT 1
- [Zabbix Agent] using TLS PSK HOT 7
- How can I use bluetooth proxy with flicd? HOT 1
- Help to get it working HOT 1
- [zabbix2] Feature request: allow docker_api access HOT 7
- [flicd] Installing it breaks existing bluetooth integrations HOT 1
- Installing flicd for the first time HOT 3
- bluetooth proxy HOT 1
- [feature request] add the option for userParameter in configuration
- /run.sh: line 8: /usr/bin/flicd: No such file or directory HOT 1
- Issue with Home Assistant Zabbix_Agent2 on fresh install of Home Assistant OS 12.3 HOT 7
- Running flicd standalone
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from home-assistant-addons.