maxwellhadley / node-red-contrib-rfxcom

node-RED nodes to access an RFXtrx433 transceiver
BSD 2-Clause "Simplified" License
22 stars 13 forks source link

Please add support for new feature in Firmware 1028 #126

Closed jag100UK closed 1 year ago

jag100UK commented 1 year ago

I've been in contact with Birt from RFXCom and he's released a firmware update to support the "Unit" for Blinds 1 T11 ASP.

My device is a RFXtrx433 Type 1, but he's release the update for RFXtrx433E too.

Previously the RFXCom treated communication with the blind on unit ID 1 as "ALL", so if you have multiple blinds operated by the same remote, you could only control the blind on Unit ID 1.

RXFXCom now correctly interprets and transmits the Unit ID, so I can address each blind individually using RFXmgr.

It would be great if we can add support for this in node-red..

Currently, the payload doesn't include any Unit information in the address.. For example:

BLINDS_T11/0xA169A4 : msg.payload : string[4]
"Open"

Perhaps the address could be extended to include the unit? For example For all Units:- BLINDS_T11/0xA169A400

For Unit ID 1 BLINDS_T11/0xA169A401

I can supply more outputs from RFXmgr if it helps coding

Many thanks

John

maxwellhadley commented 1 year ago

I've been very busy, but I am looking at this now, along with some other issues. But don't hold your breath!

jag100UK commented 1 year ago

No problem, Max.

I’d be happy to help with any testing, if you need a volunteer.

Thanks

John

Sent from my iPhone

On 27 Dec 2022, at 20:57, Max Hadley @.***> wrote:



I've been very busy, but I am looking at this now, along with some other issues. But don't hold your breath!

— Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaxwellhadley%2Fnode-red-contrib-rfxcom%2Fissues%2F126%23issuecomment-1366177073&data=05%7C01%7C%7C2097a8bcdaa2457de93808dae84ce503%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638077714203960283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f7CzXJ60Lif3m2p0Sb01hgI5Tywg2fJWYjMNiVefC1w%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANRXKF2FKA5T7N5D5BFRIE3WPNJZTANCNFSM6AAAAAASMOL6ZM&data=05%7C01%7C%7C2097a8bcdaa2457de93808dae84ce503%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638077714203960283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=B%2FEhYNKloARUT1EZYU0onHvgjgK%2FWObS2Qx%2BbCDCoaQ%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>

maxwellhadley commented 1 year ago

A fix is in progress - I hope to publish a new version in the next couple of weeks

jag100UK commented 1 year ago

That’s Great!

Thanks Max

John

Sent from my iPhone

On 29 Jan 2023, at 20:03, Max Hadley @.***> wrote:



A fix is in progress - I hope to publish a new version in the next couple of weeks

— Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaxwellhadley%2Fnode-red-contrib-rfxcom%2Fissues%2F126%23issuecomment-1407757114&data=05%7C01%7C%7C790706f3ee5944e8c55108db0233f3bd%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638106194375744869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3GkX3XuCDm1mSCT607Hm8q%2BFFVF9AZmn7Z6vacUUNmw%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANRXKFY6EATUR6MUJKITIALWU3EKVANCNFSM6AAAAAASMOL6ZM&data=05%7C01%7C%7C790706f3ee5944e8c55108db0233f3bd%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638106194375744869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=a0KzG9v%2BLRN0QcuvqAHSU5CNqcgLpKBVL4%2Bd557K4F4%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>

maxwellhadley commented 1 year ago

I have just published version 2.12.0 which adds support for the unit number to BLINDS_T11, among other things. Please chek it out: if it works for you I will close the issue

jag100UK commented 1 year ago

Thanks Max

This feels like a dumb question, but what difference am I expecting to see?

In the Pallet I have verified I have node-red-contrib-rfxcom version 2.12.0.

When I debug the value from rfx-blinds-in, it looks the same as before. There's no unit in the address or payload

Example:- BLINDS_T11/0xA169A4 : msg.payload : string[4] "Open"

On the rfx-blinds-out node, I don't see any way to specify the Unit.

Regards

John

