zwavejs2mqtt

[EddyG]

But if you do not use that device, how do you control the Spirit?

[heggink]

I only use the thermostat device.and set the temperature. It's permanently in heat mode. If I don't want heat, I switch it to 12C...

Sent from my SM-G980F using Tapatalk

[Westcott]

Hi Heggink, same here.
I find the latest Spiritz to be a very reliable device when used this way.

[EddyG]

I now have complete control of the device via dzVents and the mode and setpoint devices.

[hestia]

As the mqtt autodiscovery is ongoing, I think that a point is still not working for my devices: Animation for RGBW Controller (Fibaro).
To get these animation you could set 6,7,8,9 or 10 in the 72 configuration field [95-112-0-72]

Screenshot 2021-11-08 204442.png (22.42 KiB) Viewed 2192 times

Screenshot 2021-11-08 204517.png (36.23 KiB) Viewed 2192 times

.
It's possible to do it with Home Assistant

Code: Select all

action:
  service: zwave.set_config_parameter
  data_template: {
    "node_id": 5,
    "parameter": 72,
    "value": 6,
    "size": 1
           }

I've tried do to it with mqtt from dz, but I could not figured out how to do it
Do you have any example of mqtt command so I could try again?

[jvdz]

Just look at what MQTT Topic & Payload HA sends when activating that option and do the same in your script.

[hestia]

I don't have HA
just read this on a HA forum
I don't know if it is easy to install HA just for this.
Perhaps sbdy already have HA and could have this look or any look of a configuration parameter?

[hestia]

I've installed HA...
In fact the communication between HA and zwavejs2mqtt is ws, no mqtt
The log in HA for the call is

Code: Select all

[Node 095] [REQ] [SendData]
│ transmit options: 0x25
│ callback id:      228
└─[ConfigurationCCSet]
                                      parameter #:      72
                                      reset to default: false
                                      value size:       1
                                      value format:     SignedInteger
                                      value:            6

I don't know if it's enough to make the call from dz to zwavejs

[jvdz]

I've installed HA...
In fact the communication between HA and zwavejs2mqtt is ws, no mqtt

That is their preferred communication method, but you can also use the MQTT AutoDiscover in HA!.
I use that to be able to compare the Domoticz behavior with HA when communicating to the different gateways.

[hestia]

As the mqtt autodiscovery is ongoing, I think that a point is still not working for my devices: Animation for RGBW Controller (Fibaro).
To get these animation you could set 6,7,8,9 or 10 in the 72 configuration field [95-112-0-72]

I've found how to do it with the help of the zwavejs2mqtt git discussions
Here is a script with the mqtt message

Code: Select all

local LED_SELECTOR_ID = 887 -- dummy selector to manage the LED with predefined choices:
local LED_ANIMATION_AURORA = 10
local LED_ANIMATION_RAINBOW = 20
local LED_ANIMATION_STORM = 30
local LED_ANIMATION_FIREPLACE = 40
local LED_ANIMATION_LAPD = 50
local LED_ANIMATION_PAUSE = 60

-- zwavejs2mqtt
local mqtt_prefix = "zwave"
local NODE_nodeId = 95
local NODE_commandClass = 112
local NODE_endpoint = 0
local NODE_property = 72


