MAX thermostat parameters update

English Forums Devices
#1

Hello everyone,
I’m always trying to make my Homegear + HomeAssistant implementation work.
Currently I have connected only one thermostat; it had already been programmed with the MAX software for a weekly scheduling.
I see the following problems:

  • when I set a weekly program from the homegear admin interface and select “save on device” I do not see traffic to the outgoing or incoming CUL so I suspect that in reality nothing is saved on the thermostat.
    The update of the current temperature, as of the set one, does not change at the programmed times; I can only view the changes by restarting the homegear service or only when there is a change of valve position.
    Is this normal behavior? When there is a change of temperature setting at a programmed time, should the thermostat transmit something?
    This using MAXube was displayed regularly …
    Thanks for your help.
    Michele
#2

@micha: Can you say something about this?

#3

Hi all,

we’re using a flashed Max!Cube, so I cannot test with a CUL. But here this is working. The only problem is that the DutyCycle is reached really often :confused:

@arkimede could you post a log? Loglevel 4 would be nice :wink:

– Micha

#4

Hi @Micha, how i can attach a file (log) ? it’s too large to paste here…

#5

Just the excerpt of setting the parameters is enough. You can post it as an attachment here.

#6

I hope this is the right cut…

02/17/20 17:47:45.827 Script Engine Server: Response: 
(void)
02/17/20 17:47:45.829 Script Engine Server: Info: Client number 0 is calling RPC method: scriptOutput
(String) {"result":"success"}
(Boolean) 0
02/17/20 17:47:45.829 Script Engine Server: Response: 
(void)
02/17/20 17:47:45.832 Info: Script with id 8 finished with exit code 0
02/17/20 17:47:45.832 RPC Server (Port 2001): Debug: Connection to client number 50 closed.
02/17/20 17:47:45.833 RPC Server (Port 2001): Debug: Connection to client number 50 closed (1).
02/17/20 17:47:45.965 MAX packet received (MH-MAX-CUL, RSSI: 0x42): 0E4202021A2A0717C97A000118222A
02/17/20 17:47:45.965 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:45.965 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:45.965 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:45.965 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:46.066 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 1943001017C97A1A2A07000548485460489654A848CC55144920
02/17/20 17:47:47.181 MAX packet received (MH-MAX-CUL, RSSI: 0x43): 0E4302021A2A0717C97A000118222A
02/17/20 17:47:47.181 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:47.182 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:47.182 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:47.182 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:47.282 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 1944001017C97A1A2A07000648485460489654A848CC55144920
02/17/20 17:47:48.000 IPC Server: Info: Client number 0 is calling RPC method: lifetick Parameters:
02/17/20 17:47:48.001 IPC Server: Response: 
(Boolean) 1
02/17/20 17:47:48.397 MAX packet received (MH-MAX-CUL, RSSI: 0x42): 0E4402021A2A0717C97A000118222A
02/17/20 17:47:48.397 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:48.397 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:48.397 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:48.397 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:48.497 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 1745001017C97A1A2A070010792079207920792079207920
02/17/20 17:47:49.597 MAX packet received (MH-MAX-CUL, RSSI: 0x44): 0E4502021A2A0717C97A000118222A
02/17/20 17:47:49.597 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:49.597 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:49.598 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:49.598 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:49.698 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 1746001017C97A1A2A070011792079207920792079207920
02/17/20 17:47:50.797 MAX packet received (MH-MAX-CUL, RSSI: 0x44): 0E4602021A2A0717C97A000118222A
02/17/20 17:47:50.797 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:50.797 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:50.797 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:50.797 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:50.899 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 1747001017C97A1A2A070012792079207920792079207920
02/17/20 17:47:51.997 MAX packet received (MH-MAX-CUL, RSSI: 0x44): 0E4702021A2A0717C97A000118222A
02/17/20 17:47:51.998 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:51.998 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:51.998 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:51.998 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:52.099 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 1748001017C97A1A2A070013792079207920792079207920
02/17/20 17:47:53.198 MAX packet received (MH-MAX-CUL, RSSI: 0x43): 0E4802021A2A0717C97A000118222A
02/17/20 17:47:53.198 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:53.198 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:53.198 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:53.198 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:53.300 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 1749001017C97A1A2A070014792079207920792079207920
02/17/20 17:47:54.397 MAX packet received (MH-MAX-CUL, RSSI: 0x45): 0E4902021A2A0717C97A000118222A
02/17/20 17:47:54.397 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:54.397 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:54.397 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:54.397 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:54.500 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 174A001017C97A1A2A070015792079207920792079207920
02/17/20 17:47:55.613 MAX packet received (MH-MAX-CUL, RSSI: 0x43): 0E4A02021A2A0717C97A000118222A
02/17/20 17:47:55.613 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:55.613 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:55.613 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:55.613 Module MAX: Queue 0 is empty. Pushing pending queue...
02/17/20 17:47:55.714 Module MAX: CUL "MH-MAX-CUL": Info: Sending (MH-MAX-CUL, WOR: yes): 174B001017C97A1A2A070016792079207920792079207920
02/17/20 17:47:56.813 MAX packet received (MH-MAX-CUL, RSSI: 0x45): 0E4B02021A2A0717C97A000118222A
02/17/20 17:47:56.813 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:56.813 Module MAX: Message now at front: Message type: 0x2 Message subtype: 0xFFFFFFFF
02/17/20 17:47:56.813 Module MAX: Popping from MAX! queue: 0
02/17/20 17:47:56.813 Module MAX: Info: Queue 0 is empty and there are no pending queues.
02/17/20 17:47:56.854 Module MAX: Debug: Deleting queue 0 for peer with address 0x1A2A07
02/17/20 17:47:56.854 Module MAX: Releasing SAVEPOINT PacketQueue1714695_0
02/17/20 17:48:19.293 MAX packet received (MH-MAX-CUL, RSSI: 0x35): 0CF50442192B031A29F1002ACE
02/17/20 17:48:19.340 MAX packet received (MH-MAX-CUL, RSSI: 0x43): 0EF502021A29F1192B03000119642A
02/17/20 17:48:20.260 RPC Server (Port 2001): Info: Connection from ::1:60526 accepted. Client number: 51
02/17/20 17:48:20.260 RPC Server (Port 2001): Info: RPC server client id for client number 51 is: 42
02/17/20 17:48:20.260 RPC Server (Port 2001): Listening for incoming packets from client number 51.
02/17/20 17:48:20.261 RPC Server (Port 2001): Debug: Packet received: 504F5354202F5250433220485454502F312E310D0A486F73743A206C6F63616C686F73743A323030310D0A417574686F72697A6174696F6E3A20426173696320614739745A57646C595849364D3031685A4768686448526C63673D3D0D0A4163636570742D456E636F64696E673A20677A69700D0A436F6E74656E742D547970653A20746578742F786D6C0D0A557365722D4167656E743A20507974686F6E2D786D6C7270632F332E370D0A436F6E74656E742D4C656E6774683A203232390D0A0D0A
02/17/20 17:48:20.261 RPC Server (Port 2001): Debug: Packet received: 3C3F786D6C2076657273696F6E3D27312E30273F3E0A3C6D6574686F6443616C6C3E0A3C6D6574686F644E616D653E67657456616C75653C2F6D6574686F644E616D653E0A3C706172616D733E0A3C706172616D3E0A3C76616C75653E3C737472696E673E4F4551303934333031353A313C2F737472696E673E3C2F76616C75653E0A3C2F706172616D3E0A3C706172616D3E0A3C76616C75653E3C737472696E673E5345545F54454D50455241545552453C2F737472696E673E3C2F76616C75653E0A3C2F706172616D3E0A3C2F706172616D733E0A3C2F6D6574686F6443616C6C3E0A
02/17/20 17:48:20.261 RPC Server (Port 2001): Info: Client number 51 is calling RPC method: getValue (1) Parameters:
(String) OEQ0943015:1
(String) SET_TEMPERATURE
02/17/20 17:48:20.261 RPC Server (Port 2001): Response: 
(Float) 18
02/17/20 17:48:20.261 RPC Server (Port 2001): Response packet: HTTP/1.1 200 OK
Connection: close
Content-Type: text/xml
Content-Length: 122
#7