From: Max Hadley @.> Sent: 03 February 2023 17:17 To: maxwellhadley/node-red-contrib-rfxcom @.> Cc: jag100UK @.>; Author @.> Subject: Re: [maxwellhadley/node-red-contrib-rfxcom] Please add support for new feature in Firmware 1028 (Issue #126)

I have just published version 2.12.0 which adds support for the unit number to BLINDS_T11, among other things. Please chek it out: if it works for you I will close the issue

- Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaxwellhadley%2Fnode-red-contrib-rfxcom%2Fissues%2F126%23issuecomment-1416167103&data=05%7C01%7C%7C8c0b7fdae13d48f3050908db060a6446%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638110413926682032%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=V%2FKyyeOhOJyWJRfqJSRvuF6zM5bprWfIeqbyyqPlZe8%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANRXKF2E3LQ55GGS4YPU72TWVU4O5ANCNFSM6AAAAAASMOL6ZM&data=05%7C01%7C%7C8c0b7fdae13d48f3050908db060a6446%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638110413926682032%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zNupA4sjw7iHnwl9gjwA1TsT8qSXkHL2JHyqiw%2Fpl8I%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.**@.>>

maxwellhadley commented 1 year ago

You should add the unit number after the first part of the address, separated with a /

BLINDS_T11/0xA169A4/1

That should work for sending commands. I thought it was working for receive as well when I tested it, but it looks like it still isn't. Please can you send me the byte sequence you get when you send a command from the remote and receive it on the RFXtrx? Either use RFXmgr, or enable debug output on the RFXCOM device and copy the output from the Node-RED console. I had to 'invent' a byte sequence based on the documentation to test receive operation, and it looks like I may have got it wrong :(

jag100UK commented 1 year ago

That's great, "Blinds out" works.

Here's what I receive using RFXmgr.

I notice that RFXmgr is displaying the Unit Number 1 value higher than the remote, but I think this is just a display bug.

The messages below are sent from a Louvolite R1922-6CH

All Blinds Open

03/02/2023 10:12:20:900= 09190B09A169A4000073

Packettype = BLINDS1

subtype = T11 ASP

Sequence nbr = 9

id1-3 = A169A4 decimal:10578340

Unit = All

Command = Open

Signal level = 7 -64dBm

Unit 1 Open

03/02/2023 10:13:31:536= 09190B15A169A4010073

Packettype = BLINDS1

subtype = T11 ASP

Sequence nbr = 21

id1-3 = A169A4 decimal:10578340

Unit = 2

Command = Open

Signal level = 7 -64dBm

Unit 2 Open

03/02/2023 10:14:15:202= 09190B18A169A4020073

Packettype = BLINDS1

subtype = T11 ASP

Sequence nbr = 24

id1-3 = A169A4 decimal:10578340

Unit = 3

Command = Open

Signal level = 7 -64dBm

Unit 6 Open

03/02/2023 10:14:43:957= 09190B1AA169A4060073

Packettype = BLINDS1

subtype = T11 ASP

Sequence nbr = 26

id1-3 = A169A4 decimal:10578340

Unit = 7

Command = Open

Signal level = 7 -64dBm

Many thanks

John

From: Max Hadley @.> Sent: 03 February 2023 22:00 To: maxwellhadley/node-red-contrib-rfxcom @.> Cc: jag100UK @.>; Author @.> Subject: Re: [maxwellhadley/node-red-contrib-rfxcom] Please add support for new feature in Firmware 1028 (Issue #126)

You should add the unit number after the first part of the address, separated with a /

BLINDS_T11/0xA169A4/1

That should work for sending commands. I thought it was working for receive as well when I tested it, but it looks like it still isn't. Please can you send me the byte sequence you get when you send a command from the remote and receive it on the RFXtrx? Either use RFXmgr, or enable debug output on the RFXCOM device and copy the output from the Node-RED console. I had to 'invent' a byte sequence based on the documentation to test receive operation, and it looks like I may have got it wrong :(

- Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaxwellhadley%2Fnode-red-contrib-rfxcom%2Fissues%2F126%23issuecomment-1416453847&data=05%7C01%7C%7C78f8f0c105c14d48710208db0631ef39%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638110583759460175%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wfQmQMgQepOnbP%2Bw8D%2FHHsgEqu55FTMi%2BIAu0wcDQ4s%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANRXKF2H4A5NEQPMECPTXVLWVV5ULANCNFSM6AAAAAASMOL6ZM&data=05%7C01%7C%7C78f8f0c105c14d48710208db0631ef39%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638110583759460175%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZPZJMklux94899UhupP6Ujp6tWDC4zUCuGc2x7UbzPk%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.**@.>>

maxwellhadley commented 1 year ago

Version 2.12.1 just published: rfx-blinds-in should include the unit code in the message topic OK now

jag100UK commented 1 year ago

Thank you, Max this is working well now.

I really appreciate you taking the time to add support for this feature.

Regards

John

From: Max Hadley @.> Sent: 04 February 2023 17:32 To: maxwellhadley/node-red-contrib-rfxcom @.> Cc: jag100UK @.>; Author @.> Subject: Re: [maxwellhadley/node-red-contrib-rfxcom] Please add support for new feature in Firmware 1028 (Issue #126)

Version 2.12.1 just published: rfx-blinds-in should include the unit code in the message topic OK now

- Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaxwellhadley%2Fnode-red-contrib-rfxcom%2Fissues%2F126%23issuecomment-1416807465&data=05%7C01%7C%7Ca6ba2e8b5aa24dec017e08db06d5aae4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638111286987994907%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XQEGHq6Z8km%2Fzmav7PpB4kpbHjLdcZms%2BUfVbHOLmQM%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANRXKF43F7ENZIYGINAO5ALWV2G7RANCNFSM6AAAAAASMOL6ZM&data=05%7C01%7C%7Ca6ba2e8b5aa24dec017e08db06d5aae4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638111286987994907%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=FfIY8fnQhnai%2BCUZ7fE0jo5Ntumz1iMMHuzCxcs%2F1C4%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.**@.>>

maxwellhadley commented 1 year ago

You're welcome!