OZW refresh automatisation script

For Z-Wave related questions in Domoticz

Moderator: leecollings

Post Reply
samuelAN
Posts: 40
Joined: Tuesday 12 December 2017 14:51
Target OS: Windows
Domoticz version:
Contact:

OZW refresh automatisation script

Post by samuelAN »

Hello,

I have one FGT001 heat controller working on domoticz. I would like to poll the device when a temperature setpoint is sent to it (after some seconds).

(For those who are following the issue with the FGT001 is that OZW does not handle the way the FGT001 send back its new setpoint value... Consequencly, in order to have an up to date setpoint in Domoticz, is it necessary to enable polling of the device... which drains very fast the batteries)

The idea is to force polling after applying a new setpoint, and use a "classical" polling configuration with very large interval (i.e 1 hour) in order to avoid dead node.

With some search, I found a script called "RefreshZwave", but I have no idea if this kind of script would help and how to put it in place (I am not an expert with Domoticz...)

Can someone help me with that?

Thanks !!
samuelAN
Posts: 40
Joined: Tuesday 12 December 2017 14:51
Target OS: Windows
Domoticz version:
Contact:

Re: OZW refresh automatisation script

Post by samuelAN »

The "RefreshZwave" script that I found is the following :

Code: Select all

#!/usr/bin/php
<?php
$domoticzurl='http://ip:port/';
file_get_contents($domoticzurl.'json.htm?type=openzwavenodes&idx=5'); //Change idx to idx of zwave hardware
RefreshZwave(10); //Updates zwave device with zwave ID 10. 

function RefreshZwave($node) {
	global $domoticzurl;
	$zwaveurl=$domoticzurl.'ozwcp/refreshpost.html';
	$zwavedata=array('fun'=>'racp','node'=>$node);
	$zwaveoptions = array('http'=>array('header'=>'Content-Type: application/x-www-form-urlencoded\r\n','method'=>'POST','content'=>http_build_query($zwavedata),),);
	$zwavecontext=stream_context_create($zwaveoptions);
	
samuelAN
Posts: 40
Joined: Tuesday 12 December 2017 14:51
Target OS: Windows
Domoticz version:
Contact:

Re: OZW refresh automatisation script

Post by samuelAN »

Nobody can help me ? :(
User avatar
Egregius
Posts: 2592
Joined: Thursday 09 April 2015 12:19
Target OS: Linux
Domoticz version: v2024.7
Location: Beitem, BE
Contact:

Re: OZW refresh automatisation script

Post by Egregius »

This script will only work if a refresh command from ozwcp works.
samuelAN
Posts: 40
Joined: Tuesday 12 December 2017 14:51
Target OS: Windows
Domoticz version:
Contact:

Re: OZW refresh automatisation script

Post by samuelAN »

Thanks Egregius , indeed the refresh command updates all information but .. not the setpoint value... so this will not work :(

No other idea to make a one time polling ?
dekkerjj
Posts: 4
Joined: Sunday 28 May 2017 0:37
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: OZW refresh automatisation script

Post by dekkerjj »

I had exactly the same question and after a lot of googling and even checking the github-code I found a super-easy way to completely refresh a specific node that works for me.

httpS://IP:port/json.htm?type=command&param=requestzwavenodeinfo&idx=X
where IP:port is your domoticz installation and X is the Zwave-node-number + (it seems 16)
f.e.
IMy FGT has NodeID 010 (0x0a), so I invoke : http://Domo-IP:8080/json.htm?type=comma ... nfo&idx=26

I checked with a friend and it does NOT work with OZW 1.4 (but latest stable has OZW 1.6)

I haven't got a clue if the +16 is installation-dependant.
You can check the ID by going to 'hardware' in Domoticz, click OpenZwave USB 'Settings' . select a node in the page that follows and hover over 'Refresh Node info'. Bottom-left in your screen or in the status bar you'll see 'javascript:RefreshNode(Devicenumber)'

Hope this helps.
User avatar
Egregius
Posts: 2592
Joined: Thursday 09 April 2015 12:19
Target OS: Linux
Domoticz version: v2024.7
Location: Beitem, BE
Contact:

Re: OZW refresh automatisation script

Post by Egregius »

Keep in mind that this command will erase all personal settings of the node and restore it to factory defaults!

Code: Select all

2020-04-10 06:34:01.472  Status: OpenZWave: Node Removed. HomeID: 3911421806, NodeID: 126 (0x7e)
2020-04-10 06:34:01.897  OpenZWave: Value_Added: Node: 126 (0x7e), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1, Index: 0
2020-04-10 06:34:01.897  OpenZWave: Value_Added: Node: 126 (0x7e), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 1, Index: 0
2020-04-10 06:34:01.897  Status: SendSwitchIfNotExists: Device '126.instance.1.index.0.commandClasses.48' (Sensor) with DeviceID '00007E00' matches '126.instance.1.index.256.commandClasses.113' (Previous Event Cleared). Domoticz will use the Dimmer (and hide the Switch).
2020-04-10 06:34:01.966  OpenZWave: Value_Added: Node: 126 (0x7e), CommandClass: SENSOR MULTILEVEL, Label: Air Temperature, Instance: 1, Index: 1
2020-04-10 06:34:02.104  OpenZWave: Value_Added: Node: 126 (0x7e), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 1, Index: 256
2020-04-10 06:34:02.104  Status: SendSwitchIfNotExists: Device '126.instance.1.index.256.commandClasses.113' (Previous Event Cleared) with DeviceID '00007E00' matches '126.instance.1.index.0.commandClasses.48' (Sensor). Domoticz will use the Dimmer (and hide the Switch).
2020-04-10 06:34:02.104  OpenZWave: Value_Added: Node: 126 (0x7e), CommandClass: ALARM, Label: Home Security, Instance: 1, Index: 7
2020-04-10 06:34:02.861  Status: OpenZWave: Alarm received (Home Security: Clear), NodeID: 126 (0x7e)
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest