Ok, thanks. Number of devices certanly effects to number of errors but I still have 3 devices that I'm testing system and I receive those errors.
Maybe I test external script before I add those 12 valves. If you're correct number of errors will otherwise increase alot.

Here is a version of the script that can be run outside of Domoticz using crontab: How this separate script effects previous Domoticz script devices? Will they remain the same? I want to try that but I don't want to mess old device readings. And that old script seems to work just fine (if you don't ...

I'm very interested to know how RF communication is made. They have achieved quite long battery time for valves. I'll try get my old 868MHz tranceiver to work. Maybe I can use it as sniffer and find out that communication.

By the way, there's a little trick you could use which will make it easier to find out which newly created Domoticz device belongs to which MAX! module: if you run the maxtest.lua script from the Wiki, it will show an address for each module. In the devices page of Domoticz, al new "Unknown ...

Now and then there has been warning about script runing over 10 secs but not too many. I remember you mentioned about it. You also run Domoticz in Raspberry, yes? What version? I have on my desk almost unused Raspberry 3. I noticed that it's quite lot faster than previous version 2B that I have for ...

Ok.
Now I have updated both script and Domoticz. Everything seems running well. Thanks again!

I changed setpoint and after that reported temperature returned from 25.5 decrees to value it should be.

Hold your horses! It just occurred to me that it will report 0 degrees whenever the valve doesn't communicate its temperature. That is probably not what you want. So I changed the code again. Plus I uncommented it already, since your explanation convinced me that more people might be interested ...

I'll report if something strange happens. What did you do to script about that 0 decree value? I' wonder should I update it. Everyting seems to be ok for now.

Are setpoint values updated in Domoticz only when they change? Last update was almost 1.5 hours ago and because of that those values are on red now. Ah, yes, very good point. To avoid unnecessary JSON API calls, I have chosen to only update them when they have changed. I changed the timeout warning ...

Hold your horses! It just occurred to me that it will report 0 degrees whenever the valve doesn't communicate its temperature. That is probably not what you want. So I changed the code again. Plus I uncommented it already, since your explanation convinced me that more people might be interested ...

Are setpoint values updated in Domoticz only when they change? Last update was almost 1.5 hours ago and because of that those values are on red now.

Great, I'll test it. I haven't received that error anymore. About that room temperatures without wall thermostat; I was thinking that get some times temperature is better than nothing to have some feedback that everyting is ok. It's important especially in winter times from rooms that are rarely ...

I was thinking why there was one additional setpoint but now both valve and wall thermostat setpoints are shown.
Only thing I can wish is that if there's no wall thermostat at the room is it possible to get temperature from thermostat valve (onlý for nice-to-have )

No I haven't but i'll try. I made a few changes, which could solve (some of) your problems, also the problem that thermostats were not created. It's in the post where I first shared the new script: https://www.domoticz.com/forum/viewtopic.php?f=34&t=841&p=103332#p103332 Can you try this? I tryed it ...

I changed the setpoint but it didn't change situation.

After that I removed MAX! and re-created it again, changed setpoints but only that same valve position appeared to list.

I just realised that you first have to change the setpoint of your thermostats/valves before they are created. Have you tried that? No I haven't but i'll try. By the way, did the original script (where you had to create your own devices) work for you? I had problems with wall temperature value. It ...

I did the same and one valve out of total 3 devices was found without any error messages. 2016-11-10 10:50:02.257 EventSystem: Fetching url... 2016-11-10 10:50:02.257 EventSystem: Script event triggered: /home/pi/domoticz/scripts/lua/script_time_max.lua 2016-11-10 10:50:03.264 (MAX!) General ...

I'm using port 8080.

I tryed that script and got 2016-11-10 07:55:01.524 Error: EventSystem: in /home/pi/domoticz/scripts/lua/script_time_max.lua: /home/pi/domoticz/scripts/lua/script_time_max.lua:158: attempt to concatenate global 'MAX_ID' (a nil value) Before trying script I updated my old version of json.lua. I have ...