Controlling Max! radiator thermostats with arduino or ESP

Begonnen von kennybl, 26 September 2020, 16:04:22

Vorheriges Thema - Nächstes Thema

kennybl

Hello,

I'm sorry if i ask stupid questions but i am new to this.

I have a few MAX! radiator thermostats. They are connected to a MAX! Cube and i can control the MAX! cube via a raspberry pi.

This works but the MAX! cube looses all its configuration multiple times a year. When it does i need to reconnect all thermostats before it will work again. I think this is a common problem.


I have read that i can make my own CUL with an arduino and a CC1101 868mhz transceiver.
I have followed some tutorials and i think i have flashed an arduino with nanoCUL (V 1.67 nanoCUL868) but  now i have no idea how to connect to the radiator thermostats.

Do i NEED to use the FHEM software? I am a software programmer by myself and i would like to control the thermostats without FHEM or at least i want to control it with my own ipad app.
Is this even possible? I was hoping to use an ESP32 with wifi to set and read more radiator thermostats but i am not sure if this is possible.

All the help is welcome and if you need more information i am happy to give.

Used tutorials:
https://www.hoek.mn/2016/01/20/making-your-own-cul-the-nanocul/
https://www.maredana.nl/max-thermostat-raspberry-arduino/


Thanks!

Wzut

oh yes Cube & Alzheimer is a pain in the ass .... but the solution is easy & cheap -> a CUL or a nanoCUL
To use it first you must define a CUL device with attr rfmode MAX ,example my Test CUL :

defmod CUL CUL /dev/serial/by-id/usb-busware.de_CUL868-if00 0000
attr CUL event-on-change-reading .*
attr CUL event-on-update-reading credit10ms
attr CUL maxid 14491a
attr CUL rfmode MAX
attr CUL room MAX
attr CUL stateFormat credit10ms
attr CUL verbose 3


second Step , define a CULMAX Device :
defmod cm CUL_MAX 14491a
attr cm IODev CUL
attr cm debug 1
attr cm event-on-change-reading .*
attr cm room MAX
attr cm verbose 3


on both devices are the very important MAXID -> 14491a , thats my ID your Cube uses a diffrent number. You can save a lot of work if you can find out this number !!

Do you already have FHEM running ? If yes please start not with CUL and CUL_MAX , start with MAXLAN first.
MAXLAN connects to your Cube and autocreate will define all your MAX devices in FHEM. After this you can see your MAXID in the Internals of your MAXLAN device. Use this ID for your CUL & CUL_MAX device and delete the MAXLAN device.
But only the MAXLAN device NOT your MAX devices !!!
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Thank you for your reply.

I have maid a nanoCul and i was testing FHEM software on windows. It can find COM3 but instead of initialized it says open without receiving values.
I can test it on a raspberry pi.

The only thing i don't know is how to communicate to FHEM without using the FHEM web gui. I have made an ipad app for my house to control lights, music, shutters etc, i want to be able to integrate the max thermostat into my app (using php, python, or whatever is needed).

Can this be done?

I have had this working with the cube but as i said, it likes to forget the configuration, it may be the alzheimer haha...

Wzut

Zitat von: kennybl am 26 September 2020, 17:19:56
Can this be done?
everthing can be done but we are here in the FHEM Board. I can help you with FHEM not with your own Software.
But you can run FHEM only for controlling your MAX devices  and if this is running you transfer the live data from FHEM to your Software and vice versa. Dont use Windows first, start with your Raspberry. FHEM & Windows is a litte bit special.
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Thank you,

I understand you don't know my software but i only wanted to know if something like that would be possible. Does FHEM has some kind of API or way to communicate via python, php etc?
I will install it on the raspberry and set it up the right way

Wzut

yes it can :) the normal way to connect from your software to FHEM is telnet, default Port 7072.
If want to use telnet please have also a look to the allowed device but please use the English Corner Board -> https://forum.fhem.de/index.php/board,52.0.html for none MAX questions. There are more and better people active with the right know-how
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Thank you very much for all your help, i am going to try it and will ask at the English board for more help!

Have a nice evening

kennybl

#7
Just one more question, i have installed FHEM on my raspberry pi and i have a connection with the nanoCul,

I need to add rooms, heaters etc, but i don't know how to start, i tried this command:

define sleepingroom_1 MAX HeatingThermostat 1XX8X0 but it doesn't seem to work, did i forgot something or am i doing things wrong. I used this tutorial: https://wiki.fhem.de/wiki/MAX!CubeMigrationToFHEM

PS: I haven't connected the MAX Cube now, do i need to? I think the nanoCUL replaces the MAX! Cube right?


EDIT:
I think it already works. I resetted the radiator thermostat, i run the command "set cm pairmode 60" and it added to FHEM! Now i need to figure out how to connect everything but it looks like it works way faster than the cube!

Great work!

Wzut

oh no , now you are on the hard way !
Please dont define CUL yet , define a MAXLAN device and autocreate will do the rest.
Please have a look at my first post.
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

#9
Thank you, i just read about your first post, i connected the MAX! Cube and connected via "define ml MAXLAN 192.168.178.2"

