Domoticz

oasisnl wrote:As I look at the manual with this box it responses to the max cube commands when one of the valves/thermostats has a heating request. I'm not sure if the device will be added in domoticz using the provided scripts. But since domoticz is controlling the thermostats and valves and then the cube sends an signal to the boiler contoller there may be no need to see the controller in domoticz. Downsite is that you won't be able to check the status of the boiler within domoticz. Overall I guess it will be able to control your boiler, maybe not directly from domoticz but through the values of the thermostats and valves which are controlled by domoticz.
This is just my opinion, also myself just starting with max! and actually still looking for a good boiler controller solution.

The communication protocol with the Cube has been reverse engineered, and a good description can be found at https://github.com/Bouni/max-cube-protocol. This is the basis for the scripts and plug-ins that exist for various home automation systems. I can't seem to find any reference to the boiler switch after a quick scan, but maybe others have time to search better. If it's not documented here, the chance that we can control it is low.

I personally check the percentage of my valves with a Domoticz script, and use a Z-wave switch to control my boiler if there is heat demand.

Thanks both - seems I may have been too eager ordering the MAX! boiler control as it doesn't look like I'll be able to include it in Domoticz.
I'd like to get the boiler control within Domoticz, so that I can remotely switch on / use Alexa to control heating.

I already have a 'normal' electronic timeswitch for my boiler which has an RF roomstat to switch on when the room is too cold.
Ultimately I'd like to replace that with the ability to have the boiler fired when ANY room (or 'n' rooms) with a MAX value require heat, all controllable from Domoticz.
The max actuator seemed like it would do the trick, but stupidly I didn't check it would work in Domoticz first!

I'm not 100% familiar with boiler wiring, as I've not looked at mine yet, but I guess the wiring is essentially [Timeswitch]----[RF Roomstat Reciever]-----[Boiler Call to Heat]

If so, I'm assuming an option would be to replace the roomstat reciever with a Z-Wave / RF Boiler Relay, and then turn the timeswitch to always on ?

Greatful of any recommendations here..

I've got it working using a simpel NO NC relais with RF .

https://nl.aliexpress.com/item/433Mhz-U ... 0.0.HuorBl

Downsite of this relais is it only shows an on status in domoticz.

using this thread i've solved that
http://www.domoticz.com/forum/viewtopic ... 28&t=19226

alltough this treat is for a door contact, i've used the same way. the relais creates 2 devices ( one = boiler on, two = boiler off) using a dummy switch and the two scripts in this threat I now have a dummy boiler switch with on of status.
I've used blocky to create a script . if all valves are below 10% set boiler switch off if any valve is above 10% set boilerswitch on.

Hope this helps a bit.

Thanks Oasisnl.

I'd like to avoid any 'home made' solution for the boiler control and use something off the shelf (mainly for reliability and safety).

I found a horstmann controls iqe cp318 Z-Wave timeswitch which looked like it would fit my needs, but a bit of googling suggests that Domoticz isn't able to turn the boiler on, or set the current mode using the Z-Wave - only configure the setpoint for the included thermostat.

Is anyone aware of a reasonably priced off the shelf Z-Wave compatible timeswitch that works nicely with Domoticz?

It would be nice to have a 'traditional' timeswitch handling the basic heating, and then override it via Z-Wave when needed..

A bit off-topic for Max!, but the Horstmann SCSC17 Thermostat is Z-wave and programmable.
Pair it with a Horstmann ASR-ZW Thermostat Receiver (boiler switch)
I have 2 working well for me.
If Domoticz is down, the SCS17 can still control the ASR-ZW directly with basic day/time programming.

Does anyone have a script to turn of heating in a room when a window is open?

I have windowcontacts , use them for alarm triggering, they send separate open / close status ( not from Max!) . Idea would be something like:
when the window is open for more then 1 minute and if valves in the room are open ( so there is a heating demand, >10% or so) turn of heating for that room ( set valve termporary to 0% or set setpoint of thermostat to a 5 degrees). When window is closed restore to latest ( or actual timer/desired ) setting so that heating starts again.


thanks again for any help.

Hi
Recently launched MAX! through crontab. everything worked fine, Until the Domotics upgrade to version 3.8770, the data in the system was no longer updated. When starting the script, maxscript produces errors.

