10 hours ago, air_marshall said:

Can we get a tag for the latest stable? 3.8153

 

Currently using the 'latest' tag but experiencing some of the bleeding edge bugs which is ruining the WAF, but I need functionality that was added between the stable tag on the repo and the latest stable release.

 

I made the new branch, but the Jenkins-master is not around at the moment. So have to wait for him to be back to add the new branch to be built. 

On 8/25/2017 at 1:16 AM, Wob76 said:

Going to add another request

 

At the moment the custom icon uploading doesn't work, there is permission issues with 2 folders

/tmp and /var/lib/domoticz/www/images

I did a chmod 777 to both and the upload starts to work.

 

But even with it working, the new icons will not survive a docker update and the www/images folder is inside the container. Maybe moving the whole image folder into /config, that would fix the custom icons and floorplans.

 

Thanks,

Wob

+1 on Wob76 request; would love to have www in the config folder.

7 hours ago, soana said:

+1 on Wob76 request; would love to have www in the config folder.

 

It's not possible to move the www folder to /config as there are no option to set it at startup. Symlinking the folder is not an option we will use. 

Normally you would create a subfolder in www for your images? Then we might set up a www folder in /config that copies any subfolders on startup. 

I'll look at it when time permits it. Too busy with work lately. 

No hurries, I can copy my /config/www folder to /var/lib/domoticz/www at startup manually.

On 01/10/2017 at 7:49 PM, saarg said:

 

I made the new branch, but the Jenkins-master is not around at the moment. So have to wait for him to be back to add the new branch to be built. 

 

Any news on the ETA for the stable-3.8153 tag?

 

Many thanks!

19 minutes ago, air_marshall said:

 

Any news on the ETA for the stable-3.8153 tag?

 

Many thanks!

Sorry, no news. 

You do know you can use the latest to get the beta version? 

Edited November 2, 20178 yr by saarg

Forgive my ignorance, but can I just use the branch on github you created anyway, without the tag? If so, how?

8 hours ago, air_marshall said:

Forgive my ignorance, but can I just use the branch on github you created anyway, without the tag? If so, how?

 

No you can't unless you build it yourself. 

If you remove domoticz and install it again, you can choose the default branch which gives you the latest development on domoticz github when the image was refreshed weekly. You can also just remove the :stable part after linuxserver/domoticz in the repository box. 

I am trying to restore a DB from another Domoticz install and getting the following error in the logs:

2017-11-14 09:00:02.684 Error: Restore Database: Could not open backup file for writing!

6 hours ago, rlust said:

I am trying to restore a DB from another Domoticz install and getting the following error in the logs:

2017-11-14 09:00:02.684 Error: Restore Database: Could not open backup file for writing!

 

Never tried it, so can't say if it works correctly. 

Where did you have the file and what permissions does it have? It should be owned by nobody:users and have 755 permissions for domoticz to have the rights to write. 

I have an instance that is running on a Rasp Pi that I have been able to backup and restore to a 3rd system on a OSX MAC several times.

 

I think that there is a permission issue, but not sure where to look.

 

I can't tell you where to look as only you know where the backup is located. I already told you the permissions it need and asked where the backup was located, but as you don't answer my question, it's hard to help.

I seem to be getting double logging, I searched domoticz and couldn't find an answer there so thinking it may be related to the docker, if I follow the logs I see entries like..

 

2018-01-15 09:42:03.199  (Mi Gateway) General/kWh (Fridge Power Usage)
domoticz: (Mi Gateway) General/kWh (Fridge Power Usage)
 

I usually just grep using ^2018 to reduce the output, but is there a way to stop this behavior?

 

Thanks,

Wbo

36 minutes ago, Wob76 said:

I seem to be getting double logging, I searched domoticz and couldn't find an answer there so thinking it may be related to the docker, if I follow the logs I see entries like..

 

2018-01-15 09:42:03.199  (Mi Gateway) General/kWh (Fridge Power Usage)
domoticz: (Mi Gateway) General/kWh (Fridge Power Usage)
 