return {
     logging =   {   level   =   
                    --domoticz.LOG_ERROR, --select one to override system log level normal = LOG_ERROR
                    domoticz.LOG_DEBUG,
                    --domoticz.LOG_INFO,
                    --domoticz.LOG_ERROR,
                    --domoticz.LOG_FORCE
    },
    on = {
    	devices = {LED_SELECTOR_ID},
    },

    execute = function(dz, device)
    _G.logMarker =  dz.moduleLabel -- set logmarker to scriptname  
    --local LOG_LEVEL = dz.LOG_INFO  -- LOG_INFO, LOG_DEBUG, LOG_ERROR, LOG_FORCE  - normal = LOG_INFO
    local LOG_LEVEL = dz.LOG_DEBUG 

    dz.log("LED_SELECTOR " .. device.state .. " " .. tostring(device.level) .. " nValue: " .. device.nValue, LOG_LEVEL)

-----< BEG FUNCTIONS > ----------------------------------------------------------------------------------------

 	
    local function logWrite(str, level)  -- Support function for shorthand debug log statements
        if level == nil then
            level = LOG_LEVEL
        end
        dz.log(tostring(str), level)
    end
    

	local function setRGBWAnimation(rgbAnimation)
        local codeAnimation
		if rgbAnimation == LED_ANIMATION_PAUSE then
    		codeAnimation = 1
    	elseif rgbAnimation == LED_ANIMATION_FIREPLACE then
			codeAnimation = 6
		elseif rgbAnimation == LED_ANIMATION_STORM then
			codeAnimation = 7
		elseif rgbAnimation == LED_ANIMATION_RAINBOW then
			codeAnimation = 8
		elseif rgbAnimation == LED_ANIMATION_AURORA then
			codeAnimation = 9
		elseif rgbAnimation == LED_ANIMATION_LAPD then
			codeAnimation = 10
	    end

        local mqtt_prefix = "zwave"
        local NODE_nodeId = 95
        local NODE_commandClass = 112
        local NODE_endpoint = 0
        local NODE_property = 72
        local NODE_value = codeAnimation
        local suffix = "set"
        
        --mqttTopic = "zwave/95/112/0/72/set" 
        
        local mqttTopic = mqtt_prefix .. '/' .. NODE_nodeId .. '/' .. NODE_commandClass .. '/' .. NODE_endpoint .. '/' .. NODE_property .. '/' .. suffix
        
        local mosquitto_cmd = 'mosquitto_pub' ..' -t '.. mqttTopic .. ' -m '.. NODE_value

        os.execute (mosquitto_cmd)
        logWrite("mosquitto_cmd=" .. mosquitto_cmd)  
	end

   
-----< END FUNCTIONS > ----------------------------------------------------------------------------------------

		setRGBWAnimation(device.level)
		

end
}

mosquitto_pub -t zwave/95/112/0/72/set -m 8

[EddyG]

Sample script for the EUR_SPIRITZ Wall Radiator Thermostat.
Just to show how settings can be changed that don't have a Domoticz device like the lower setpoint.
I included the modes, although 3 of them can be set by a selector device. I enhanced zwabejs2mqtt with the 'Full' mode in the selector switch.
The values in the ZSetHigh and ZSetLow are the setpoint values.

Code: Select all

--local ZModeOff = 'mosquitto_pub -h 127.0.0.1 -t zwavejs2mqtt/Zolder_Thermostaat/64/0/mode/set -m "{\\"value\\": 0}"'
--local ZModeEco = 'mosquitto_pub -h 127.0.0.1 -t zwavejs2mqtt/Zolder_Thermostaat/64/0/mode/set -m "{\\"value\\": 1}"'
--local ZModeHeat = 'mosquitto_pub -h 127.0.0.1 -t zwavejs2mqtt/Zolder_Thermostaat/64/0/mode/set -m "{\\"value\\": 11}"'
--local ZModeFull = 'mosquitto_pub -h 127.0.0.1 -t zwavejs2mqtt/Zolder_Thermostaat/64/0/mode/set -m "{\\"value\\": 15}"'
local ZSetHigh = 'mosquitto_pub -h 127.0.0.1 -t zwavejs2mqtt/Zolder_Thermostaat/67/0/setpoint/1/set -m "{\\"value\\": 21}"'
local ZSetLow = 'mosquitto_pub -h 127.0.0.1 -t zwavejs2mqtt/Zolder_Thermostaat/67/0/setpoint/11/set -m "{\\"value\\": 17}"'

