Domoticz

timovd wrote: On the FIbaro Dimmer 2, I press the B-button three times to put it in learning mode, but nothing is happening. There is about 2 meter distance between the Z-stick and the Dimmer. Am I still doing something wrong?

The USB stick is now correctly recognized?
Try pressing the buttons 4 times. That works for me sometimes (1 for waking it up and then 3 for adding it).

Getting there... It's connected now. How can I make the Dimmer visible at tab "Switches"?

timovd wrote: How can I make the Dimmer visible at tab "Switches"?

Goto Setup - Devices and look for the dimmer. Then press the green arrow to add the device.

ThinkPad wrote:Does anyone here have succesful spindown of the disks while using the packages from jumbotroll?

Haven't paid attention to it yet, but most of the time my NAS is doing only stuff that doesn't require any disk activity like VPN-server or Domoticz. So the ideal situation would be to have the disks in spindown and only let them spin up when the disks really need to be accessed.
But i'm not sure if the disks spindown, will put a Z-Wave plug between the NAS powersupply so i can monitor it.

But if it doesn't go to sleep, would there be any options to modify Domoticz to prevent it from accessing the disks every now and then? (maybe it writes the log to the disks on a set interval?).
Anyone experience with that?

My experience is that with Domoticz the NAS will not go in spindown mode because the logfile is continually been written to. The logfile is in the domoticz/var directory.
If it is possible that Domoticz writes to a log file on a USB stick then the NAS could probably go in hibernation. This is also working for other programs like Sickbeard.

@Jumbotroll, do you think it is possible to change the path of the log file? Or should there first be an option in Domoticz to change the path where the log file is stored?

G3rard wrote: @Jumbotroll, do you think it is possible to change the path of the log file? Or should there first be an option in Domoticz the change the path where the log file is stored?

I think this must be changed in domoticz source.

Regards
Jumbotroll

