• Content Count

  • Joined

  • Last visited

Everything posted by Wob76

  1. Yeah, I also tried an alternative browser, it's odd, 2.0 without VPN (PIA) works fine, v1 with VPN (PIA) no problem, only change between them is the repository being pulled. Are those with it working use PIA or another VPN provider? I'll investigate further at some point but for now I'm happy with v1, might wait for the plugin support to be ported. Thanks for the help. Sent from my Pixel 3 XL using Tapatalk
  2. I can't access the web UI with 2.0, but rolling back fixes it, did the configuration requirements change? Sent from my Pixel 3 XL using Tapatalk
  3. Good to know, so does the web GUI fall into the 3rd party plugin category? Wob Sent from my Pixel 3 XL using Tapatalk
  4. So rolling back to binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04 fixes my issue, but it's not just the deluge port that isn't working, I can't connect to the web socket or the privoxy ports, logs are not giving me much indication of the issue. Wob
  5. I tried directly on the docket port for the web, I usually access via reverse proxy, neither work. With VPN on I don't see any activity in the deluge web log. Here is the run command, but it hasn't been changed in months so I don't think it's the issue. docker run -d --name='delugevpn' --net='bridge' --log-opt max-size='50m' --log-opt max-file='3' --privileged=true -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXX' -e 'VPN_PASS'='XXXX' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='
  6. I'm just trying to access the web GUI and I get nothing with the VPN on, I did try the windows app but it is probably outdated, I first noticed the issue as SickChill had an issue pushing a download to it. It was working find just a few days ago, but I can't work out if the issue is from the update or if it's a PIA issue. Sent from my Pixel 3 XL using Tapatalk
  7. As with a few others I seem to be having problems with PIA, It's been running fine since I moved from rutorrent around December last year, but stopped today after updating the docker yesterday. I have rolled back 2 versions and still can't get to the GUI and other dockers can't send torrents to it, I also tried a different PIA server to see if that was the issue without success. If I disable the VPN the GUI works. No sign of any issues within the logs that I can see. supervisord.log (VPN USER\PASS Masked) Created by... ___. .__ .__ \_ |__ |__| ____ | |__
  8. Nice, I just did a quick test and I seem to get speeds more aligned with my connection, are you planning on updating the plugin to use this? Thanks, Wob
  9. Is anyone else finding the setting are not saving between reboots? Each time I start up nothing is configured within this plugin.
  10. Not exactly helpful considering this is a couchpotato thread. I am still waiting for nest folder support in the library before radar is useful for me. Sent from my SM-G935F using Tapatalk
  11. Hi, thanks for the plugin, I just installed this as I am having some issues with nodered startup, hoping a delay will help. I have 2 nodered containers, nodered nodered.dev I can only select the first of the two, I can select the rest OK, so seems it be the names are too similar, or the fact the icons are both the same? Thanks, Wob Sent from my SM-G935F using Tapatalk
  12. Just an update on my progress, It seems to be a stability issue with dzVents, with that disabled the docker is fairly stable (still crashed after a week), but as soon as I enable the scripts it will crash every few days. I have updated with each docker release, and currently at the version with Domoticz v3.8875, still crashing. The VM I am running is on v3.8834 and has been up for almost 13 days, so for the moment I am going to stick with a VM, seems more logical for my config as I have a few customisations I was having to do after each pull anyway, resources are higher
  13. OK, I built up a VM with ubuntu server 16.04.3 and pulled down domoticz as per the install guide (https://www.domoticz.com/wiki/Linux) to ensure I wasn't messing anything up. After the install dzVents runtime is located in ~/domoticz/dzVents/runtime I did the same thing I was doing on a new pull of the container, created a dzvents script using the example code, this caused caused a segfault crash of the system. I found a thread that suggested going to Setup\Settings\Other and disabling both EventSystem and dzVents and then re-enabling them. This fixed the segfault.
  14. @ken-ji Thanks for the details, I guess I could look at setting up a VLAN, seems like an odd choice to be able to put a device on a LAN, but not have it talk to other device on the LAN (Host or otherwise). For the moment I'll just stick with pipeworks, it has been plodding along nicely for some time now.
  15. Domoticz is a frustrating beast. On one had the development seems patchy and the forums are not very responsive to questions or issues. On the other hand it seems to be the easiest and most flexible open source home automation option, I have tried HASS, OpenHAB and a anything else I could find to run in a docker, and domoticz is still the best choice for me. I have told myself a couple of times that I would move to another system when I couldn't get help on the forum, but I have managed to fix the problem eventually. I am going to give a Smartthing hub a go soon, but I don't think
  16. I'll report back how I go. Sent from my SM-G935F using Tapatalk
  17. I haven't actually run Domoticz on another system, but I might look at firing it up on a Linux VM, my list of modifications after a pull is getting a bit long. Or maybe it should move onto a pi. Sent from my SM-G935F using Tapatalk
  18. dzVents is definitely broken in the image. If I pull a fresh docker, and just create a test script, save using the demo code, which does nothing except make a log entry when a switch is pressed, the system becomes unstable, and continually restarts once every minute. I tried making a dummy switch and linking the script to that switch, but its still unstable. If I click said switch I see "Problem sending switch command" and trigger a restart. 2018-01-22 11:07:31.636 EventSystem: reset all events... 2018-01-22 11:07:31.636 EventSystem: Write file: /config/scr
  19. I have previously been using pipeworks to assign unique IP's to a few dockers, I thought I would move to the new inbuilt option, it works fine talking to the new docker from my network, but those dockers are not able to see the host, or any other dockers on the host. my subnet is and I am just entering the ip like Another question, is the MAC address that gets assigned to a docker in this fashion static, if I wanted to use DHCP? Am I missing something?
  20. @coppit Thanks so much for the update. My memory usage dropped from 430Mb to 20Mb and CPU from around 4% to 0.21%, so back to my happy days of low resources.
  21. I did the pull after the error, to fix it, I may have messed something up in my database at some point. The scripts folder is the old location according to that thread. I'll pull a fresh image at some point and just install a single dzVents script, leaving my database out of it, and report back. Sent from my SM-G935F using Tapatalk
  22. I just read more of the first post, under the heading "New Location" he mentions moving the runtime environment and that it will clear out the old location, so I would say when I hit 3.8551 is when I first saw the issue. Sent from my SM-G935F using Tapatalk
  23. Sorry, a rushed response while I was out and about as of 3.8551 dzVents is included according to this thread on the Domoticz forums. https://www.domoticz.com/forum/viewtopic.php?t=19738 I noticed the error after importing my backup, maybe it only happens after enabling a dzVents script? Are you running any? My test build is also crashing, so I'll have to dig to find out what's causing it I'll do a fresh pull again and see if I can reproduce the error and when it happens. Sent from my SM-G935F using Tapatalk
  24. As far as the forum it is now part of the new betas. Sent from my SM-G935F using Tapatalk