return {
        active = true,
--      active = false,

        on = {
                timer = { 'at 08:31',
                              'at 18:01' },
        },

        logging = {
                level = domoticz.LOG_INFO,
--              level = domoticz.LOG_DEBUG,
                marker = 'ZT'
        },


        execute = function(dz, item)
                                dz.executeShellCommand({ command = ZSetHigh })
                                dz.executeShellCommand({ command = ZSetLow })
                                if item.trigger == 'at 08:31' then
                                        dz.devices('Zolder Thermostaat Mode').switchSelector('Heat')
                                elseif item.trigger == 'at 18:01' then
                                        dz.devices('Zolder Thermostaat Mode').switchSelector('Eco')
                                end
        end
}

[ChriWo]

Hi EddyG,

Thank you for the sample. But I have one problem I get this Error:
2021-11-22 19:25:00.292 Error: dzVents: Error: (3.1.8) ZT: levelname Eco does not exist

But I have also have not figured out how to get to the 'Full' mode in the selector switch and the ZSetLow.

Can you please explain.

Thank you

[EddyG]

In the 'original' Auto-Discovery selector switch that level is called 'Energy Heat' I changed the levelname to Eco. It fits more what it does.
The Full mode is NOT implemented in the selector switch, if you need it in the script you can use the mosquitto_pub command.
ZSetLow is just a variable which includes a command to set the "Low" setpoint as in the script, because that is not included in the Auto-Discovery.
My script just 'resets' both setpoint twice a day to my default settings, just incase I changed those manually and forget to set them back.
B.t.w. the 'Full mode' is only active for 15 minutes after that the Thermostat sets it self back to the mode "Heat'

[hestia]

I've moved to mqtt auto discovery + zwavejs2mqtt last week.
So far it has been working mostly fine: better stability on some motion sensors than with OWZ: I was loosing them very often with OZW.

Some minors regressions: no kWh on some devices (I need to check the concerned models mostly Qubino), and the LED Controller

Sometimes the "connection" was lost between zwvajs2mqtt and domoticz: I don't know why and what happened exactly

What is good, it's a better understanding of the network, so I could make some changes to get it better.

For the RGBW Controller, the setColor method in DzVents no longer works, so I extend the script above https://domoticz.com/forum/viewtopic.ph ... 37#p282437 like this

Code: Select all

local LED_SELECTORS_ID = {887, 1114}    -- dummy selector to manage the LED with predefined choices:
local NODES_nodeId =    {               -- id in dz and relative zwave nodes
                            [887] = 95,
                            [1114] = 119
                        }


local RGBW_ORDER = -- animation and static color
    {   [0] =   {0, 0, 0, 0, 0, 0, 4},
        [10] =  {9},    -- Aurora
        [20] =  {8},    -- Rainbow
        [30] =  {7},    -- Storm
        [40] =  {6},    -- Fireplace
        [50] =  {10},   -- LAPD
        [60] =  {1},    -- Pause
		[70] =  {255, 255, 255, 255},   -- warm white !!!!
	    [80] =  {255, 165, 0, 50},      -- candle / bougie
        [90] =  {238, 130, 238, 0},	    -- violet
        [100] = {130, 65, 245, 0},      -- indigo
        [110] = {0, 0, 255, 0},         -- bleu
        [120] = {0, 128, 0, 0},         -- vert
        [130] = {255, 255, 0, 0},       -- jaune
        [140] = {255, 70, 0, 0},        -- orange
        [150] = {255, 0, 0, 0},         -- rouge
        [160] = {227, 137, 7, 251}      -- candle white
	}	

	-- static color
    -- setColor(r, g, b, ww):
   	-- r: Red level: 0-255
   	-- g: Green level: 0-255
   	-- b: Blue level: 0-255
   	-- ww: Warm white level: 0-255


-- zwavejs2mqtt
local mqtt_prefix = "zwave"

local NODE_nodeId