I recently upgrade to version 2.3075 but this has broken the energy readings from my solar inverter through SBFspot (SMA inverter with speedwire). The sensor is there in Domoticz and it can read other realtime data like the voltage of my inverter but it reports energy unknown in the log (which is ofcourse the data I'm really after). I'd like to rollback to a previous version of the Domoticz package but I cant seem to figure out how to do this. Could someone enlighten me?

Take a backup of database in domoticz first, then delete V2.3075.
Manually download an older "working version" from here http://jadahl.dscloud.me/sspks/index.php?fulllist=true
an manually install before you restore database from domoticz.

Regards
Jumbotroll

G3rard wrote:

ThinkPad wrote:Does anyone here have succesful spindown of the disks while using the packages from jumbotroll?

Haven't paid attention to it yet, but most of the time my NAS is doing only stuff that doesn't require any disk activity like VPN-server or Domoticz. So the ideal situation would be to have the disks in spindown and only let them spin up when the disks really need to be accessed.
But i'm not sure if the disks spindown, will put a Z-Wave plug between the NAS powersupply so i can monitor it.

But if it doesn't go to sleep, would there be any options to modify Domoticz to prevent it from accessing the disks every now and then? (maybe it writes the log to the disks on a set interval?).
Anyone experience with that?

My experience is that with Domoticz the NAS will not go in spindown mode because the logfile is continually been written to. The logfile is in the domoticz/var directory.
If it is possible that Domoticz writes to a log file on a USB stick then the NAS could probably go in hibernation. This is also working for other programs like Sickbeard.

@Jumbotroll, do you think it is possible to change the path of the log file? Or should there first be an option in Domoticz to change the path where the log file is stored?

jumbotroll wrote:

G3rard wrote: @Jumbotroll, do you think it is possible to change the path of the log file? Or should there first be an option in Domoticz the change the path where the log file is stored?

I think this must be changed in domoticz source.

Regards
Jumbotroll

It seems it is a parameter in the file that starts Domoticz:
http://domoticz.com/forum/viewtopic.php ... cation+log
Maybe it can be changed in the package? But i don't know to what... i would say /volume2/, but there are probably users that have multiple volumes, so a USB-disk would become /volume3/
Or just write it to the RAM I never needed to look back in the log

But not only the log is updated, also the domoticz.db ofcourse.... So if the HDD's would be in spindown and you turn on a light, the 'ON' entry is written to the database --> HDD's turn back on.
I think it is quite hard to get the HDD's in spindown... problem is bigger than i thought

There is no problem to change the path where to save the logfile in the dsm-control.sh, but where do we want it?
There is so many different wishes and the best thing would be to have standard setting.
I did think about a different solution, with a wizard when the user installing domoticz on synology with different settings, but time will show if my skills in programming allow this

Regards
Jumbotroll

Update
Domoticz V2.3107.
OpenZWave 1.3.487.

New
Added arch-comcerto2k for DS414j

Regards
Jumbotroll

jumbotroll wrote:Take a backup of database in domoticz first, then delete V2.3075.
Manually download an older "working version" from here http://jadahl.dscloud.me/sspks/index.php?fulllist=true
an manually install before you restore database from domoticz.

Regards
Jumbotroll

Thanx a bunch, a rollback fixed my issue. So it looks like I'm stuck for now.

Did notice that the full list only contains two versions per architecture at the moment while there where more when I first looked at it.

Phuturist wrote:

jumbotroll wrote:Take a backup of database in domoticz first, then delete V2.3075.
Manually download an older "working version" from here http://jadahl.dscloud.me/sspks/index.php?fulllist=true
an manually install before you restore database from domoticz.

Regards
Jumbotroll

Thanx a bunch, a rollback fixed my issue. So it looks like I'm stuck for now.

Did notice that the full list only contains two versions per architecture at the moment while there where more when I first looked at it.

I delete older files when I update some times to release some space on my server.
Have you tested the update domoticz v2.3107 to see if the bug was fixed in the source?
You can check the commits in the source code here: https://github.com/domoticz/domoticz/commits/master

Edit: Problem with Energy Sensor and Alert since version 3072 http://www.domoticz.com/forum/viewtopic.php?f=6&t=8175

Regards
Jumbotroll

Hi, I installed v2.3113, but it crashed after a while. The version prior to this crashed every few minutes. What is going on with the latest versions? They seem to work for a while, but then......

mvveelen wrote:Hi, I installed v2.3113, but it crashed after a while. The version prior to this crashed every few minutes. What is going on with the latest versions? They seem to work for a while, but then......

v2.3113 is working stable here, but can you see what causes the crash in the log?
Is anyone else have problem with v2.3113?
I am only using rfxcom and testing with rflink, maybe it's the latest openzwave that causes this crash?
Maybe I should roll back to an older version of openzwave?

Regards
Jumbotroll

No, I can't see what it causes. It keeps running for an hour or longer and then it just stops. Can't see the log then.

Do you have the v2.3050 version somewhere? That one was OK. Perhaps it is the OpenZWave part.....?

If it is the DB, is there some tooling which I can use to check the DB?

v2.3113 is working fine on my DS715, updated the package yesterday at ~18:00, no problems at all.
Using RFXCOM and Aeon S2 Z-Wave stick, all working fine.

So it's a bit weird that some have issues, and some don't have any problems at all.

mvveelen wrote:No, I can't see what it causes. It keeps running for an hour or longer and then it just stops. Can't see the log then.

Do you have the v2.3050 version somewhere? That one was OK. Perhaps it is the OpenZWave part.....?

If it is the DB, is there some tooling which I can use to check the DB?

The logfile is in the domoticz/var folder. Maybe that gives some more information.

mvveelen wrote:No, I can't see what it causes. It keeps running for an hour or longer and then it just stops. Can't see the log then.

Do you have the v2.3050 version somewhere? That one was OK. Perhaps it is the OpenZWave part.....?

If it is the DB, is there some tooling which I can use to check the DB?

Sorry, v2.3050 was deleted from my server.
I have build a testbuild for you with older openzwave (1.3.482)
Download from my Beta section: http://www.jadahl.com/beta.html

Regards
Jumbotroll

@mvveelen Have you updated your Hue firmware? That is causing an issue for others.
http://www.domoticz.com/forum/viewtopic ... 191#p55921

Hi, I don't have any Hue lights. Thanks for the advice.

@Jumbotroll, is it possible to update to that test-version instead of installing it? I don't really want to delete the whole again and install it afterwards. I have some scripts etc. that I have to upload each time and give the files the right permissions.

v2. 3037 is running smoothly since this morning with 1 flaw:

2015-09-25 08:57:22.385 Error: SQL Query("SELECT Value, Date FROM MultiMeter_Calendar WHERE (DeviceRowID==93 AND Date>='2015-09-18' AND Date<='2015-09-25') ORDER BY Date ASC") : no such column: Value

There seems to be a DB change (??), and going back to the v2.3037 results in no more readings from my Fibaro Wall Plug.

Edit: nevermind, I uninstalled v2.3037 and installed v2.3116

This is an error message I got:

Error: SQL Query("ALTER TABLE Hardware ADD COLUMN [Extra] VARCHAR(200) DEFAULT ('')") : duplicate column name: Extra

Probably no issue ?

Edit 2:

The readings for the FWP are back Now, let me see if it keeps running the next few hours or more.

Thanks Jumbotroll !

Edit 3:

I see this error once in a while popping up in the log:

Error: Kodi: (Kodi) Async Read Exception: Operation canceled

Edit 4:

I decided to delete the Kodi "hardware". After adding it again, the same error pops up. So....no more Kodi status for me at this moment.