After that, all thermometers are already shown. I only cannot find my MAXID (in ml there are some id's but it is FUUID (a long guid), and a SERIAL but it starts with NEQ12....)

Do i need to start over and do it different?

Wzut

MAXIDs or MAX addresses are always six digits hex.
Have a look at the Internal addr in your MAXLAN (ml) device thats your friend.
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Would it be possible to give me a step by step explanation of what exactly to do?
Even Teamviewer would be an option but i understand if you don't want to do that ofcourse

Wzut

#12
Sorry I dont have software like Teamviewer or Skype running on my PC

If I understand your posts in Englisch Corner correctly, I think you are simply missing certain FHEM basics.
I would recommend to a German speaking user to read this first:
https://forum.fhem.de/index.php/topic,19621.0.html
https://wiki.fhem.de/wiki/Erste_Schritte_in_FHEM
Unfortunately i don't know any good english documentation but maybe Google can help you a litte bit to translate.

Anyway : You asked for a fresh FHEM and if it is running now please define first your MAXLAN device :
define ml MAXLAN 192.168.0.228:62910 30
no CUL or CUL_MAX device yet !

192.168.0.228 is my IP please use yor own.
After a few minutes autocreate has define all your existing MAX devices and you can do some things from FHEM , e.g. change the set temperature of a HT or WT.

If that's the case come back, I'll explain the next step to you


Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

#13
I did define ml MAXLAN 192.168.0.228:62910 30 with my own ip and I think it works so far, I got all the 8 thermostats that are installed in my house.



BTW: This is the log:


2020.10.11 16:30:28 0: Server started with 6 defined entities (fhem.pl:21056/2020-01-26 perl:5.028001 os:linux user:fhem pid:24150)
2020.10.11 17:48:42 3: Opening ml device 192.168.1.16:62910
2020.10.11 17:48:43 3: ml device opened
2020.10.11 17:48:43 2: MAXLAN_Parse: Cube thinks it is 11.10.2020 18:48
2020.10.11 17:48:43 2: MAXLAN_Parse: Time difference is 60 minutes\2020.10.11 17:48:43 2: autocreate: define MAX_1bccc1 MAX HeatingThermostat 1bccc1
2020.10.11 17:48:43 2: autocreate: define FileLog_MAX_1bccc1 FileLog ./log/MAX_1bccc1-%Y.log MAX_1bccc1
2020.10.11 17:48:43 2: autocreate: define MAX_1bd434 MAX HeatingThermostat 1bd434
2020.10.11 17:48:43 2: autocreate: define FileLog_MAX_1bd434 FileLog ./log/MAX_1bd434-%Y.log MAX_1bd434
2020.10.11 17:48:43 2: autocreate: define MAX_1bdd75 MAX HeatingThermostat 1bdd75
2020.10.11 17:48:43 2: autocreate: define FileLog_MAX_1bdd75 FileLog ./log/MAX_1bdd75-%Y.log MAX_1bdd75
2020.10.11 17:48:43 2: autocreate: define MAX_1bccc6 MAX HeatingThermostat 1bccc6
2020.10.11 17:48:43 2: autocreate: define FileLog_MAX_1bccc6 FileLog ./log/MAX_1bccc6-%Y.log MAX_1bccc6
2020.10.11 17:48:43 2: autocreate: define MAX_1bdd5d MAX HeatingThermostat 1bdd5d
2020.10.11 17:48:43 2: autocreate: define FileLog_MAX_1bdd5d FileLog ./log/MAX_1bdd5d-%Y.log MAX_1bdd5d
2020.10.11 17:48:43 2: autocreate: define MAX_1bdb83 MAX HeatingThermostat 1bdb83
2020.10.11 17:48:43 2: autocreate: define FileLog_MAX_1bdb83 FileLog ./log/MAX_1bdb83-%Y.log MAX_1bdb83
2020.10.11 17:48:43 2: autocreate: define MAX_1be7d4 MAX HeatingThermostat 1be7d4
2020.10.11 17:48:43 2: autocreate: define FileLog_MAX_1be7d4 FileLog ./log/MAX_1be7d4-%Y.log MAX_1be7d4
2020.10.11 17:48:43 2: autocreate: define MAX_1be048 MAX HeatingThermostat 1be048
2020.10.11 17:48:43 2: autocreate: define FileLog_MAX_1be048 FileLog ./log/MAX_1be048-%Y.log MAX_1be048
2020.10.11 17:48:43 3: MAX Cube is set to timezone CET-CEST



The time difference is 60 minutes, do I need to (and am I able to) change this?
also, changing temperature works but I see this in the log after updating 3 thermostat temperatures:


2020.10.11 17:55:26 2: MAX: Invalid value  for READING groupid on MAX_1bdb83. Forcing to 0
2020.10.11 17:55:36 2: MAX: Invalid value  for READING groupid on MAX_1bdd5d. Forcing to 0
2020.10.11 17:56:09 2: MAX: Invalid value  for READING groupid on MAX_1bccc6. Forcing to 0

Wzut

#14
yes you can change the time - the ml device has a attribute timezone but I think thats not important now because later FHEM is your clock master.


Zitat2020.10.11 17:55:26 2: MAX: Invalid value  for READING groupid on MAX_1bdb83. Forcing to 0
Thats a little bit strange. The Cube organizes all devices in rooms and each room has its own id. In FHEM is that the reading groupid and it must have a value, if not it is set to 0
Did you define rooms in your Cube ?
Valid Rooms are very important for the Cube because all devices of a room (group) are peered.
A peered devices is sending its messages direct to his peers and also to the cube.
Unfortunately it is not possible to read this (and other) informations back from a device !   

The next step is to find out the MAXID of your Cube -> look at the Internal addr of your ml device (6 digits hex).
Make a backup of all your MAX devices :
In FHEMWEB in the comandline field :
{ MAX_Save('all') }
if this fails you can go to each device and do the set saveConfig command.
It is very important to have a valid backup file of each device ( stored under logs/ )
After you have a saved config each device has a new get command show_saved_Config here you can look what you saved.

Now it is time to delete the ml device and save your fhem.cfg ( no red question mark ! ) and power down the Cube
Shutdown & restart FHEM

Now define your CUL and your CUL_MAX device -> my post from 26 September 2020, 17:15:50
Dont use 123456 as MAXID use your own !!!

After you have defined the CUL_MAX device go to each normal device and check the attribute IODev , normaly it points to your old MAXLAN device (ml)
Change this to your new CUL_MAX device cm. After that save and shutdown restart.

If after all something is not working only the FHEM Log file can tell you what the problem is. To get a log with more details and informations please set  the attribute verbose to 5 on your CUL_MAX device ( not global ! , global can be 3 or less )
Additionally you can set on all MAX devices the attribut debug to 1 than you will have more informations of the device in its readings.
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

#15
I rechecked the MAX Cube software and all devices are connected to groups, i reset the FHEM and connected the MAX_LAN again and still the same "group" error.
Do you think it helps if i reset the MAX Cube and create groups again and reset all thermostats?

I also noticed that i can change for example one thermostat, but changing another one doesn't do anything

Also, if i put this in the top input field { MAX_Save('all') }, i get this error: Undefined subroutine &main::MAX_Save called at (eval 30) line 1..
Did i do something wrong or is this the fail you mention?

Wzut

Maybe your Cube is now a litte bit confused because on your first attempts you did a factory reset on some devices and you paired them with the other MAXID 123456
Shure you cann reset and remove all devices from the Cube and start from early beginning. 
If you want to do so much work for yourself then you can start with CUL/CUL_MAX right away.
You definitely need a clean system i guess that's just not the case now.

ZitatI also noticed that i can change for example one thermostat, but changing another one doesn't do anything
let me guess : working is that one without the factory reset ?
This is your mess with the two different IDs

The Backup all command depents on the used 10_MAX version, no problem you can use the single backup (saveConfig) command on each device step by step. But none of this makes any sense unless you have a clean system.
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

I did a MAX Cube factory reset and all Thermostat reset as well, i did all again and i get the same error:


2020.10.12 16:52:13 3: Opening ml device 192.168.1.16:62910
2020.10.12 16:52:13 3: ml device opened
2020.10.12 16:52:13 2: MAXLAN_Parse: Cube thinks it is 12.10.2020 17:52
2020.10.12 16:52:13 2: MAXLAN_Parse: Time difference is 60 minutes
2020.10.12 16:52:14 2: autocreate: define MAX_1be7d4 MAX HeatingThermostat 1be7d4
2020.10.12 16:52:14 2: autocreate: define FileLog_MAX_1be7d4 FileLog ./log/MAX_1be7d4-%Y.log MAX_1be7d4
2020.10.12 16:52:14 3: MAX Cube is set to timezone CET-CEST
2020.10.12 16:53:17 2: MAX: Invalid value  for READING groupid on MAX_1be7d4. Forcing to 0


I am not sure what i do wrong here. Can't i make the rooms myself and connect the thermostats to this or is it impossible to do?

Wzut

#18
OK, I need more informations from your cube.
Set attribute verbose 5 on your ml device.
Delete all normal MAX devices except ml , save  & stop FHEM.
Change the 00_MAXLAN.pm and the 10_MAX.pm module with my attached new beta versions.
After the next reconnect of the Cube it will send a list of its devices and autocreate will do the rest.
If you cann see all your MAX devices in room MAX set verbose on ml back to 3
I need the hole log from start to now.
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

I did everything you said but still no rooms. Please tell me if I did something wrong
Here is the log file:
2020.10.12 18:29:09 5: MAXLAN_SimpleWrite:  l:
2020.10.12 18:29:09 5: Msg L:Cxvn1IgSGQ8pANsA
2020.10.12 18:29:09 5: len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 88, answer 0, unkbit (0,0,0)
2020.10.12 18:29:09 5: ml: dispatch MAX,1,ThermostatState,1be7d4,190f2900db00
2020.10.12 18:29:09 5: MAX_Parse MAX,1,ThermostatState,1be7d4,190f2900db00
2020.10.12 18:29:09 5: battery 0, rferror 0, panel 0, langateway 1, dstsetting 1, mode 1, valveposition 15 %, desiredTemperature 20.5, until , curTemp 21.9
2020.10.12 18:29:39 5: MAXLAN_SimpleWrite:  l:
2020.10.12 18:29:40 5: Msg L:Cxvn1IgSGQ8pANsA
2020.10.12 18:29:40 5: len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 88, answer 0, unkbit (0,0,0)
2020.10.12 18:29:40 2: Got List response for undefined device with addr 1be7d4
2020.10.12 18:30:10 5: MAXLAN_SimpleWrite:  l:
2020.10.12 18:30:10 5: Msg L:Cxvn1IgSGQ8pANsA
2020.10.12 18:30:10 5: len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 88, answer 0, unkbit (0,0,0)
2020.10.12 18:30:10 2: Got List response for undefined device with addr 1be7d4
2020.10.12 18:30:24 0: Server shutdown
2020.10.12 18:36:20 1: Including fhem.cfg
2020.10.12 18:36:20 3: WEB: port 8083 opened
2020.10.12 18:36:20 2: eventTypes: loaded 4 events from ./log/eventTypes.txt
2020.10.12 18:36:21 1: Including ./log/fhem.save
2020.10.12 18:36:21 1: usb create starting
2020.10.12 18:36:21 3: Probing ZWDongle device /dev/serial1
2020.10.12 18:36:21 3: Probing CUL device /dev/ttyAMA0
2020.10.12 18:36:22 3: Probing TCM_ESP3 device /dev/ttyAMA0
2020.10.12 18:36:22 3: Probing ZWDongle device /dev/ttyAMA0
2020.10.12 18:36:22 3: Probing SIGNALDuino device /dev/ttyAMA0
2020.10.12 18:36:22 3: Probing MYSENSORS device /dev/ttyAMA0
2020.10.12 18:36:22 3: Probing ArduCounter device /dev/ttyAMA0
2020.10.12 18:36:22 3: Probing ElsnerWS device /dev/ttyAMA0
2020.10.12 18:36:23 3: Probing FRM device /dev/ttyAMA0
2020.10.12 18:36:28 3: Probing TCM_ESP3 device /dev/ttyUSB0
2020.10.12 18:36:30 3: Probing TCM_ESP2 device /dev/ttyUSB0
2020.10.12 18:36:30 3: Probing FHZ device /dev/ttyUSB0
2020.10.12 18:36:30 3: Probing TRX device /dev/ttyUSB0
2020.10.12 18:36:30 3: Probing ZWDongle device /dev/ttyUSB0
2020.10.12 18:36:31 3: Probing SIGNALDuino device /dev/ttyUSB0
2020.10.12 18:36:31 3: Probing MYSENSORS device /dev/ttyUSB0
2020.10.12 18:36:31 3: Probing ArduCounter device /dev/ttyUSB0
2020.10.12 18:36:31 3: Probing ElsnerWS device /dev/ttyUSB0
2020.10.12 18:36:32 3: Probing FRM device /dev/ttyUSB0
2020.10.12 18:36:37 1: usb create end
2020.10.12 18:36:37 5: ml, Notify global , INITIALIZED
2020.10.12 18:36:37 3: Opening ml device 192.168.1.16:62910
2020.10.12 18:36:40 1: ml: Can't connect to 192.168.1.16:62910: Connection timed out
2020.10.12 18:36:40 2: ml, Could not connect
2020.10.12 18:36:40 5: ml, disconnect
2020.10.12 18:36:40 0: Featurelevel: 6
2020.10.12 18:36:40 0: Server started with 7 defined entities (fhem.pl:21056/2020-01-26 perl:5.028001 os:linux user:fhem pid:1052)
2020.10.12 18:37:10 3: Opening ml device 192.168.1.16:62910
2020.10.12 18:37:10 3: ml device opened
2020.10.12 18:37:11 5: ml, Parse: MSG H:NEQ1206430,172943,0113,00000000,25253f1a,00,32,140a0c,1325,03,0000
2020.10.12 18:37:11 2: ml, Cube thinks it is 12.10.2020 19:37
2020.10.12 18:37:11 2: ml, Time difference is 60 minutes
2020.10.12 18:37:11 5: ml, _parse_cmd_H: ip 25253f1a, duty cycle 0, freememory 32, clockset 3
2020.10.12 18:37:11 5: ml, Parse: MSG M:00,01,VgIBARBTbGFhcGthbWVyIEtlbnpvG+fUAQEb59RQRVExMDEzODY5DXRoZXJtb3N0YWF0XzEBAQ==
2020.10.12 18:37:11 5: ml, Parse: MSG C:172943,7RcpQwATAQBORVExMjA2NDMwAAsABEAAAAAAAAAAAP///////////////////////////wsABEAAAAAAAAAAQf///////////////////////////2h0dHA6Ly9tYXgtcG9ydGFsLmVxLTMuZGU6ODAvbG9va3VwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAENFVAAACgADAAAOEENFU1QAAwACAAAcIA==
2020.10.12 18:37:11 5: ml, _parse_cmd_C: len 237, addr 172943, devicetype 0, firmware 1, testresult 0, groupid 19, serial NEQ1206430
2020.10.12 18:37:11 5: ml, Parse: MSG C:1be7d4,0hvn1AEBEaFQRVExMDEzODY5KyE9CQcYAzAM/wBESFUIRSBFIEUgRSBFIEUgRSBFIEUgRSBFIERIVQhFIEUgRSBFIEUgRSBFIEUgRSBFIEUgREhUbETMVRRFIEUgRSBFIEUgRSBFIEUgRSBESFRsRMxVFEUgRSBFIEUgRSBFIEUgRSBFIERIVGxEzFUURSBFIEUgRSBFIEUgRSBFIEUgREhUbETMVRRFIEUgRSBFIEUgRSBFIEUgRSBESFRsRMxVFEUgRSBFIEUgRSBFIEUgRSBFIA==
2020.10.12 18:37:11 5: ml, _parse_cmd_C: len 210, addr 1be7d4, devicetype 1, firmware 17, testresult 161, groupid 1, serial PEQ1013869
2020.10.12 18:37:11 5: ml: dispatch MAX,1,define,1be7d4,HeatingThermostat,PEQ1013869,1
2020.10.12 18:37:11 5: MAX_Parse, MAX,1,define,1be7d4,HeatingThermostat,PEQ1013869,1
2020.10.12 18:37:11 3: MAX_PARSE, got message define for undefined device 1be7d4 type HeatingThermostat , autocreate is enabled
2020.10.12 18:37:11 2: autocreate: define MAX_1be7d4 MAX HeatingThermostat 1be7d4
2020.10.12 18:37:11 3: MAX_1be7d4, invalid or missing value  for READING groupid , forcing to 0
2020.10.12 18:37:11 3: MAX_1be7d4, invalid or missing value  for READING .weekProfile , forcing to 444855084520452045204520452045204520452045204520452044485508452045204520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc5514452045204520452045204520452045204520
2020.10.12 18:37:11 2: autocreate: define FileLog_MAX_1be7d4 FileLog ./log/MAX_1be7d4-%Y.log MAX_1be7d4
2020.10.12 18:37:11 5: ml, Notify global , UNDEFINED MAX_1be7d4 MAX HeatingThermostat 1be7d4|ATTR MAX_1be7d4 model HeatingThermostat|DEFINED MAX_1be7d4|DEFINED FileLog_MAX_1be7d4|SAVE
2020.10.12 18:37:11 5: ml, comfortemp 21.5, ecotemp 16.5, boostValve 80, boostDuration 1, tempoffset 0, minsetpointtemp off, maxsetpointtemp on, windowopentemp 12.0, windowopendur 15
2020.10.12 18:37:11 5: ml: dispatch MAX,1,HeatingThermostatConfig,1be7d4,16.5,21.5,on,off,444855084520452045204520452045204520452045204520452044485508452045204520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc5514452045204520452045204520452045204520,80,1,0,12.0,15,100,0,0,12
2020.10.12 18:37:11 5: MAX_Parse, MAX,1,HeatingThermostatConfig,1be7d4,16.5,21.5,on,off,444855084520452045204520452045204520452045204520452044485508452045204520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc5514452045204520452045204520452045204520,80,1,0,12.0,15,100,0,0,12
2020.10.12 18:37:11 5: ml: dispatch MAX,1,Error,1be7d4
2020.10.12 18:37:11 5: MAX_Parse, MAX,1,Error,1be7d4
2020.10.12 18:37:11 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:37:11 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:37:41 5: ml, SimpleWrite: l:
2020.10.12 18:37:41 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:37:41 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:38:11 5: ml, SimpleWrite: l:
2020.10.12 18:38:11 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:38:11 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:38:41 5: ml, SimpleWrite: l:
2020.10.12 18:38:41 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:38:41 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:39:11 5: ml, SimpleWrite: l:
2020.10.12 18:39:12 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:39:12 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:39:42 5: ml, SimpleWrite: l:
2020.10.12 18:39:42 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:39:42 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:40:12 5: ml, SimpleWrite: l:
2020.10.12 18:40:12 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:40:12 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:40:42 5: ml, SimpleWrite: l:
2020.10.12 18:40:42 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:40:42 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:41:12 5: ml, SimpleWrite: l:
2020.10.12 18:41:12 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:41:12 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:41:42 5: ml, SimpleWrite: l:
2020.10.12 18:41:42 5: ml, Parse: MSG L:Cxvn1AkAAAAAAAAA
2020.10.12 18:41:42 5: ml len 11, addr 1be7d4, initialized 0, valid 0, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:42:12 5: ml, SimpleWrite: l:
2020.10.12 18:42:12 5: ml, Parse: MSG L:Cxvn1AkSGRApAAAA
2020.10.12 18:42:12 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:42:12 5: ml: dispatch MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:42:12 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:42:42 5: ml, SimpleWrite: l:
2020.10.12 18:42:42 5: ml, Parse: MSG L:Cxvn1AkSGRApAAAA
2020.10.12 18:42:42 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:42:42 5: ml: dispatch MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:42:42 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:43:12 5: ml, SimpleWrite: l:
2020.10.12 18:43:12 5: ml, Parse: MSG L:Cxvn1AkSGRApAAAA
2020.10.12 18:43:12 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:43:12 5: ml: dispatch MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:43:12 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:43:31 2: AttrTemplates: got 127 entries
2020.10.12 18:43:42 5: ml, SimpleWrite: l:
2020.10.12 18:43:42 5: ml, Parse: MSG L:Cxvn1AkSGRApAAAA
2020.10.12 18:43:42 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:43:42 5: ml: dispatch MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:43:42 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:44:12 5: ml, SimpleWrite: l:
2020.10.12 18:44:13 5: ml, Parse: MSG L:Cxvn1AkSGRApAAAA
2020.10.12 18:44:13 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 18:44:13 5: ml: dispatch MAX,1,ThermostatState,1be7d4,191029000000
2020.10.12 18:44:13 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,191029000000

Wzut

OK, strange :
2020.10.12 18:37:11 5: ml, _parse_cmd_C: len 210, addr 1be7d4, devicetype 1, firmware 17, testresult 161, groupid 1, serial PEQ1013869
2020.10.12 18:37:11 5: ml: dispatch MAX,1,define,1be7d4,HeatingThermostat,PEQ1013869,1 <- here it is
2020.10.12 18:37:11 5: MAX_Parse, MAX,1,define,1be7d4,HeatingThermostat,PEQ1013869,1  <- here it is
2020.10.12 18:37:11 3: MAX_PARSE, got message define for undefined device 1be7d4 type HeatingThermostat , autocreate is enabled

in my FHEM ml fills the readings serial and groupid after autocreate has defined them.
If you set reconnect on the ml device usually the cube is sending the list again. Are the readings groupid than set to 1 ?

by the way , your MAXID  : 172943

Please post a list of MAX_1be7d4
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

I did a "reconnect" on the ml and I got this log I think:


2020.10.12 19:08:17 5: ml, SimpleWrite: l:
2020.10.12 19:08:17 5: ml, Parse: MSG L:Cxvn1AkSGRApANoA
2020.10.12 19:08:17 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 19:08:17 5: ml: dispatch MAX,1,ThermostatState,1be7d4,19102900da00
2020.10.12 19:08:17 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,19102900da00
2020.10.12 19:08:22 5: ml, disconnect
2020.10.12 19:08:22 3: Opening ml device 192.168.1.16:62910
2020.10.12 19:08:23 3: ml device opened
2020.10.12 19:08:23 5: ml, Parse: MSG H:NEQ1206430,172943,0113,00000000,2452fab8,03,32,140a0c,1408,03,0000
2020.10.12 19:08:23 2: ml, Cube thinks it is 12.10.2020 20:8
2020.10.12 19:08:23 2: ml, Time difference is 60 minutes
2020.10.12 19:08:23 5: ml, _parse_cmd_H: ip 2452fab8, duty cycle 3, freememory 32, clockset 3
2020.10.12 19:08:23 5: ml, Parse: MSG M:00,01,VgIBARBTbGFhcGthbWVyIEtlbnpvG+fUAQEb59RQRVExMDEzODY5DXRoZXJtb3N0YWF0XzEBAQ==
2020.10.12 19:08:23 5: ml, Parse: MSG C:172943,7RcpQwATAQBORVExMjA2NDMwAAsABEAAAAAAAAAAAP///////////////////////////wsABEAAAAAAAAAAQf///////////////////////////2h0dHA6Ly9tYXgtcG9ydGFsLmVxLTMuZGU6ODAvbG9va3VwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAENFVAAACgADAAAOEENFU1QAAwACAAAcIA==
2020.10.12 19:08:23 5: ml, _parse_cmd_C: len 237, addr 172943, devicetype 0, firmware 1, testresult 0, groupid 19, serial NEQ1206430
2020.10.12 19:08:23 5: ml, Parse: MSG C:1be7d4,0hvn1AEBEaFQRVExMDEzODY5KyE9CQcYAzAM/wBESFUIRSBFIEUgRSBFIEUgRSBFIEUgRSBFIERIVQhFIEUgRSBFIEUgRSBFIEUgRSBFIEUgREhUbETMVRRFIEUgRSBFIEUgRSBFIEUgRSBESFRsRMxVFEUgRSBFIEUgRSBFIEUgRSBFIERIVGxEzFUURSBFIEUgRSBFIEUgRSBFIEUgREhUbETMVRRFIEUgRSBFIEUgRSBFIEUgRSBESFRsRMxVFEUgRSBFIEUgRSBFIEUgRSBFIA==
2020.10.12 19:08:23 5: ml, _parse_cmd_C: len 210, addr 1be7d4, devicetype 1, firmware 17, testresult 161, groupid 1, serial PEQ1013869
2020.10.12 19:08:23 5: ml: dispatch MAX,1,define,1be7d4,HeatingThermostat,PEQ1013869,1
2020.10.12 19:08:23 5: MAX_Parse, MAX,1,define,1be7d4,HeatingThermostat,PEQ1013869,1
2020.10.12 19:08:23 5: ml, comfortemp 21.5, ecotemp 16.5, boostValve 80, boostDuration 1, tempoffset 0, minsetpointtemp off, maxsetpointtemp on, windowopentemp 12.0, windowopendur 15
2020.10.12 19:08:23 5: ml: dispatch MAX,1,HeatingThermostatConfig,1be7d4,16.5,21.5,on,off,444855084520452045204520452045204520452045204520452044485508452045204520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc5514452045204520452045204520452045204520,80,1,0,12.0,15,100,0,0,12
2020.10.12 19:08:23 5: MAX_Parse, MAX,1,HeatingThermostatConfig,1be7d4,16.5,21.5,on,off,444855084520452045204520452045204520452045204520452044485508452045204520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc55144520452045204520452045204520452045204448546c44cc5514452045204520452045204520452045204520,80,1,0,12.0,15,100,0,0,12
2020.10.12 19:08:23 5: ml: dispatch MAX,1,Error,1be7d4
2020.10.12 19:08:23 5: MAX_Parse, MAX,1,Error,1be7d4
2020.10.12 19:08:23 5: ml, Parse: MSG L:Cxvn1AkSGRApANoA
2020.10.12 19:08:23 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 19:08:23 5: ml: dispatch MAX,1,ThermostatState,1be7d4,19102900da00
2020.10.12 19:08:23 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,19102900da00
2020.10.12 19:09:43 5: ml, SimpleWrite: s:AARAAAAAG+fUAWo=
2020.10.12 19:09:43 5: ml, Parse: MSG S:03,0,31
2020.10.12 19:09:43 5: ml, _parse_cmd_S: dutycyle 3, freememoryslot 49
2020.10.12 19:09:43 5: ml: dispatch MAX,1,AckSetTemperature,1be7d4,21.0
2020.10.12 19:09:43 5: MAX_Parse, MAX,1,AckSetTemperature,1be7d4,21.0
2020.10.12 19:09:46 5: ml, SimpleWrite: l:
2020.10.12 19:09:47 5: ml, Parse: MSG L:Cxvn1AkSGRAqAAAA
2020.10.12 19:09:47 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 19:09:47 5: ml: dispatch MAX,1,ThermostatState,1be7d4,19102a000000
2020.10.12 19:09:47 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,19102a000000
2020.10.12 19:10:17 5: ml, SimpleWrite: l:
2020.10.12 19:10:17 5: ml, Parse: MSG L:Cxvn1AkSGRAqANoA
2020.10.12 19:10:17 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 19:10:17 5: ml: dispatch MAX,1,ThermostatState,1be7d4,19102a00da00
2020.10.12 19:10:17 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,19102a00da00
2020.10.12 19:10:47 5: ml, SimpleWrite: l:
2020.10.12 19:10:47 5: ml, Parse: MSG L:Cxvn1AkSGRAqANoA
2020.10.12 19:10:47 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 19:10:47 5: ml: dispatch MAX,1,ThermostatState,1be7d4,19102a00da00
2020.10.12 19:10:47 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,19102a00da00


After that I changed a temperature and I got this log:

2020.10.12 19:11:17 5: ml, SimpleWrite: l:
2020.10.12 19:11:17 5: ml, Parse: MSG L:Cxvn1AkSGRAqANoA
2020.10.12 19:11:17 5: ml len 11, addr 1be7d4, initialized 1, valid 1, error 0, errCmd 09, answer 0, unkbit (0,0,0)
2020.10.12 19:11:17 5: ml: dispatch MAX,1,ThermostatState,1be7d4,19102a00da00
2020.10.12 19:11:17 5: MAX_Parse, MAX,1,ThermostatState,1be7d4,19102a00da00




list MAX_1be7d4:

Internals:
   CFGFN     
   DEF        HeatingThermostat 1be7d4
   FUUID      5f849447-f33f-c04f-6188-676d2c890d04a284
   FVERSION   10_MAX.pm:?-s21928/2020-05-13
   IODev      ml
   LASTInputDev ml
   MSGCNT     62
   NAME       MAX_1be7d4
   NOTIFYDEV  global
   NR         20
   NTFY_ORDER 50-MAX_1be7d4
   STATE      21.0
   SVN        21928
   TYPE       MAX
   TimeSlot   -1
   addr       1be7d4
   devtype    1
   ml_MSGCNT  62
   ml_TIME    2020-10-12 19:10:17
   type       HeatingThermostat
   READINGS:
     2020-10-12 19:08:23   PairedTo        172943
     2020-10-12 19:08:23   SerialNr        PEQ1013869
     2020-10-12 19:10:17   battery         ok
     2020-10-12 19:10:17   batteryState    ok
     2020-10-12 19:08:23   boostDuration   5
     2020-10-12 19:08:23   boostValveposition 80
     2020-10-12 19:08:23   comfortTemperature 21.5
     2020-10-12 19:08:23   decalcification Sat 12:00
     2020-10-12 19:10:17   desiredTemperature 21.0
     2020-10-12 19:10:17   deviation       0.8
     2020-10-12 19:08:23   ecoTemperature  16.5
     2020-10-12 18:37:11   error           invalid or missing value  for READING .weekProfile
     2020-10-12 19:08:23   firmware        1.1
     2020-10-12 19:10:17   gateway         1
     2020-10-12 19:08:23   groupid         1
     2020-10-12 19:09:43   lastcmd         desiredTemperature 21.0
     2020-10-12 19:08:23   maxValveSetting 100
     2020-10-12 19:08:23   maximumTemperature on
     2020-10-12 19:08:23   measurementOffset 0.0
     2020-10-12 19:08:23   minimumTemperature off
     2020-10-12 19:10:17   mode            manual
     2020-10-12 19:10:17   panel           unlocked
     2020-10-12 19:10:17   rferror         0
     2020-10-12 19:10:17   state           21.0
     2020-10-12 19:10:17   temperature     21.8
     2020-10-12 19:08:23   testresult      161
     2020-10-12 19:08:23   valveOffset     0
     2020-10-12 19:10:17   valveposition   16
     2020-10-12 19:08:23   weekprofile-0-Sat-temp 17.0 °C  /  21.0 °C  /  17.0 °C
     2020-10-12 19:08:23   weekprofile-0-Sat-time 00:00-06:00  /  06:00-22:00  /  22:00-24:00
     2020-10-12 19:08:23   weekprofile-1-Sun-temp 17.0 °C  /  21.0 °C  /  17.0 °C
     2020-10-12 19:08:23   weekprofile-1-Sun-time 00:00-06:00  /  06:00-22:00  /  22:00-24:00
     2020-10-12 19:08:23   weekprofile-2-Mon-temp 17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C
     2020-10-12 19:08:23   weekprofile-2-Mon-time 00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-24:00
     2020-10-12 19:08:23   weekprofile-3-Tue-temp 17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C
     2020-10-12 19:08:23   weekprofile-3-Tue-time 00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-24:00
     2020-10-12 19:08:23   weekprofile-4-Wed-temp 17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C
     2020-10-12 19:08:23   weekprofile-4-Wed-time 00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-24:00
     2020-10-12 19:08:23   weekprofile-5-Thu-temp 17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C
     2020-10-12 19:08:23   weekprofile-5-Thu-time 00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-24:00
     2020-10-12 19:08:23   weekprofile-6-Fri-temp 17.0 °C  /  21.0 °C  /  17.0 °C  /  21.0 °C  /  17.0 °C
     2020-10-12 19:08:23   weekprofile-6-Fri-time 00:00-06:00  /  06:00-09:00  /  09:00-17:00  /  17:00-23:00  /  23:00-24:00
     2020-10-12 19:08:23   windowOpenDuration 15
     2020-10-12 19:08:23   windowOpenTemperature 12.0
   helper:
     dt         21.0
     myday      2
Attributes:
   IODev      ml
   model      HeatingThermostat
   room       MAX

Wzut

perfect ! the reading groupid is set to 1 :) Now you can do the rest
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Thanks a lot! I go to add all thermostats to groups and then go on with your steps

