Domoticz

Update: It got merged.

Hi folks,

I have prepared a Pull Request for merging dzVents 2.2.0 into Domoticz. All seems to work quite well but before merging this into the main branch I'd like to have some more people test this branch with their system. The branch can be found in here. It is up to date with current Domoticz master.

So, please download or do a check-out of this branch. Compile it and run it with (a copy of) your database and let me know if it works for you as expected or not. If you do a checkout don't forget to switch to 'dev' branch!!

I want to have this in Domoticz before a new stable is made available because it has a couple of necessary bug fixes.

Changes for 2.2.0:
- Fixed typo in the doc WActual > WhActual.
- Updated switch adapter to match more switch-like devices.
- Added Z-Wave Thermostat mode device adapter.
- Fixed a problem with thermostat setpoint devices to issue the proper url when updating.
- Added secondsSinceMidnight to time attributes (e.g. lastUpdate.secondsSinceMidnight)
- Added 4 new time-rules: xx minutes before/after sunset/sunrise.
- Added example script to fake user presence.
- Fixed support for uservariables with spaces in their names.
- Show a warning when an item's name isn't unique in the collection.
- Show a warning if the scene or group isn't available right after creating it. Needs a Domoticz restart.
- Added timing options for security methods armAway, armHome and disarm.
- Added idx, deviceId and unit to device objects. Don't confuse deviceId with device.id(x) which is actually the index of the device.
- Added instructions on how to create a security panel device in Domoticz. This device now has a state that has the same value as domoticz.security.

We also fixed a few things in Domoticz: new scenes/groups are now immediately available to the event system (lua/dzVents etc). lastUpdate is now correctly passed to the event system so it does show the previous update correctly for the device that was triggered (instead of the current time).

Hi Danny,

I am on the way to compile and test your version. But bad day - checked out and compiled wrong branch master, on RPi almost 1 hour... uh.

Compiling correct dev branch now...

Hi Danny,

compiled and running. At first impression, my devices are working normally. New/changed dzVents device adapters (Zwave thermostat mode, Thermostat setpoint) tested and works as expected.

Thank you

dannybloe wrote:Update: It got merged.

Great. Then I won't have to set up a development environment and compile Domoticz. Do You have any idea about in what Domoticz version dzVents 2.2.0 will be available? I will install as soon as possible.

3.8143+

I'm trying to switchOn a Hue-group with dzVents 2.1.0.. :

2017-07-25 18:21:00.455 Error: dzVents: Error: Method switchOn is not available for device "Group Eetkamer" (deviceType=Lighting Limitless/Applamp, deviceSubType=RGBW). If you believe this is not correct, please report.
I'm on Domoticz Version: 3.8134

Thanks..

Same issue on version 3.8143 with 2.2.0. Perhaps I am doing something wrong?
Must say this is a client--master setup. running the script from the client with a server connection to the master..

I think it is a cache issue. If you dare, you can open www/views/setup.html and search for "2.2.0". You should see it there.
Try clearing your browser cache manually. That should do the trick.

Think i found the issue: running the 3.8143 version from Jadahl.. conclusion from dzVents/documentation/history.md this version is still running 2.0.0.
** [2.0.0] Domoticz integration **

What's Jadahl?
My history.md does show 2.2.0.

I just downloaded the package for synology and (apart from a weird file structure) it seems to have the latest dzVents 2.2.0 code in there.

Nope!
I have updated dzVents to 2.2.0 in synology v3.8143 packages!
Maybe some browser Cach problem?

The file structure is like this on synology: /usr/local/domoticz/var/scripts/dzVents$

If not my browser with a cash problem I sure as hell have some of my own :-p
Cash is always welcome.

But caching doesn't affect the functioning of dzVents as it is all triggered by the event system. Caching may show you an older version number in the settings for dzVents (should show 2.2.0) but clearly for some reason caches aren't always cleared.

i know.. this is my /usr/local/domoticz/var/scripts/dzVents/documentation/history.md

cat history.md

[2.0.0] Domoticz integration

- Almost a complete rewrite.
- **BREAKING CHANGE**: Accessing a device, scene, group, variable, changedDevice, or changedVariable has been changed: instead of doing `domoticz.devices['myDevice']` you now have to call a function: `domoticz.devices('myDevice')`. This applies also for the other collections: `domoticz.scenes(), domoticz.groups(), domoticz.changedDevices(), domoticz.changedVariables()`. If you want to loop over these collection **you can no longer use the standard Lua for..pairs or for..ipairs construct**. You have to use the iterators like forEach, filter and reduce: `domoticz.devices().forEach(function() .. end)` (see [Iterators](#Iterators)). This was a necessary change to make dzVents a whole lot faster in processing your event scripts. **So please change your existing dzVents scripts!**
...
...

did a package upgrade from the package center.
Weird thing is.. it's showing 2.2.0 version in the settings.
DS412+ .. doing a package reinstall tomorrow.. can't be a cache problem. Weird.

This is because of backup restore function when update the package on the synology.
If you reinstall the package, the history will show correct version.
I have No solution to fix this right now, but maybe later
If you check in settings menu it will show 2.2.0

dannybloe wrote:Update: It got merged.

jumbotroll wrote:If you check in settings menu it will show 2.2.0

I also did a synology update today; it seems like the dzVents scripts are not loaded by default, unless you 'touch' one of the scripts in the scripts/dzVents/scripts/ folder. It might be update related, but i hope the scripts are loaded when domoticz is restarted/nas rebooted.

edit: i have a script (symlink) in the /scripts/dzVents/scripts/ folder, pointing to another location on my nas which i can actually edit from windows. This 'file' is no longer loaded 'by default' it seems. Can you check?

jumbotroll wrote:This is because of backup restore function when update the package on the synology.
If you reinstall the package, the history will show correct version.
I have No solution to fix this right now, but maybe later
If you check in settings menu it will show 2.2.0

reinstalled and working. Now i can transfer my scripts from RPi (2B not fast enough) to Synology Thank you for your effort in building the synology packages.