Domoticz

haryb wrote: ↑Monday 22 October 2018 9:58

Code: Select all

http.request('http://192.168.1.21:'..DomoticzPort..'/json.htm?type=command&param=addhardware&htype=15&port=1&name=MAX!&enabled=true')

192.168.1.21 this IP is correct ? I think should be my IP domoticz this same which is write in top variables ?

No, this is not correct, you should replace it with Umberto, maybe you should update your post to avoid others run into this problem as well.

Because of this (for you probably incorrect) IP address, the hardware is not created the first time the script is run, which will cause all kinds of subsequent errors. Let us know if it works again after this change!

P.S. Alternatively, you can also check out the Python plugin

I changed this hard IP to name variable my Domoticz IP but still i have the same error
I care about this script LUA.
Can anyone confirm that his last version of the script works 100% ?
Maybe I have some set in Domoticz first ? Or in my Cube ?

I don't know what happened but it start to work.
I restart Rasperry and add some Scen in Domoticz next I try run script and it's works
Thanks

Hi all,

Sorry for that issue. You were right, I didn't change all the IP's into a variable. This is fixed in the attachement.

I have 1 issue though: if I change the setpoint, it doesn't change it on the thermostats (no error or whatever). Is this also in your setup? If not… I have to restart my MAXCube (again). It used to work but suddenly stopped (and that part I didn't change ).

As for the lua script: don't put it in the domoticz scripts directory, that will probably not work. Create a crontab entry 'crontab -e', put the script (maxcron.lua and not maxcron.txt) in a 'MAX' directory (/home/pi/MAX) and create a 'logging' directory (/home/pi/logging).

crontab -e to open the crontab editor, paste the next two lines and save and close it again.

## MAX! control script
*/5 * * * * sudo lua /home/pi/MAX/maxcron.lua > /home/pi/logging/max.log

So, please help: mvzut, maybe you have an idea?

Is there any script to get only temperature from wall thermostats? I don't need to control MAX! system with domoticz, just want to receive temperature data.

The easiest way is to just install the plugin and disable all devices you don't use. In the settings of the plugin you can disable certain device types (e.g. valve percentagea). And the ones that are created by default (e.g. thermostats) can easily be set to "unused" in the settings > devices page of Domoticz.
Alternatively, you could create a stripped version of the plugin, but there are no real benefits in that except for more compact code. If you only want to read out temperatures, you need to read ALL device data from the Cube anyway and filter out the temperatures. The current plugin can do that just fine.

I did refresh one of my Raspberry Pi's which ran the installation via: https://www.domoticz.com/wiki/EQ3_MAX!
I used the latest Raspian Buster image because I read previous version will Crash Domoticz now.
Unfortunately I do get LUA errors and missing files. The installation as provided doesn't work for me.
Should I return to the Raspian stretch image or is there a solution for this?

The Lua version of this plugin is not actively maintained anymore. It may still work, but no guarantees. I strongly suggest to install the Python version, for instructions see https://github.com/mvzut/maxcube-Domoticz-plugin

Thanks!! Works fine, But recognize thse errors? How can I solve them?
2020-03-28 16:06:28.011 Error: (eQ-3 MAX! Gateway) 'onHeartbeat' failed 'TypeError':''>' not supported between instances of 'NoneType' and 'int''.
2020-03-28 16:06:28.012 Error: (eQ-3 MAX! Gateway) ----> Line 318 in '/home/pi/domoticz/plugins/MaxCube/plugin.py', function onHeartbeat
2020-03-28 16:06:28.012 Error: (eQ-3 MAX! Gateway) ----> Line 277 in '/home/pi/domoticz/plugins/MaxCube/plugin.py', function onHeartbeat
Ron

I did use the latest Buster lite images for my Raspberry. What else do I need to install for Python? What Plugins? And from where?
Just the basic install and reboot did not gave me the Eq3 Gateway hardware in Domotica setting hardware panel.
Followed this instruction:
From ( https://github.com/mvzut/maxcube-Domoti ... /README.md )
One of the easiest ways to install the plugin is by entering the following commands in a terminal to your machine running Domoticz (at least if this machine is a Raspberry Pi or something similar):
cd ~/domoticz/plugins
git clone https://github.com/mvzut/maxcube-Domoticz-plugin MaxCube
(or choose your own folder name instead of "MaxCube")
For updating from an existing version, type the following:
cd ~/domoticz/plugins/MaxCube (assuming you installed the plugin in this folder)
git reset --hard
git pull
After installing or updating the plugin, always restart Domoticz. You can find the plugin under Settings > Hardware. Activate the plugin by selecting it from the "Type" drop-down menu, fill in the parameters (explanation see below) and click "Add" (only for first-time installation).
............
After some extra Python plugins ( sudo apt install libpython3.x, python3-dev) and again reboot it did show up.
But now it looks like it fails after item 5 of 9 Eq3 devices I use. All radiator control in seperate rooms.
2020-03-28 18:24:50.052 (Gateway) Checking device '@Behandel kamer' in room 6
2020-03-28 18:24:50.053 Error: (Gateway) 'onHeartbeat' failed 'TypeError':''>' not supported between instances of 'NoneType' and 'int''.
2020-03-28 18:24:50.053 Error: (Gateway) ----> Line 318 in '/home/pi/domoticz/plugins/MaxCube/plugin.py', function onHeartbeat
2020-03-28 18:24:50.053 Error: (Gateway) ----> Line 277 in '/home/pi/domoticz/plugins/MaxCube/plugin.py', function onHeartbeat
No problem to start from scratch, but what shoudl I change.
Thanks Ron

A total reset of all Eq3 components did the trick. Deleted the hardware form Domoticz, did a reset of the Eq3-Gateway and added all the eQ3 devices and added it in Domoticz again. So no reset on Domoticz, only delete of the hardware items in setting / hardware. But a total reset of Eq3.

Sorry for the late reply. Glad you solved it.

Sometimes the hardware definition in the EQ3 Hub gets "messed up", I've had this once as well. In such cases it seems to report the available hardware in a format that the plugin doesn't expect. I'll try to make it more robust for such situations (no promises on timing . But reconfiguring the Hub also works.

By the way, it's a good habit to reboot your Cube once in a while. It seems it cannot always handle the frequent API communication, and in extreme cases this leads to a total reset of the Cube. In my experience, this happens much less frequent if you reboot it e.g. once a week. I have automated this via an automatic switch.