jofri

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by jofri

  1. Hi again, Who do you mapp a usb device and get a static name on it? I got lots of errors when I add the parameters: /dev/ttyACM0 and also use this link in the applications. Dec 4 18:27:43 Teknikum kernel: domoticz[41962]: segfault at 0 ip 00002b5b6f669345 sp 00002b5b72683680 error 4 in ld-musl-x86_64.so.1[2b5b6f64c000+89000] Dec 4 18:27:45 Teknikum kernel: domoticz[42018]: segfault at 0 ip 00002b1049ef5345 sp 00002b104cf54680 error 4 in ld-musl-x86_64.so.1[2b1049ed8000+89000] Dec 4 18:27:47 Teknikum kernel: domoticz[42065]: segfault at 0 ip 00002ae5a29a2345 sp 00002ae5a59bc680 error 4 Dec 4 18:27:47 Teknikum kernel: domoticz[42068]: segfault at 0 ip 00002ae5a29a2345 sp 00002ae5a5a01680 error 4 Dec 4 18:27:47 Teknikum kernel: in ld-musl-x86_64.so.1[2ae5a2985000+89000] Dec 4 18:27:47 Teknikum kernel: in ld-musl-x86_64.so.1[2ae5a2985000+89000] Dec 4 18:27:49 Teknikum kernel: domoticz[42116]: segfault at 0 ip 00002aae978f2345 sp 00002aae9a90c680 error 4 in ld-musl-x86_64.so.1[2aae978d5000+89000] Dec 4 18:27:51 Teknikum kernel: domoticz[42159]: segfault at 0 ip 00002aec34c5f345 sp 00002aec37c79680 error 4 in ld-musl-x86_64.so.1[2aec34c42000+89000] I belive that the sigma designs is the usb controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 0781:5530 SanDisk Corp. Cruzer Bus 001 Device 008: ID 0658:0200 Sigma Designs, Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 0424:2660 Standard Microsystems Corp. Hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  2. Hi, Im trying to get my docker Domoticz get connected to my new z-stick z-wave controller. Then i plugin the usb stick in the server i got a device name: yytam93 for example. Its seems that drivers is installed and everything is ok. But then i trying to add the controller in the domoticz application there is no connection between the z-stick and Domosticz. My question is: Do i need to the something in the docker config to get it work? Map the usb device into the docker? In the domosticz application I set /dev/yytam93 as my z-stick on the hardware tab. Big thanks in advance!
  3. i change the the command to br0 and now its works, i just ping 192.168.1.193 and I got a respone. They I tried to start the weblink via WebUI it takes the old ip adress but If i type the ip adress and port 8080 it works. Is there any way to change this?
  4. All my other containers running on the same ip adress with different ports. I just want to change the ip adress for the Domoticz I have no pipeworks settings for the other containers. They are up and running as well. Dont understand way this is so hard to set a static ip adress on a container. Is there some way to set an ip adress via the console SLI ?
  5. last picture that says that eth1 is not used...
  6. Logs for pipworks keeping saying: Device "eth1" does not exist. event_line=2017-11-15T20:08:58.618946004+01:00 container start a279f8091eb1da176d490e67adfd502b05bd680ea09c542c7acfa82d7da3ab5e (build_version=Linuxserver.io version:- 71 Build-date:- November-10-2017-23:52:39-UTC, image=linuxserver/domoticz, name=domoticz) Device "eth1" does not exist. event_line=2017-11-15T20:09:56.573557841+01:00 container die a279f8091eb1da176d490e67adfd502b05bd680ea09c542c7acfa82d7da3ab5e (build_version=Linuxserver.io version:- 71 Build-date:- November-10-2017-23:52:39-UTC, exitCode=0, image=linuxserver/domoticz, name=domoticz) event_line=2017-11-15T20:09:57.287172915+01:00 container start 45a527fe69fe6708fa739558d1a1011adfde902381aa5c40e4f856c73725d257 (build_version=Linuxserver.io version:- 71 Build-date:- November-10-2017-23:52:39-UTC, image=linuxserver/domoticz, name=domoticz) event_line=2017-11-15T20:13:53.618663394+01:00 container start 79d0195f1f0273356437c46fa5dd2627c2df290a82161104c03f2e0c7e09a747 (image=dreamcat4/pipework, name=pipework-1.1.6) event_line=2017-11-15T20:13:53.969464043+01:00 container start fda4b30fa2b1d9713de4526fdb437c7f172dec9ac8bfbd5e14f3778db8103705 (image=mace/ddclient, name=DDclient) event_line=2017-11-15T20:13:54.309723499+01:00 container start ef4d2d6468620f65850786c97152a44f0d3e7d4c208abe288a63ff4c1f4d0546 (image=limetech/plex, name=PlexMediaServer) event_line=2017-11-15T20:13:54.640568879+01:00 container start d5ed16b92c6a8a69c5dafe127465ed59c28baeb19267ef77ff289db39a375964 (image=pducharme/unifi, name=UniFi) event_line=2017-11-15T20:13:55.251236510+01:00 container start a05dd46e3449304a018e8f8a63fe1b411aa8c750720aea0eb7fc07a8ef6b410d (image=pducharme/unifi-video-controller, name=UniFi-Video) event_line=2017-11-15T20:15:25.874054663+01:00 container start ae55574896fc626e8dccf739521125645a754e037c82d906f0e197652206d15e (build_version=Linuxserver.io version:- 71 Build-date:- November-10-2017-23:52:39-UTC, image=linuxserver/domoticz, name=domoticz) Device "eth1" does not exist. Device "eth1" does not exist.
  7. But should i type br0 or eth0 ? Im bit confused here. Please check the picture of my network settings. then i type: -e 'pipework_cmd=eth0 @CONTAINER_NAME@ 192.168.1.193/[email protected]' its open my container https://192.168.1.192:8443/ i dont see any settings the eth1 or br0 ?
  8. Just checing the logs for pipworks: Device "eth1" does not exist. event_line=2017-11-15T19:42:49.791578810+01:00 container die e6db63e4c793ff44b1fb814974e47367092b702dba123a7193c97bf4c7c6c102 (build_version=Linuxserver.io version:- 71 Build-date:- November-10-2017-23:52w39-UTC, exitCode=0, image=linuxserver/domoticz, name=domoticz) why its picking up eth0 then i have named it to eth0 in the network settings.
  9. Hi again, I have now removed the docker network homenet I have allready installed pipework and its has been started accouring to the logs. I guess that the dockername should be "domoticz" or nothing else? I set the network - set the 'Enable Bridging' to Yes and set the 'Bridging Members' to the interface you intend to use eth0. The strang this is that when i type in a ip adress like 192.168.1.93 for example. see picture. When I start up the domoticz its open my other app unifi controller on ip adress: https://192.168.1.192:8443 Could it be something with the Host port and contaioner port? Whats the different? / johan
  10. HI, I feels that Im going for the pipworks solution. Okay, How do I enable br0 bridge? Should I remove the network called Homenet also. Whats the commands in the Extra options box ( parameter) for setting a new Ip adress for a container? Big thanks in advance!
  11. [services.d] done. 2017-11-13 19:36:15.609 Domoticz V3.8720 (c)2012-2017 GizMoCuz 2017-11-13 19:36:15.609 Build Hash: 2fc1ac2e, Date: 2017-11-10 15:07:42 2017-11-13 19:36:15.609 Startup Path: /var/lib/domoticz/ domoticz: Domoticz is starting up.... domoticz: Domoticz running... domoticz: PluginSystem: Started, Python version '3.6.1'. 2017-11-13 19:36:15.642 PluginSystem: Started, Python version '3.6.1'. domoticz: Active notification Subsystems: gcm, http (2/14) 2017-11-13 19:36:15.645 Active notification Subsystems: gcm, http (2/14) domoticz: WebServer(HTTP) started on address: 0.0.0.0 with port 8080 2017-11-13 19:36:15.664 WebServer(HTTP) started on address: 0.0.0.0 with port 8080 domoticz: WebServer(SSL) started on address: 0.0.0.0 with port 1443 2017-11-13 19:36:15.670 WebServer(SSL) started on address: 0.0.0.0 with port 1443 2017-11-13 19:36:15.670 Proxymanager started. domoticz: Proxymanager started. domoticz: Starting shared server on: 0.0.0.0:6144 2017-11-13 19:36:15.673 Starting shared server on: 0.0.0.0:6144 2017-11-13 19:36:15.673 TCPServer: shared server started... domoticz: TCPServer: shared server started... domoticz: RxQueue: queue worker started... 2017-11-13 19:36:15.673 RxQueue: queue worker started... domoticz: EventSystem: reset all events... 2017-11-13 19:36:17.675 EventSystem: reset all events... domoticz: EventSystem: reset all device statuses... 2017-11-13 19:36:17.675 EventSystem: reset all device statuses... 2017-11-13 19:36:17.695 Python EventSystem: Initalizing event module. 2017-11-13 19:36:17.695 EventSystem: Started 2017-11-13 19:36:17.695 EventSystem: Queue thread started... domoticz: Python EventSystem: Initalizing event module. domoticz: EventSystem: Started domoticz: EventSystem: Queue thread started... domoticz: EventSystem: reset all events... 2017-11-13 19:36:17.675 EventSystem: reset all events... domoticz: EventSystem: reset all device statuses... 2017-11-13 19:36:17.675 EventSystem: reset all device statuses... 2017-11-13 19:36:17.695 Python EventSystem: Initalizing event module. 2017-11-13 19:36:17.695 EventSystem: Started 2017-11-13 19:36:17.695 EventSystem: Queue thread started... domoticz: Python EventSystem: Initalizing event module. domoticz: EventSystem: Started domoticz: EventSystem: Queue thread started... 2017-11-13 19:36:18.121 PluginSystem: Entering work loop. domoticz: PluginSystem: Entering work loop.
  12. Hi, A strange thing is that when I change Host port to 1444 i get redirect to unother container: In some guides its says use: 'br0' but my networksetting says eth0. Which should I choose? Schould a bridge the nic to be able to use it?
  13. When i will run https: it will ports conflicts with other containers.
  14. im getting this errorcode often: /usr/bin/docker: Error response from daemon: failed to create the macvlan port: device or resource busy.
  15. Hi, Spent lots of time to clear this out but now I need someone who got some more expertizeee Im running a unraid 6.3.5 on a HP microserver. gen8 I need to change ip adresses on one of my container. ( domoticz ) the ports is in confict. I haved followed some guideline on google, pipework and this. None of them is working for me, and im i noobie in Linus. I have created a network: root@Teknikum:~# docker network inspect homenet [ { "Name": "homenet", "Id": "b5c44e9dfc6776cc452a82d9bd1f882f06e6fb62c442572cb6bd10cba9609340", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.1.0/24", "IPRange": "192.168.1.128/25", "Gateway": "192.168.1.1" } ] }, "Internal": false, "Containers": {}, "Options": { "parent": "eth0" }, "Labels": {} } ] root@Teknikum:~# docker network ls NETWORK ID NAME DRIVER SCOPE 68f3ccdc9a55 bridge bridge local b5c44e9dfc67 homenet macvlan local 2e2532ffa672 host host local cec9fbee9d1b none null local root@Teknikum:~# This is my network settings. I have 1 ethernet cabel connected to the microserver. This is my router. This is my config after failing installation. I have also tried this extra parameter: --cap-add=NET_ADMIN -e 'pipework_cmd=br0 @CONTAINER_NAME@ 192.168.1.91/[email protected] xx:xx:xx:xx:xx:xx' Not working, Does anyone have some tips or something I need to check? Please let my know if you need some more info Big thanks in advance!