pi@pi:~/domoticz/scripts/lua $ lua maxscript.lua
lua: /home/pi/domoticz/scripts/lua/JSON.lua:660: html passed to JSON:decode(): <html><head><title>Unauthorized</title></head><body><h1>401 Unauthorized</h1></body></html>
stack traceback:
[C]: in function 'assert'
/home/pi/domoticz/scripts/lua/JSON.lua:660: in function 'onDecodeOfHTMLError'
/home/pi/domoticz/scripts/lua/JSON.lua:975: in function 'decode'
maxscript.lua:42: in function 'get_MAX_ID'
maxscript.lua:228: in main chunk
[C]: in ?

And when you run the test maxtest produces such errors

pi@pi:~/domoticz $ lua maxtest2.lua
Rooms
-----
Kuhnia/Salon 117169
Spalnia/Megamaja 126EF6

Devices
-------
RadiatorSalon2-Rad 117169
PultSalon-Stat 125708
PultSpalnia-Stat 125826
RadiatorSalon-Rad 1170D5
WindSensorSpalnia-Sens 0FAFD8
Eco Switch 01BBE0
WindSensorSalon-Sens 0FAFF2
RadiatorSpalnia-Rad 126EF6

Device status
-------------
lua: maxtest2.lua:112: attempt to concatenate global 'setpoint' (a nil value)
stack traceback:
maxtest2.lua:112: in function 'maxCmd_L'
maxtest2.lua:145: in main chunk
[C]: in ?

What could be the problem?

what can be wrong with the script I don't know, but version 3.8770 is still a beta version. If you don't intent to run beta you can adjust this in settings, system updates and then select the option "stabile"
Don't know really how to undo the update, probably using restore from backup should work?

In general, installed again raspbbery PI OS, and installed a stable version 3.8153 of the domotix, but the error remained

pi@pi:~/domoticz $ lua maxtest.lua
Rooms
-----
Kuhnia/Salon 117169
Spalnia/Megamaja 126EF6

Devices
-------
RadiatorSpalnia-Rad 126EF6
WindSensorSalon-Sens 0FAFF2
RadiatorSalon2-Rad 117169
PultSalon-Stat 125708
Eco Switch 01BBE0
WindSensorSpalnia-Sens 0FAFD8
PultSpalnia-Stat 125826
RadiatorSalon-Rad 1170D5

Device status
-------------
lua: maxtest.lua:115: attempt to concatenate global 'setpoint' (a nil value)
stack traceback:
maxtest.lua:115: in function 'maxCmd_L'
maxtest.lua:148: in main chunk
[C]: in ?


What am I doing wrong?????

I googled around a bit.
ON page 25 of this topic this issue as mentioned and could have something to do with lua5.1 to lua5.2
and on page 15 this error is mentioned, here the solution was to delete the window sensors.

I don't know if window sensors are fully supported in the latest scripts ? can anyone confirm if these are supported?

Maybe you can test by deleting the window sensors in domoticz and in the cube?

but I worked with window sensors, but I'll try.

By your advice deleted Window sensors. To Regret nothing has changed, What am I doing wrong?

pi@pi:~/domoticz $ lua maxtest.lua
Rooms
-----
Spalnia/Megamaja 126EF6
Kuhnia/Salon 117169

Devices
-------
Eco Switch 01BBE0
RadiatorSpalnia-Rad 126EF6
RadiatorSalon-Rad 1170D5
PultSpalnia-Stat 125826
PultSalon-Stat 125708
RadiatorSalon2-Rad 117169

Device status
-------------
lua: maxtest.lua:112: attempt to concatenate global 'setpoint' (a nil value)
stack traceback:
maxtest.lua:112: in function 'maxCmd_L'
maxtest.lua:145: in main chunk
[C]: in ?

are you sure you are using the latest scritp?
what script are you using, crontab or domoticz?
I recently had some troubles and I was pointed out by the forum members that I used an old script.
There are several scripts around.


The crontab version is described here:
http://www.domoticz.com/forum/viewtopic ... 05#p104705
The Domoticz script is here:
https://www.domoticz.com/wiki/EQ3_MAX!#Max_Script

I now use the crontab script instead of the domoticz one. It creates all devices in domoticz etc. You only need to create a cronjob.
See page 30 and later of this topic. mwzut user was off great help to me,

maybe try changing the scripts. it isn't to difficult to do.

I installed the stubble version 3.8153. I reinstalled the whole system without updates. I use a crontab