kennybl

I now have connected all my thermostats and they have room: MAX

I want to save all the configs with the set saveConfig, but when I press "set", I get this safari error:

Safari cannot open the page

I tried to enter a value in the input field but also without, the error stays the same

Wzut

any lines in the log file ?
do you have files that end with .max in /opt/fhem/logs ?
has the device a new Reading called lastConfigSave ? 
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

#26
I don't have a /opt/fhem/logs folder, I do have a /opt/fhem/log folder so I guess it needs to be that one.

I have a list of files but they all end with .log, .save or .txt.
I do have all the MAX_1bc....-2020.log but I'm not sure if you mean this?

There is no lastConfigSave value for the thermostat


Edit: After i try to set the saveConfig i see fhem crashes and after 20 seconds it is restarted again (Both Mac & Windows)

Wzut

Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Zitat von: Wzut am 17 Oktober 2020, 13:44:32
nice and how should I help if you hide the corresponding log?

i don't hide the config haha, i just don't know what config you need to have since i don't have a .max file?

Wzut

I dont talk about configs , I want to see the part of your normal FHEM Log file when FHEM has crashed,
usually the cause of the crash is logged there.   
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

I'm sorry, all of this is really new to me.

Here are the lines from the log from the moment i press the "saveConfig" set

Undefined subroutine &main::Logdir called at ./FHEM/10_MAX.pm line 896.
2020.10.17 16:08:40 1: Including fhem.cfg
2020.10.17 16:08:40 3: WEB: port 8083 opened
2020.10.17 16:08:40 2: eventTypes: loaded 138 events from ./log/eventTypes.txt
2020.10.17 16:08:41 1: Including ./log/fhem.save
2020.10.17 16:08:41 1: usb create starting
2020.10.17 16:08:41 3: Probing ZWDongle device /dev/serial1
2020.10.17 16:08:41 3: Probing CUL device /dev/ttyAMA0
2020.10.17 16:08:41 3: Probing TCM_ESP3 device /dev/ttyAMA0
2020.10.17 16:08:41 3: Probing ZWDongle device /dev/ttyAMA0
2020.10.17 16:08:41 3: Probing SIGNALDuino device /dev/ttyAMA0
2020.10.17 16:08:42 3: Probing MYSENSORS device /dev/ttyAMA0
2020.10.17 16:08:42 3: Probing ArduCounter device /dev/ttyAMA0
2020.10.17 16:08:42 3: Probing ElsnerWS device /dev/ttyAMA0
2020.10.17 16:08:43 3: Probing FRM device /dev/ttyAMA0
2020.10.17 16:08:48 3: Probing TCM_ESP3 device /dev/ttyUSB0
2020.10.17 16:08:48 3: Probing TCM_ESP2 device /dev/ttyUSB0
2020.10.17 16:08:48 3: Probing FHZ device /dev/ttyUSB0
2020.10.17 16:08:48 3: Probing TRX device /dev/ttyUSB0
2020.10.17 16:08:49 3: Probing ZWDongle device /dev/ttyUSB0
2020.10.17 16:08:49 3: Probing SIGNALDuino device /dev/ttyUSB0
2020.10.17 16:08:49 3: Probing MYSENSORS device /dev/ttyUSB0
2020.10.17 16:08:50 3: Probing ArduCounter device /dev/ttyUSB0
2020.10.17 16:08:50 3: Probing ElsnerWS device /dev/ttyUSB0
2020.10.17 16:08:51 3: Probing FRM device /dev/ttyUSB0
2020.10.17 16:08:56 1: usb create end
2020.10.17 16:08:56 3: Opening ml device 192.168.1.16:62910
2020.10.17 16:08:56 3: ml device opened
2020.10.17 16:08:56 2: ml, Cube thinks it is 17.10.2020 17:8
2020.10.17 16:08:56 2: ml, Time difference is 60 minutes
2020.10.17 16:08:57 0: Featurelevel: 6
2020.10.17 16:08:57 0: Server started with 24 defined entities (fhem.pl:21056/2020-01-26 perl:5.028001 os:linux user:fhem pid:8944)