return {
     logging =   {   level   =   
                    --domoticz.LOG_ERROR, --select one to override system log level normal = LOG_ERROR
                    domoticz.LOG_DEBUG,
                    --domoticz.LOG_INFO,
                    --domoticz.LOG_ERROR,
                    --domoticz.LOG_FORCE
    },
    on = {
    	devices = LED_SELECTORS_ID,
    },

    execute = function(dz, device)
    _G.logMarker =  dz.moduleLabel -- set logmarker to scriptname  
    --local LOG_LEVEL = dz.LOG_INFO  -- LOG_INFO, LOG_DEBUG, LOG_ERROR, LOG_FORCE  - normal = LOG_INFO
    local LOG_LEVEL = dz.LOG_DEBUG 

    dz.log("LED_SELECTOR " .. device.state .. " " .. tostring(device.level) .. " nValue: " .. device.nValue, LOG_LEVEL)

-----< BEG FUNCTIONS > ----------------------------------------------------------------------------------------

 	
    local function logWrite(str, level)  -- Support function for shorthand debug log statements
        if level == nil then
            level = LOG_LEVEL
        end
        dz.log(tostring(str), level)
    end

	local function setZwavejs(p_NODE_commandClass, p_NODE_endpoint, p_NODE_property, p_NODE_value)

        local suffix = "set"
        local mqttTopic = mqtt_prefix .. '/' .. NODE_nodeId .. '/' .. p_NODE_commandClass .. '/' .. p_NODE_endpoint .. '/' .. p_NODE_property .. '/' .. suffix
        
        local mosquitto_cmd = 'mosquitto_pub' ..' -t '.. mqttTopic .. ' -m '.. p_NODE_value

        os.execute (mosquitto_cmd)
        logWrite("mosquitto_cmd=" .. mosquitto_cmd)  
	end
	

	local function RGBWAnimation(p_rgbAnimation)
	    dz.log("RGBWAnimation " .. p_rgbAnimation, LOG_LEVEL)
        local NODE_commandClass = 112
        local NODE_endpoint = 0
        local NODE_property = 72
        local NODE_value = p_rgbAnimation
    
        setZwavejs(NODE_commandClass, NODE_endpoint, NODE_property, NODE_value)
        
	end
	
	
	local function RGBWColor (p_red, p_green, p_blue, p_warmWhite)

	    dz.log("RGBWColor " .. p_red .. '  '.. p_green .. '  '.. p_blue .. ' ' .. p_warmWhite, LOG_LEVEL)

        local NODE_commandClass = 51
        local NODE_endpoint = 0
        local NODE_property = 'targetColor'
        local NODE_value = '{\\"value\\":{\\"warmWhite\\":' .. p_warmWhite .. ',\\"red\\":' .. p_red .. ',\\"green\\":' .. p_green .. ',\\"blue\\":' .. p_blue .. '}}' 
        
        setZwavejs(NODE_commandClass, NODE_endpoint, NODE_property, NODE_value)
        
	end
	

-----< END FUNCTIONS > ----------------------------------------------------------------------------------------

	logWrite(device.id .. ' ' .. device.level)
    local devLevel = device.level
    
    if  device.level == 0 or device.nValue == 0 then
        device.switchSelector(0).silent()
	    device.switchOff().silent()
	    devLevel = 0
	end

	if  devLevel ~= 170 then
	    NODE_nodeId = NODES_nodeId[device.id]
	    
	    logWrite('NODE_nodeId: ' .. NODE_nodeId)
  
     	local paramArray = RGBW_ORDER[devLevel]
    	
    	if paramArray[1] == nil then
    	    logWrite('Level: ' .. devLevel .. ' bad parameters', dz.LOG_ERROR)
    	elseif paramArray[2] == nil then -- animation
    	    RGBWAnimation(paramArray[1])
    	else
    	    RGBWColor (paramArray[1], paramArray[2], paramArray[3], paramArray[4])
        end
    end
    
end
}

[hestia]

Hi,
I've just had a discussion on the zwave-js / zwavejs2mqtt git and as a reply:

BTW as explained in docs I don't have any plan right now to keep mqtt discovery updated

https://zwave-js.github.io/zwavejs2mqtt ... stant-mqtt

The preferred method of integrating your Z-Wave components with Home Assistant is through the official Home Assistant Z-Wave JS integration, this because MQTT Discovery is limited compared to a native integration and Home Assistant updates frequently break it. Based on this I would NOT RECCOMMEND using MQTT Discovery, I don't plan to keep it maintained in the future.