Please use the edit functions of the forum, you could edit your post :slight_smile:
grafik

#8

sorry, why?

#9

Sorry, I meant please format your post containing the log.

Why? For better readability, of course :wink:

#10

hope now it’s right :smiley:

1 Like
#11

Hi @arkimede,

sorry for the late reply. It looks like the parameters are pushed correctly to the device. Maybe there is an error in the putParamset() that comes bofore the posted block. Could you please repost the log starting a little earlier with the putParamset().

Cheers,

Sathya

#12

Hi @sathya,
no problem, this issue fixed some times ago by you :slight_smile:
See other post…

If you want help, now… we have to fix another problem with setup of MAX thermostat parameters…
when you go in the admin ui, page “edit configuration parameters for thermostat…” you can see channel 0 (week program) and channel 2 (empty) but not channel 1/3 where are other useful parameters…
Moreover, will be more it would also be highly appreciated to be able to configure the coupling between a valve and a wall thermostat or a window switch through the user interface.
I asked both of these questions some time ago and someone replied (I don’t remember who) for the first problem (configuration channels) was a bug but the person who had to deal with it had no way or time; for the second, which was not implemented.
If this is so, I would like to ask you if you can tell me which project or file I should look at to try to fix the problem by myswlf; I would also really like to understand how to configure a development environment (what IDE? Compiler? etc.)
Thank you very much
Michele

#13

Hi @arkimede,

The reason is that those parameters are variables and not configuration parameters. Variables are currently not settable in the admin UI.

I will talk to @Micha about it.

@Micha?

Cheers,

Sathya

#14

Hi there,

as mentioned somewhere before it’s not possible yet, but direct coupling is a point on my roadmap. It’s a very special Homematic-thing, so it wasn’t that hight prority so far.

@arkimede the Admin UI is based on symfony. You could have a look at Controller/Admin/Inventory/DeviceController.php and Model/Admin/HomegearDevice.php. I’m using plain VSCode, and a virtual machine with a homgear nightly installed :wink:

– Micha

#15

I use
https://github.com/hobbyquaker/homematic-manager
for the stuff which isn’t configurable by Homegear.

#16

Thank you all for your kind answers!
I’ll see what I can do :slight_smile:
good job
Michele

#17

HI @Larx, unfortunately my devices are MAX and not Homematic…

#18

Hi @sathya, there are certainly configurable parameters in channels 1 and 3 - decalcification, vacancy time, night temperature, open window temperature … Things of this kind; always the person I spoke with some time ago, showed me the configuration page of the Homematic devices and these parameters, such as channels 1 and 3, were correctly displayed; I think it’s a bug on the MAX page…
– edit
this is reference to the thread


– second edit
the channel that should be viewed / edited is number 1 instead of 2 which is empty; that’s the bug …

Cheers
Michele

#19

Mine too. Doesn’t matter, Homegear exposes the devices like Homematic devices.

#20

Hi @Larx,
let me better understand…
Do I have to configure Homematic-manager to connect to homegear? Do I have to specify the Homegear address (e.g. 192.168.1.2:2001) when it asks me for the configuration?
test
Thank you
Michele