I usually just grep using ^2018 to reduce the output, but is there a way to stop this behavior?

 

Thanks,

Wbo

 

Use the log in domoticz instead. 

I'll see if I can limit the logging to the container log.

1 minute ago, saarg said:

 

Use the log in domoticz instead. 

I'll see if I can limit the logging to the container log.

 

That log doesn't go back very far, I can really only filter back minutes, I have busy logs, so it doesn't really help.

 

As mention, using grep filters it down, but seems a waste of resources storing 2 lines in the logs.

I am pulling a fresh container in an attempt to diagnose some crashes I am seeing lately. I ran into the problem awhile ago when updating, but forgot to post.

 

There seems to be an issue with dzVents if you pull the latest version, its looking for it in /config

Error: EventSystem: in /config/dzVents/runtime/dzVents.lua: cannot open /config/dzVents/runtime/dzVents.lua: No such file or directory

I can't actually find dzVents.lua at all, my fix was to git pull dzVents into the config folder.

 

Wob.

11 hours ago, Wob76 said:

I am pulling a fresh container in an attempt to diagnose some crashes I am seeing lately. I ran into the problem awhile ago when updating, but forgot to post.

 

There seems to be an issue with dzVents if you pull the latest version, its looking for it in /config

Error: EventSystem: in /config/dzVents/runtime/dzVents.lua: cannot open /config/dzVents/runtime/dzVents.lua: No such file or directory

I can't actually find dzVents.lua at all, my fix was to git pull dzVents into the config folder.

 

Wob.

 

dzVents is not a part of a domoticz install is it?

As far as the forum it is now part of the new betas.

Sent from my SM-G935F using Tapatalk

7 hours ago, Wob76 said:

As far as the forum it is now part of the new betas.

Sent from my SM-G935F using Tapatalk
 

 

That was a cryptic line  

I checked the latest version here and I do not see the error you have. When does the error happen?

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

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

 

 

 

 

I used 3.8805 and didn't see it. I haven't used any dzVents script though.

But if you have pulled down dzvents from github into the config folder, this might be the reason you see the error. I find dzvents in /config/scripts/

I used 3.8805 and didn't see it. I haven't used any dzVents script though.
But if you have pulled down dzvents from github into the config folder, this might be the reason you see the error. I find dzvents in /config/scripts/

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

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/scripts/dzVents/generated_scripts/Test.lua
2018-01-22 11:08:00.055  Domoticz V3.8805 (c)2012-2018 GizMoCuz
2018-01-22 11:08:00.055  Build Hash: e160f7cc, Date: 2018-01-10 01:56:44
2018-01-22 11:08:00.067  Startup Path: /var/lib/domoticz/
2018-01-22 11:08:00.097  PluginSystem: Started, Python version '3.6.3'.
2018-01-22 11:08:00.100  Active notification Subsystems: gcm, http (2/14)
2018-01-22 11:08:00.101  WebServer(HTTP) started on address: :: with port 8080
2018-01-22 11:08:00.104  WebServer(SSL) started on address: :: with port 1443
2018-01-22 11:08:00.105  Proxymanager started.
2018-01-22 11:08:00.106  Starting shared server on: :::6144
2018-01-22 11:08:00.107  TCPServer: shared server started...
2018-01-22 11:08:00.107  RxQueue: queue worker started...
2018-01-22 11:08:02.108  EventSystem: reset all events...
2018-01-22 11:08:02.109  EventSystem: Write file: /config/scripts/dzVents/generated_scripts/Test.lua
2018-01-22 11:08:02.111  EventSystem: reset all device statuses...
2018-01-22 11:08:02.131  Python EventSystem: Initalizing event module.
2018-01-22 11:08:02.131  EventSystem: Started
2018-01-22 11:08:02.132  EventSystem: Queue thread started...
2018-01-22 11:08:02.579  PluginSystem: Entering work loop.
2018-01-22 11:08:06.741  Incoming connection from: 192.168.0.250
2018-01-22 11:08:11.207  EventSystem: reset all events...

 

Have you tested that this doesn't happen on another system?