Unknown device detected

Recently I had an awning fitted which uses a Dooya remote control compatible with RFXCOM. I created an Indigo device with the appropriate config using HouseCode 5188D5. All worked well, but then I started getting error messages:

RFXCOM Error Unknown device detected (type = 25). Select a BlindsT1234 Device from the list of devices
RFXCOM Error HouseCode (hex)=E37B7D ,subtype (int)=6 ,unitCode (int)=193

In an effort to stop the error messages I tried creating another Indigo device with the config specified in the error message, but the error messages persist.

Here are the relevant log entries:

2023-07-30 12:37:41.730 DEBUG Plugin.debugLog: ++++++++++++++
2023-07-30 12:38:05.727 DEBUG Plugin.debugLog: b'\t\x19\x06\x1a\xe3{}\xc1\x00\x80' (processing)
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: processPacket: Data: b'\t\x19\x06\x1a\xe3{}\xc1\x00\x80' and type <class 'bytes'>
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: Blinds Remote with id1-3 2282425 and unitcode 193 command 0 received
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: Blinds Remote with subtype 6 and sensor 228242693 received
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: Enter the below into Device Details: HouseCode (hex):E37B7D, Subtype (int):6& UnitCode (int):193
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: b'\t\x19\x06\x1a\xe3{}\xc1\x00\x80' SensorId2: 6, and sensorid type: <class 'bytes'>
2023-07-30 12:38:05.730 ERROR Plugin.errorLog: Unknown device detected (type = 25). Select a BlindsT1234 Device from the list of devices
2023-07-30 12:38:05.730 ERROR Plugin.errorLog: HouseCode (hex)=E37B7D ,subtype (int)=6 ,unitCode (int)=193
2023-07-30 12:38:05.730 DEBUG Plugin.debugLog: ++++++++++++++
2023-07-30 12:38:09.803 DEBUG Plugin.debugLog: b'\t\x19\x06\x1b\xe3{}\xc1\x00\x80' (processing)
2023-07-30 12:38:09.803 DEBUG Plugin.debugLog: processPacket: Data: b'\t\x19\x06\x1b\xe3{}\xc1\x00\x80' and type <class 'bytes'>
2023-07-30 12:38:09.803 DEBUG Plugin.debugLog: Blinds Remote with id1-3 2282425 and unitcode 193 command 0 received
2023-07-30 12:38:09.804 DEBUG Plugin.debugLog: Blinds Remote with subtype 6 and sensor 228242693 received
2023-07-30 12:38:09.804 DEBUG Plugin.debugLog: Enter the below into Device Details: HouseCode (hex):E37B7D, Subtype (int):6& UnitCode (int):193
2023-07-30 12:38:09.804 DEBUG Plugin.debugLog: b'\t\x19\x06\x1b\xe3{}\xc1\x00\x80' SensorId2: 6, and sensorid type: <class 'bytes'>
2023-07-30 12:38:09.804 ERROR Plugin.errorLog: Unknown device detected (type = 25). Select a BlindsT1234 Device from the list of devices
2023-07-30 12:38:09.804 ERROR Plugin.errorLog: HouseCode (hex)=E37B7D ,subtype (int)=6 ,unitCode (int)=193
2023-07-30 12:38:09.804 DEBUG Plugin.debugLog: ++++++++++++++

I suspect the problem is coming from the awning wind sensor, which is separate from the awning and presumably simulates a remote control device to retract the awning when it's windy, but I can't see how to stop the error messages.

Any suggestions would be appreciated!

Hi

That was a change that I believe I introduced to support the Dooya blinds (have a few myself)

It will for a couple of reasons:

1.
In the RFXCOM plugin - there is a setting to log unknown devices. Unselect this and the blind error should go away.
You will need to reenable when setting up new devices.

But:
It will relate to another blind remote being used typically, and as you describe (re-read your message) probably the wind sensor.

This will go away if you create devices matching the ‘unknown’ device, because then is no longer unknown.
Might be 2 devices needed - one for open, one for close - not sure how the wind sensor works.
Don’t check have the correct HouseCode, subtype and unit codes and are in the correct format either Hex or Int (as per the info in the boxes)

Added benefit is the wind sensor status should also then be displayable from within Indigo.

Glenn


Sent from my iPad using Tapatalk

Hi Glenn

Thanks for the advice.

I created one device with the parameters given in the error message but that didn't stop the errors. You mention creating devices, plural. How would I do that when the parameters in the error messages are always the same?

Alan

You are correct - if you have the details correct then these messages should stop. Because basically becomes a known device.

Not sure why that isn’t working?
Double check you have the details correct.
May be a particularl aspect of the wind sensor - that means it is not being registered probably?

Did you see the log unknown devices checkbox in the plugin Config?

Glenn


Sent from my iPad using Tapatalk

Yes - I’ve unchecked it.

Device details definitely correct; entered exactly as the error message specified. Happy to show screenshots if it helps.

Might pay to log that devices details and copy here to double check.

I’ll have a look at code base and see if anything obvious there.


Sent from my iPad using Tapatalk

Here you go:

address : E37B7D
batteryLevel : None
blueLevel : None
brightness : 100
buttonConfiguredCount : 0
buttonGroupCount : 0
configured : True
defaultBrightness : 100
description :
deviceTypeId : BlindsT1234
displayStateId : brightnessLevel
displayStateImageSel : DimmerOn
displayStateValRaw : 100
displayStateValUi : 100
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState :
folderId : 1586788187
globalProps : MetaProps : (dict)
nl.rjdekok.indigoplugin.RFXCOM : (dict)
address : E37B7D (string)
ignoreDimmer : false (bool)
reverseActions : false (bool)
subtype : 6 (string)
unit : 193 (string)
greenLevel : None
id : 1799196580
lastChanged : 2023-07-28 21:08:28
lastSuccessfulComm : 2023-07-28 21:08:28
ledStates : []
model : BlindsT1234
name : Balcony Awning copy
onBrightensToDefaultToggle : False
onBrightensToLast : False
onState : True
ownerProps : nl.rjdekok.indigoplugin.RFXCOM : (dict)
address : E37B7D (string)
ignoreDimmer : false (bool)
reverseActions : false (bool)
subtype : 6 (string)
unit : 193 (string)
pluginId : nl.rjdekok.indigoplugin.RFXCOM
pluginProps : emptyDict : (dict)
protocol : Plugin
redLevel : None
remoteDisplay : True
sharedProps : com.indigodomo.indigoserver : (dict)
states : States : (dict)
blindState : Open (string)
brightnessLevel : 100 (integer)
command : Off (string)
lastUpdated : 2023/07/28 21:08:28 (string)
onOffState : on (on/off bool)
type : 6 (integer)
subModel :
subType :
supportsAllLightsOnOff : False
supportsAllOff : False
supportsColor : False
supportsOnState : True
supportsRGB : False
supportsRGBandWhiteSimultaneously : False
supportsStatusRequest : True
supportsTwoWhiteLevels : False
supportsTwoWhiteLevelsSimultaneously : False
supportsWhite : False
supportsWhiteTemperature : False
version : None
whiteLevel : None
whiteLevel2 : None
whiteTemperature : None

Hmm

Looks like it is being update with changes -
Does the state of this device change with the error message?

The plugin config setting re unknown devices should remove this


Sent from my iPhone using Tapatalk

Ok

Have spent a bit of time going through the code base, which uses HexCode, unitCode, as Byte and Integer to create a overall Sensor code which is saved.
Basically it all is working fine!

What version of plugin are you running - have been a few Python 3 versions
Is the Device enabled? Have you restarted Plugin?

Likely to need a whole lot more logging...

Logging:

Code: Select all

2023-07-30 12:38:05.727 DEBUG Plugin.debugLog: b'\t\x19\x06\x1a\xe3{}\xc1\x00\x80' (processing)
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: processPacket: Data: b'\t\x19\x06\x1a\xe3{}\xc1\x00\x80' and type <class 'bytes'>
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: Blinds Remote with id1-3 2282425 and unitcode 193 command 0 received
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: Blinds Remote with subtype 6 and sensor 228242693 received
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: Enter the below into Device Details: HouseCode (hex):E37B7D, Subtype (int):6& UnitCode (int):193
2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: b'\t\x19\x06\x1a\xe3{}\xc1\x00\x80' SensorId2: 6, and sensorid type: <class 'bytes'>
2023-07-30 12:38:05.730 ERROR Plugin.errorLog: Unknown device detected (type = 25). Select a BlindsT1234 Device from the list of devices
2023-07-30 12:38:05.730 ERROR Plugin.errorLog: HouseCode (hex)=E37B7D ,subtype (int)=6 ,unitCode (int)=193

Plugin Receives:
(Bytearray)
b'\t\x19\x06\x1a\xe3{}\xc1\x00\x80'
HouseCode (hex):E37B7D, Subtype (int):6 & UnitCode (int):193

This is all correct.

Overall 'Sensor' value is what is saved, and checked on device Start.

Calculated by:
HexValue="e37b7d"

Code: Select all

adres1 = int(dev.pluginProps['address'][0:2], 16)
adres2 = int(dev.pluginProps['address'][2:4], 16)
adres3 = int(dev.pluginProps['address'][4:6], 16)

Then added the unitCode which is given as 193

Code: Select all

int((adres1 * 1000000) + (adres2 * 10000) + (adres3 * 100) + housecode)

Gives us a Sensor = 228242693

In you log you will see this is given, and is calculated differently, hence had to check.

Code: Select all

2023-07-30 12:38:05.729 DEBUG Plugin.debugLog: Blinds Remote with subtype 6 and sensor [b]228242693 [/b]received

So the sensor value calculated on device start, and received as per log here both equal = 228242693 essentially meaning the device is not unknown and you shouldn't receive this message.

So likely device is not starting up for whatever reason, is not enabled within Indigo or something else??

& Just re-read this:

Yes - I’ve unchecked it.
.

Do you mean have unchecked show unknown devices as error?

In which case that seems very odd, as code would suggest no way to get those errors if not checked.

Sorry for any confusion; the error messages did stop when I unchecked the box. I was just trying to understand why they would arise in the first place, given that I’d created a new device which presumably should have stopped them.

I’m running the latest version of the plugin, and I’ve tried restarting.

But the main problem (error messages in the log) is effectively fixed, so thanks.

Sorry for any confusion; the error messages did stop when I unchecked the box. I was just trying to understand why they would arise in the first place, given that I’d created a new device which presumably should have stopped them.

I’m running the latest version of the plugin, and I’ve tried restarting.

But the main problem (error messages in the log) is effectively fixed, so thanks.

No problem - glad one mystery explained!

Although doesn’t make sense that message still appeared despite that device existing. May have been disabled, not enabled or something up with it (exception/crash when tries to start), as seems to have correct details.

Glenn


Sent from my iPad using Tapatalk