Wzut

OK, there is a problem with your 10_MAX.pm. , sorry -> Undefined subroutine &main::Logdir

Please try my newest beta version from here -> https://forum.fhem.de/index.php/topic,115018.0.html
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Thank you, i updated the 3 files in the /opt/fhem/FHEM folder but still the same problem (i stopped Fhem and started Fhem after updating the files)

Wzut

exact the same error text in the log ?
What value shows the Internal SVN on a MAX device ?
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

no, now it is

2020.10.17 18:34:12 2: AttrTemplates: got 127 entries
Undefined subroutine &main::Logdir called at ./FHEM/10_MAX.pm line 903.


SVN: BETA

Wzut

Thats very, very strange ... Logdir() is a simple function in fhem.pl
Ok, I made now a version for you where Logdir is defined in 10_MAX.pm , but I dont understand why the normal version is not working in your installation
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Thanks, I could save the .max file and I see it is created in /opt/fhem/log, but then I try to get show_savedConfig, I get no value in the select dropdown and the message I get is:

Can't open ./log/ .max: No such file or directory


Wzut

Do you realy have a file  .max ? There is the devicename missing and the get dropdown cant show that.
How did you make this ? A normal set saveConfig with a empty text field creates a file with the device name and .max
e.g. MAX_0f0a0b.max If you type in a text this text will be used as name for the file  -> test  creates test.max
A full backup of all devices can be done in the FHEMWEB textfield with the command
{ FHEM::MAX::MAX_Save() }
after this look in the log file which devices are backuped
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