so, I'm a bit surprised that the solution described here is presented as a future for zwave in domoticz, perhaps I've missed something, or a plan is ongoing...

[heggink]

Hi,
I've just had a discussion on the zwave-js / zwavejs2mqtt git and as a reply:

BTW as explained in docs I don't have any plan right now to keep mqtt discovery updated

https://zwave-js.github.io/zwavejs2mqtt ... stant-mqtt

The preferred method of integrating your Z-Wave components with Home Assistant is through the official Home Assistant Z-Wave JS integration, this because MQTT Discovery is limited compared to a native integration and Home Assistant updates frequently break it. Based on this I would NOT RECCOMMEND using MQTT Discovery, I don't plan to keep it maintained in the future.

so, I'm a bit surprised that the solution described here is presented as a future for zwave in domoticz, perhaps I've missed something, or a plan is ongoing...

Define future...

The thing is that OZW is pretty much a dead end street. Zwavejs is a much more workable and future proof solution. zwavejs2mqtt is based on zwavejs ('just' adds mqtt). The question then is "what's the most workable integration for domoticz". Zigbee2mqtt and zwavejs2mqtt both (still) support mqtt autodiscovery and only zwavejs2mqtt has announced that the developer has no plans to keep it maintained in the future but that does not mean that it's desupported. Zigbee2mqtt will continue to support mqtt so no problems there.

So then what? 2 options AFAICT:

• either "someone" implements native zwavejs integration into domoticz

• or "someone" takes over the mqtt side of zwavejs to keep it supported

Ultimately, this being open source, it all comes down to someone taking ownership for this hence my remark "define future". As long as this is open source, we all are responsible for keeping things maintained. Either that or we all switch to Home Assistant

[EddyG]

What also concerns me is "this because MQTT Discovery is limited compared to a native integration"
I wonder if someone has experience with https://github.com/zwave-js/node-red-contrib-zwave-js

[jvdz]

What also concerns me is "this because MQTT Discovery is limited compared to a native integration"

This is in comparison with the HomeAssistat addon integration so is all about HomeAssistant I think.

I wonder if someone has experience with https://github.com/zwave-js/node-red-contrib-zwave-js

Just wondering how having it in Nodered would help with the integration into Domoticz?

[EddyG]

Just wondering how having it in Nodered would help with the integration into Domoticz?

The backend is Zwave-js API and towards Domoticz I have full control.
I could leave out devices that I don't need and include devices that I need.
In the current solution with Auto-Discovery I am missing 1 of the setpoints in my thermostats, and the mode selector switch does not have all the settings.
I have a solution in my dzVents script to change the missing setpoint, and found a solution for the missing mode.
If that missing setpoint and missing mode is accessible via Zwave-js API and nodered then that could be a route to go.
And I just asked if someone has experience with it, just to get more info.

[hestia]

Define future...

The thing is that OZW is pretty much a dead end street. Zwavejs is a much more workable and future proof solution. zwavejs2mqtt is based on zwavejs ('just' adds mqtt). The question then is "what's the most workable integration for domoticz". Zigbee2mqtt and zwavejs2mqtt both (still) support mqtt autodiscovery and only zwavejs2mqtt has announced that the developer has no plans to keep it maintained in the future but that does not mean that it's desupported. Zigbee2mqtt will continue to support mqtt so no problems there.

So then what? 2 options AFAICT:

• either "someone" implements native zwavejs integration into domoticz

• or "someone" takes over the mqtt side of zwavejs to keep it supported

Ultimately, this being open source, it all comes down to someone taking ownership for this hence my remark "define future". As long as this is open source, we all are responsible for keeping things maintained. Either that or we all switch to Home Assistant

If you're aware of this, I'm half reassured!
Anyway I still have some simple switches that don't trigger dzvents and don't report their status (on/off)
So what is working well zwavejs doesn't automatically work well in dz