You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found something weird with the returning msg.topic of the node ccu-rpc-event in Redmatic 5.2.0
In the node the returning msg.topic is declared with "${room}/${datapoint}/${datapointType}/${payload}"
No problem with this al working fine exept when the payload is 0 or false, then the value is NOT showed (integrated) into the msg.topic. (I don't know with negatief value's).
This happend with both HMIP-RF as BIDCOS-RF.
But the msg.payload show the value 0 or false
==> Picture Node HmRFIP No payload 0
==> Picture Node BidCos No payload 0
Also if the node is declared HMIP-RF with the value OPERATING-VOLTAGE then the room and functions are NOT implemented neither into the msg.topic as in the msg(object). With the BidCos there is NO problem.
==>Picture Node HmRFIP No room
I found a solution by redeclaring the topic myself in a separate function
I mentionned this behavior also in rdmtc/node-red-contrib-ccu
Srr for my poor english :)
The text was updated successfully, but these errors were encountered:
I found something weird with the returning msg.topic of the node ccu-rpc-event in Redmatic 5.2.0
In the node the returning msg.topic is declared with "${room}/${datapoint}/${datapointType}/${payload}"
No problem with this al working fine exept when the payload is 0 or false, then the value is NOT showed (integrated) into the msg.topic. (I don't know with negatief value's).
This happend with both HMIP-RF as BIDCOS-RF.
But the msg.payload show the value 0 or false
==> Picture Node HmRFIP No payload 0
==> Picture Node BidCos No payload 0
Also if the node is declared HMIP-RF with the value OPERATING-VOLTAGE then the room and functions are NOT implemented neither into the msg.topic as in the msg(object). With the BidCos there is NO problem.
==>Picture Node HmRFIP No room
I found a solution by redeclaring the topic myself in a separate function
I mentionned this behavior also in rdmtc/node-red-contrib-ccu
Srr for my poor english :)
The text was updated successfully, but these errors were encountered: