fredblo/node-red-contrib-myhome-bticino-v2

Node-RED nodes pack to interact with Bticino / Legrand MyHome devices

node-red-contrib-myhome-bticino-v2's Issues

Persistent connection not working with multiple commands

During testing, I noticed that when sending 2 commands in succession, the connection is re-established each time with the login.

This behavior causes a crash of the MH200 gateway when many commands are sent. Could this issue be resolved to prevent the gateway crash?

Gateway: MH200 (Keep alive 600 )
node-red: 3.0.2
node-red-contrib-myhome-bticino-v2: 2.3.0

Thank you for your attention.

16 Jan 08:48:27 - [info] [myhome-light:Corridoio -1] gateway connection : handshake acknowledged, asking for authentication if required...
16 Jan 08:48:27 - [info] [myhome-light:Corridoio -1] gateway connection : request to authenticate acknowledged, authenticating using basic password check...
16 Jan 08:48:27 - [info] [myhome-light:Corridoio -1] gateway connection : Connection successful !
16 Jan 08:48:27 - [info] [myhome-light:Corridoio -1] Command '*1*1*21##' sent using gateway...
16 Jan 08:48:27 - [info] [myhome-light:Corridoio -1] Command '*#1*21##' sent using gateway...
16 Jan 08:48:27 - [info] [myhome-gateway:MH-200] Received OpenWebNet command (OWN_LIGHTS) : '*1*1*21##'
16 Jan 08:48:27 - [info] [myhome-gateway:MH-200] Received OpenWebNet command (OWN_LIGHTS) : '*1*1*21##'
16 Jan 08:48:27 - [info] [myhome-gateway:MH-200] Received OpenWebNet command (OWN_OTHERS) : '*17*1*116##'
16 Jan 08:48:27 - [info] [myhome-gateway:MH-200] Received OpenWebNet command (OWN_OTHERS) : '*17*2*116##'
16 Jan 08:48:27 - [info] [myhome-gateway:MH-200] Received OpenWebNet command (OWN_LIGHTS) : '*1*1*21##'
16 Jan 08:48:28 - [info] [myhome-light:Corridoio -1] gateway connection : handshake acknowledged, asking for authentication if required...
16 Jan 08:48:28 - [info] [myhome-light:Corridoio -1] gateway connection : request to authenticate acknowledged, authenticating using basic password check...
16 Jan 08:48:28 - [info] [myhome-light:Corridoio -1] gateway connection : Connection successful !
16 Jan 08:48:28 - [info] [myhome-light:Corridoio -1] Command '*1*0*21##' sent using gateway...
16 Jan 08:48:28 - [info] [myhome-light:Corridoio -1] Command '*#1*21##' sent using gateway...
16 Jan 08:48:28 - [info] [myhome-gateway:MH-200] Received OpenWebNet command (OWN_LIGHTS) : '*1*0*21##'
16 Jan 08:48:28 - [info] [myhome-gateway:MH-200] Received OpenWebNet command (OWN_LIGHTS) : '*1*0*21##'

Is MH200 module supported?

Hello, thanks for your contribution to the scs system. I didn’t see MH200 gateway on the supported device list. I’m wondering that whether this device is unsupported? Or just you haven’t tested on MH200?

empty command_responses on inject node

Hi, when try to inject status request with inject node ( ex. *#1*32## - check status of 3.2 light)
in debug I see next thing:

{"command_sent":["*#1*32##"],"command_responses":[]}
so command_response is empty

but in same time if I connect monitoring node, I see that BUS responses (*1*0*32## - says it OFF) about status when I asked for it:

Error while installing

LOGS:

2022-03-21T18:19:15.144Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2022-03-21T18:19:18.414Z [err] npm
2022-03-21T18:19:18.415Z [err] ERR!
2022-03-21T18:19:18.415Z [err] code EBADENGINE
2022-03-21T18:19:18.420Z [err] npm
2022-03-21T18:19:18.420Z [err] ERR!
2022-03-21T18:19:18.421Z [err] engine Unsupported engine
2022-03-21T18:19:18.421Z [err] npm
2022-03-21T18:19:18.421Z [err] ERR! engine
2022-03-21T18:19:18.421Z [err] Not compatible with your version of node/npm: [email protected]
2022-03-21T18:19:18.421Z [err] npm ERR!
2022-03-21T18:19:18.421Z [err] notsup Not compatible with your version of node/npm: [email protected]
2022-03-21T18:19:18.421Z [err] npm
2022-03-21T18:19:18.421Z [err] ERR! notsup Required: {"node":"^0.12.7"}
2022-03-21T18:19:18.421Z [err] npm ERR! notsup Actual: {"npm":"8.1.3","node":"v16.14.0"}
2022-03-21T18:19:18.436Z [err]
2022-03-21T18:19:18.436Z [err] npm ERR! A complete log of this run can be found in:
2022-03-21T18:19:18.436Z [err] npm ERR! /root/.npm/_logs/2022-03-21T18_19_18_422Z-debug.log
2022-03-21T18:19:18.448Z rc=1

Reconnection error every minutes with mh201

I'm experiencing a loop (once every minutes more or less) of error with the connection with my MH201.
Here the related log from nodered

20/5/2021, 13:36:16node: MH201 msg : string[140] "gateway connection issue (Command not acknowledged (NACK) when already connected): last known state was 'connected', trying to re-connect..." 20/5/2021, 13:36:17node: MH201 msg : string[100] "gateway connection : disconnected from host, last known state was 'connected'. Auto retry activated." 20/5/2021, 13:36:17node: MH201 msg : string[113] "gateway connection issue (socket connection closed): last known state was 'disconnected', trying to re-connect..."

Different local BUS addresses

Hi @FredBlo !

You did a wonderful work , thanks .
I have a question , in my Myhome installation I have no.2 F422 and 3 different local bus ( 0 , 1 , 2 ) .
The gateway is on BUS 0

I have tried to send commands on other bus using OpenWebNet documention - WHO1 _ page 7
Table WHERE you can see :
A PL #4# Int →Point to point of local bus

I tried to insert a different address on MH Light ( eg .51#4#02 - Light Bus2_A5_PL1 ) and seem work fine ! 👍
The only problem seem the invalid property on lightid when I deploy it

TURN ON
msg.payload : string[14]
*1*1*51#4#02##

TURN OFF
msg.payload : string[14]
*1*0*51#4#02##

Can you check it ? ( see attached flow )

flows_BUS TEST.zip

Many thanks !

Termostat

Hi
How can I set "setTemperature" parametr with node MH Thermo Zone? Any exampless?

F454

I have the F454 webserver. Does this module also work? because I can't connect I get the following error:
"↵↵---------------------------------------------------------------------↵Your flow credentials file is encrypted using a system-generated key.↵↵If the system-generated key is lost for any reason, your credentials↵file will not be recoverable, you will have to delete it and re-enter↵your credentials.↵↵You should set your own key using the 'credentialSecret' option in↵your settings file. Node-RED will then re-encrypt your credentials↵file using your chosen key the next time you deploy a change.↵---------------------------------------------------------------------↵"
26/12/2023, 17:36:23
msg : string[31]
"Encrypted credentials not found"
26/12/2023, 17:36:23node: F-455
msg : string[78]
"gateway connection : disconnected from host, last known state was 'connected'."