My HGI80 equivalent Domoticz setup without HGI80

[minthemerciless]

Now I can retrieve what I believe to be schedule data, my next challenge is to decode it. The first 14 nibbles look to be very similar to the payload of the request. Based on the Evohome_schedule_backup.py on GitHub, I think these 14 nibbles should be removed and the remaining data is the useful schedule data. Can anyone confirm this? It's the part at the start of the data that looks like '00200008000100'.

[DanD]

@minthemerciless

If you're using the Python code for schedule backup from my Github area, it decodes the messages and stores all the setpoints in a TXT file. You'll see from the Python code that the structure of these messages isn't straightforward to decode as the schedule information has been zlib compressed and the compressed stream split up into smaller blocks. The Python code puts each of the blocks back into a single string which can then be decompressed.

I'm not clear on what your overall objective is with the serial device you've constructed and Node Red setup? My Python schedule backup and restore scripts are just prototypes which demonstrate how the detailed schedule information can be requested from the controller, amended and then written back. I don't think anyone has implemented this functionality within the Node Red flows, but I may be wrong. I had planned to integrate this functionality into the Evohome Domoticz code, but haven't yet been able to progress this as it will require a significant update to the code.

Dan

[minthemerciless]

@DanD

I'm currently using the Python code as a template/ guide to implement a similar thing in Node Red. I would like to be able to implement the backup/ restore functionality through Node Red. This would allow for multiple schedules and automated modifications through Node Red. I am also not aware of anyone who has done this in Node Red.
I have not done much python coding so your script is a bit alien to me. Do you have a description of the packet structure?

Thanks again for the assistance.

Rob

[DanD]

@minthemerciless

Great, thanks for the explanation of what you're implementing. I'd misinterpreted your earlier message and just thought you were trying to get the basic functionality working in Node Red. You've probably already seen this info, but here are all the details available on the message structure which a couple of us worked on over on the Domoticz forum (look at the last 5-6 posts).

https://www.domoticz.com/forum/viewt...216168#p216168

I hope this is of some use.

Dan

[minthemerciless]

@DanD, very useful link, thanks. So I'm reasonably confident with my data. I now need a way of decompressing the data. On to the next stage.

[minthemerciless]

In the zlib version I have, there isn't a decompress method. Is this because it's a newer/older version? Is there a newer version of decompress? This is my data:

02688163606060606280800D2C0C0C3338206C98580A2B03C3 1D568418235C9D018A18BA3A26B83A7E460264317475CC58EC 65C6A28E05AE8E4301590C5D1D2B16F7B16251C786C55E3624 750028DB1331

Is someone able to decompress it to see if it's correct?

[DanD]

Your data string doesn't look right and I've tried decompressing with zlib via Python and it returns an error. Do the spaces indicate the end of the data from each message? If so, it looks like you're missing quite a bit of the payload. Here's an example set of messages from my system:

13/04/2017 18:55:06 045 RQ --- 30:060058 01:037519 --:------ 0404 007 00200008000100
13/04/2017 18:55:06 045 RP --- 01:037519 30:060058 --:------ 0404 048 0020000829010368816DCCC10D8030084051A0881DA8078F3D398303388B733A8A9A686CDACF8D1F7822FF1C2A5272C9
13/04/2017 18:55:09 045 RQ --- 30:060058 01:037519 --:------ 0404 007 00200008000203
13/04/2017 18:55:09 045 RP --- 01:037519 30:060058 --:------ 0404 048 002000082902034D92F36E79CE73DB161FEFD649A4468D6F57F0143C054FC133F00C3C03CFC04BE025F01278093C07CF
13/04/2017 18:55:10 045 RQ --- 30:060058 01:037519 --:------ 0404 007 00200008000303
13/04/2017 18:55:11 045 RP --- 01:037519 30:060058 --:------ 0404 038 002000081F0303C173F01CBCE9FD6DEF9EB6D9D87AEF697BE70578015E80178D77014CCE19AA

The 3 payloads which require concatenation and then decompressing (from the RP messages) are as follows:

68816DCCC10D8030084051A0881DA8078F3D398303388B733A8A9A686CDACF8D1F7822FF1C2A5272C9
4D92F36E79CE73DB161FEFD649A4468D6F57F0143C054FC133F00C3C03CFC04BE025F01278093C07CF
C173F01CBCE9FD6DEF9EB6D9D87AEF697BE70578015E80178D77014CCE19AA

[minthemerciless]

Your data string doesn't look right and I've tried decompressing with zlib via Python and it returns an error. Do the spaces indicate the end of the data from each message? If so, it looks like you're missing quite a bit of the payload. Here's an example set of messages from my system:

13/04/2017 18:55:06 045 RQ --- 30:060058 01:037519 --:------ 0404 007 00200008000100
13/04/2017 18:55:06 045 RP --- 01:037519 30:060058 --:------ 0404 048 0020000829010368816DCCC10D8030084051A0881DA8078F3D398303388B733A8A9A686CDACF8D1F7822FF1C2A5272C9
13/04/2017 18:55:09 045 RQ --- 30:060058 01:037519 --:------ 0404 007 00200008000203
13/04/2017 18:55:09 045 RP --- 01:037519 30:060058 --:------ 0404 048 002000082902034D92F36E79CE73DB161FEFD649A4468D6F57F0143C054FC133F00C3C03CFC04BE025F01278093C07CF
13/04/2017 18:55:10 045 RQ --- 30:060058 01:037519 --:------ 0404 007 00200008000303
13/04/2017 18:55:11 045 RP --- 01:037519 30:060058 --:------ 0404 038 002000081F0303C173F01CBCE9FD6DEF9EB6D9D87AEF697BE70578015E80178D77014CCE19AA

The 3 payloads which require concatenation and then decompressing (from the RP messages) are as follows:

68816DCCC10D8030084051A0881DA8078F3D398303388B733A8A9A686CDACF8D1F7822FF1C2A5272C9
4D92F36E79CE73DB161FEFD649A4468D6F57F0143C054FC133F00C3C03CFC04BE025F01278093C07CF
C173F01CBCE9FD6DEF9EB6D9D87AEF697BE70578015E80178D77014CCE19AA

@DanD

No, the spaces don't indicate the ends of messages. I think that was a copy paste issue. My raw messages look like this

045 RQ --- 18:730 01:172240 --:------ 0404 007 02200008000100
051 RP --- 01:172240 18:013589 --:------ 0404 048 02200008290102688163606060606280800D2C0C0C3338206C98580A2B03C31D568418235C9D018A18BA3A26B83A7E46
045 RQ --- 18:730 01:172240 --:------ 0404 007 02200008000202
050 RP --- 01:172240 18:013589 --:------ 0404 045 0220000826020264317475CC58EC65C6A28E05AE8E4301590C5D1D2B16F7B16251C786C55E3624750028DB1331

I think this looks right?

[DanD]

Yes, that pair of responses looks complete. Here are the 2 sections of the payloads which contain the schedule information:

688163606060606280800D2C0C0C3338206C98580A2B03C31D568418235C9D018A18BA3A26B83A7E46
64317475CC58EC65C6A28E05AE8E4301590C5D1D2B16F7B16251C786C55E3624750028DB1331

I tried concatenating and decompressing them with zlib and it worked OK and produced this output (after being formatted/interpreted by the Python code):

ZONE=3 DAY=1 TIME=20:00 TEMP=22.00
ZONE=3 DAY=1 TIME=23:00 TEMP=15.00
ZONE=3 DAY=2 TIME=20:00 TEMP=22.00
ZONE=3 DAY=2 TIME=23:00 TEMP=15.00
ZONE=3 DAY=3 TIME=20:00 TEMP=22.00
ZONE=3 DAY=3 TIME=23:00 TEMP=15.00
ZONE=3 DAY=4 TIME=20:00 TEMP=22.00
ZONE=3 DAY=4 TIME=23:00 TEMP=15.00
ZONE=3 DAY=5 TIME=20:00 TEMP=22.00
ZONE=3 DAY=5 TIME=23:00 TEMP=15.00
ZONE=3 DAY=6 TIME=20:00 TEMP=22.00
ZONE=3 DAY=6 TIME=23:00 TEMP=15.00
ZONE=3 DAY=7 TIME=20:00 TEMP=22.00
ZONE=3 DAY=7 TIME=23:00 TEMP=15.00

Does this schedule information match your zone?

[minthemerciless]

Yes, that pair of responses looks complete. Here are the 2 sections of the payloads which contain the schedule information:

688163606060606280800D2C0C0C3338206C98580A2B03C31D568418235C9D018A18BA3A26B83A7E46
64317475CC58EC65C6A28E05AE8E4301590C5D1D2B16F7B16251C786C55E3624750028DB1331

I tried concatenating and decompressing them with zlib and it worked OK and produced this output (after being formatted/interpreted by the Python code):

ZONE=3 DAY=1 TIME=20:00 TEMP=22.00
ZONE=3 DAY=1 TIME=23:00 TEMP=15.00
ZONE=3 DAY=2 TIME=20:00 TEMP=22.00
ZONE=3 DAY=2 TIME=23:00 TEMP=15.00
ZONE=3 DAY=3 TIME=20:00 TEMP=22.00
ZONE=3 DAY=3 TIME=23:00 TEMP=15.00
ZONE=3 DAY=4 TIME=20:00 TEMP=22.00
ZONE=3 DAY=4 TIME=23:00 TEMP=15.00
ZONE=3 DAY=5 TIME=20:00 TEMP=22.00
ZONE=3 DAY=5 TIME=23:00 TEMP=15.00
ZONE=3 DAY=6 TIME=20:00 TEMP=22.00
ZONE=3 DAY=6 TIME=23:00 TEMP=15.00
ZONE=3 DAY=7 TIME=20:00 TEMP=22.00
ZONE=3 DAY=7 TIME=23:00 TEMP=15.00

Does this schedule information match your zone?

@DanD

Yes, that is correct on to getting the decoding working.