thats the domoticz version number.

did you also look at page 25 off this topic where people mention same problem as you which has to do with lua 5.1 vs. 5.2. Did you also install all of those components on your pi ?

I did everything I advised the errors remained. I started the Domotics script from the Wiki, I spread the error:

2017-12-05 21:10:00.786 Error: EventSystem: in /home/pi/domoticz/scripts/lua/script_time_max.lua: /home/pi/domoticz/scripts/lua/script_time_max.lua:129: attempt to compare nil with number

I'd like to be able to set a Thermostat to auto from domoticz. Is that possible ? If so, how ?

Thanks

You can use the timer settings in the settings of domoticz to set different setpoints on different times of day/weeks etc.
I use this on my thermostats in domoticz , works great, no need to use the automatic settings of cube / max which can only be controlled with the max cube app.
Maybe this also works for you ?

That's not exactly what I was looking for. I'd like to continue relying on the cube and being able to switch one/all thermostats to auto in one click. So, again, has the code to do that particular request to the cube been developed ? and if so, how can I trigger it ?

thanks

Well programmers can someone help find the cause of the problem with the function 'maxCmd_L'

Vitalij wrote: ↑Monday 04 December 2017 22:23 By your advice deleted Window sensors. To Regret nothing has changed, What am I doing wrong?

pi@pi:~/domoticz $ lua maxtest.lua
Rooms
-----
Spalnia/Megamaja 126EF6
Kuhnia/Salon 117169

Devices
-------
Eco Switch 01BBE0
RadiatorSpalnia-Rad 126EF6
RadiatorSalon-Rad 1170D5
PultSpalnia-Stat 125826
PultSalon-Stat 125708
RadiatorSalon2-Rad 117169

Device status
-------------
lua: maxtest.lua:112: attempt to concatenate global 'setpoint' (a nil value)
stack traceback:
maxtest.lua:112: in function 'maxCmd_L'
maxtest.lua:145: in main chunk
[C]: in ?

Studying this problem, I found in this thread a preliminary code http://www.domoticz.com/forum/viewtopic ... 160#p86922
that does not give an osibox, where this function 'maxCmd_L' gives values

pi@pi:~/domoticz $ lua x0.lua
M=00,01,VgICAQtLdWhuaWFTYWxvbhFxaQIPU3BhbG5pYU1lZ2FtYWphEm72CAERcWlMRVExMTM1Mjg5ElJhZGlhdG9yU2Fsb24yLVJhZAEDElcITUVRMTEyODYzMQ5QdWx0U2Fsb24tU3RhdAEFAbvgSkVRMDMwODQ0OAlFY29Td2l0Y2gAARFw1UxFUTExMzUwMjURUmFkaWF0b3JTYWxvbi1SYWQBAhJu9k1FUTEyODM3MjQTUmFkaWF0b3JTcGFsbmlhLVJhZAIDElgmTUVRMTEyODM0MRBQdWx0U3BhbG5pYS1TdGF0AgQPr/JMRVExMTEzNjAzEVdpbmRvd0t1aG5pYS1TZW5zAQQPr9hMRVExMTA3ODk5EldpbmRvd1NwYWxuaWEtU2VucwIB
L=BgG74AkAAAYPr/IJEhAMElcICRIYBC4AAADiBg+v2AkSEAsRcNUJEhhkLgAAAAwSWCYJEhgEHgAAAM0LEXFpCRIYZC4AAAALEm72CRIYAB4AAAA=
Len=7 Adr=01BBE0 batt=OK mode=Auto bst=0
Len=7 Adr=0FAFF2 batt=OK mode=Auto bst=0
Len=13 Adr=125708 batt=OK mode=Auto bst=1
Thermostat setpoint=23 Temp=22.6
Len=7 Adr=0FAFD8 batt=OK mode=Auto bst=0
Len=12 Adr=1170D5 batt=OK mode=Auto bst=1
Valve pos=100 Setpoint=23 Temp=0
Len=13 Adr=125826 batt=OK mode=Auto bst=1
Thermostat setpoint=15 Temp=20.5
Len=12 Adr=117169 batt=OK mode=Auto bst=1
Valve pos=100 Setpoint=23 Temp=0
Len=12 Adr=126EF6 batt=OK mode=Auto bst=1
Valve pos=0 Setpoint=15 Temp=0