Yes, I saved all 8 thermostats and I have 8 files (MAX_1b____.max)

I made the file via opening the thermostat, select "set MAX_1b____ [saveConfig] [    ]".
I first tried to set a name as "backup" but since that didn't seem to work I left it empty. After that I saw there where 2 files, backup.max and MAX_1b____.max) but when I try to get the saved config it gives that message.


I also did
{ FHEM::MAX::MAX_Save() }, the log shows:


2020.10.18 13:32:29 3: MAX_1bccc6, configSaved to ./log/MAX_1bccc6.max
2020.10.18 13:32:29 3: MAX_1be048, configSaved to ./log/MAX_1be048.max
2020.10.18 13:32:29 3: MAX_1bdd5d, configSaved to ./log/MAX_1bdd5d.max
2020.10.18 13:32:29 3: MAX_1bdb83, configSaved to ./log/MAX_1bdb83.max
2020.10.18 13:32:29 3: MAX_1bccc1, configSaved to ./log/MAX_1bccc1.max
2020.10.18 13:32:29 3: MAX_1bdd75, configSaved to ./log/MAX_1bdd75.max
2020.10.18 13:32:29 3: MAX_1bd434, configSaved to ./log/MAX_1bd434.max
2020.10.18 13:32:29 3: MAX_1be7d4, configSaved to ./log/MAX_1be7d4.max


