Domoticz

dannybloe wrote: Wednesday 21 February 2018 16:49 What you can do is create the device in the GUI and check the network tab to see what url is called. Then use that url from dzVents using openURL.

manjh wrote: Wednesday 21 February 2018 16:58

dannybloe wrote: Wednesday 21 February 2018 16:49 What you can do is create the device in the GUI and check the network tab to see what url is called. Then use that url from dzVents using openURL.

Thanks. But this script will be run frequently, so I want to prevent any unnecessary overhead.

The script is checking the WAN IP address on regular intervals, and stores the found address in a text device for the next check. When a new IP is found, it will send an e-mail so I can update my DNS entries.
Normally, the text device would be created manually at install of the script. The user is instructed to do so. But if he forgets, or makes a typo in the name...
That's why I thought a quick check for device status would be "light" enough.
But after explaining all this, I am beginning to think I should not even go this route but rely on manual creationg of the device.

Nevertheless, the programmer in me is curious how this might be done...

I have used Blockly very briefly, but that did not last long. Switched over to LUA and have been happy with that. A few days ago I tripped over dzVents, and it is looking very interesting. Has a good mix of being user-friendly (like Blockly) and still being able to do exactly what I want, down to the last bit and byte (like LUA).
Looking forward to learning more of dzVents...

return {

    on = { timer = {'every minute '} }, 
    
    execute = function(domoticz)
    
        if domoticz.devices('My_External_IP') == nil then 
            domoticz.openURL('http://pi-1:8084/json.htm?type=createdevice&idx=16&sensorname=My_External_IP&sensormappedtype=0xF313')
        else    -- Because of the async nature of openURL the device is not yet created in the initial run so we need to wait at least one cycle
            domoticz.devices('My_External_IP').updateText(os.date("last update at %X on %A %d %B %Y"))
        end
    end
}


--  2018-02-22 01:29:00.757  dzVents: Info:  ------ Start external script: CheckExternalIP.lua:, trigger: every minute
--  2018-02-22 01:29:00.761  dzVents: Info:  ------ Finished CheckExternalIP.lua
--
--  Given the 4 mSecs this check and update takes on my PI-3,  I don't think you need to be overly worried about unnecessary overhead. 
--
-- 

waaren wrote: Thursday 22 February 2018 1:37

Code: Select all

return {

    on = { timer = {'every minute '} }, 
    
    execute = function(domoticz)
    
        if domoticz.devices('My_External_IP') == nil then 
            domoticz.openURL('http://pi-1:8084/json.htm?type=createdevice&idx=16&sensorname=My_External_IP&sensormappedtype=0xF313')
        else    -- Because of the async nature of openURL the device is not yet created in the initial run so we need to wait at least one cycle
            domoticz.devices('My_External_IP').updateText(os.date("last update at %X on %A %d %B %Y"))
        end
    end
}


--  2018-02-22 01:29:00.757  dzVents: Info:  ------ Start external script: CheckExternalIP.lua:, trigger: every minute
--  2018-02-22 01:29:00.761  dzVents: Info:  ------ Finished CheckExternalIP.lua
--
--  Given the 4 mSecs this check and update takes on my PI-3,  I don't think you need to be overly worried about unnecessary overhead. 
--
-- 

dannybloe wrote: Wednesday 21 February 2018 16:49 What you can do is create the device in the GUI and check the network tab to see what url is called. Then use that url from dzVents using openURL.

manjh wrote: Saturday 24 February 2018 12:31

waaren wrote: Thursday 22 February 2018 1:37

Code: Select all

return {

    on = { timer = {'every minute '} }, 
    
    execute = function(domoticz)
    
        if domoticz.devices('My_External_IP') == nil then 
            domoticz.openURL('http://pi-1:8084/json.htm?type=createdevice&idx=16&sensorname=My_External_IP&sensormappedtype=0xF313')
        else    -- Because of the async nature of openURL the device is not yet created in the initial run so we need to wait at least one cycle
            domoticz.devices('My_External_IP').updateText(os.date("last update at %X on %A %d %B %Y"))
        end
    end
}


--  2018-02-22 01:29:00.757  dzVents: Info:  ------ Start external script: CheckExternalIP.lua:, trigger: every minute
--  2018-02-22 01:29:00.761  dzVents: Info:  ------ Finished CheckExternalIP.lua
--
--  Given the 4 mSecs this check and update takes on my PI-3,  I don't think you need to be overly worried about unnecessary overhead. 
--
-- 

Thanks. I tried the code. Get a warning on the domoticz.devices statement: device does not exist. This is as expected.
Then it tries to create the device, but that does not work. I modified the IP and port, no success...

manjh wrote: Saturday 24 February 2018 16:48

dannybloe wrote: Wednesday 21 February 2018 16:49 What you can do is create the device in the GUI and check the network tab to see what url is called. Then use that url from dzVents using openURL.

Perhaps a silly question: where can I find the "network tab"? I loked in Domoticz, cannot find it!

waaren wrote: Saturday 24 February 2018 17:53

manjh wrote: Saturday 24 February 2018 16:48

dannybloe wrote: Wednesday 21 February 2018 16:49 What you can do is create the device in the GUI and check the network tab to see what url is called. Then use that url from dzVents using openURL.

Perhaps a silly question: where can I find the "network tab"? I loked in Domoticz, cannot find it!

Network tab is a feature of your browser where you can inspect what is being sent.