But still no value in the dropdown after "show_savedConfig"

Wzut

The list for the dropdown is created by a function from 01_FHEMWEB and this is working with %L
%L points normal to your current logdir. Logdir() is not find in your installation so I think something is wrong but I dont know what yet.

Did you change or set the attributes global logdir or global modpath ?
normaly logdir is not set and modpath points to .

Did you look in one of your .max files ? are lines in ?


Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

kennybl

I didn't change any attributes for lodger or global mod path, at least nog on purpose.

I checked the .max files and they have all the values from the thermostat, can I continue with doing the next steps for removing the MAX Cube?

Wzut

Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher

betateilchen

#42
@kennybl

Zitat2020.10.11 16:30:28 0: Server started with 6 defined entities (fhem.pl:21056/2020-01-26 perl:5.028001 os:linux user:fhem pid:24150)

Your FHEM installation is in an age of 9 months, current version is #22987
You should do an update as soon as possible, before going on and to prevent further waste of time.
-----------------------
Formuliere die Aufgabe möglichst einfach und
setze die Lösung richtig um - dann wird es auch funktionieren.
-----------------------
Lesen gefährdet die Unwissenheit!

kennybl

#43
Thank you, strange, I can't remember what tutorial I used to install FHEM but I thought I used the FHEM wiki.

How can I upgrade to version 22987?

edit:
I did use the "update" command and now I am at 22935.
I do get the list of savedconfigs but I am not sure if the version still needs to be updated

kennybl

I think I got everything working, I removed the maxlan and did all the steps.

I can change the radiator thermostat a few times, after the 4th or 5th time within 30 seconds I still got this message:
cm, CUL not enough credit! credit10ms is 15, but we need 110. Waiting 95 seconds. Currently 1 messages are waiting to be sent
is this normal?

Wzut

yes , if you want to do too much in short time.
Please ask Google about Maximum Duty Cycle Limit on 868Mhz , e.g. -> https://www.thethingsnetwork.org/docs/lorawan/duty-cycle.html
Maintainer der Module: MAX, MPD, UbiquitiMP, UbiquitiOut, SIP, BEOK, readingsWatcher