Arming Envisalink panel from MSR

[cw-kid]

Hi

I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.

They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

This is how that device looks in the Ezlo API.

Devices Info:

_id: "10696001"
deviceTypeId: "ezlopi"
parentDeviceId: "10696000"
category: "level_sensor"
subcategory: ""
gatewayId: "457a5069"
batteryPowered: false
name: "Gas Sensor Digital"
type: "sensor"
reachable: true
persistent: true
serviceNotification: false
armed: false
roomId: ""
security: "no"
ready: true
status: "idle"
parentRoom: true
protectConfig: "default"

Items Info:

_id: "20696001"
deviceId: "10696001"
hasGetter: true
hasSetter: false
name: "smoke_density"
show: true
valueType: "substance_amount"
scale: "parts_per_million"
value: 2.7472610473632812
valueFormatted: "2.75"
status: "idle"

There is also an Analog Gas sensor that one did import in to MSR OK.

Devices Info:

_id: "10696000"
deviceTypeId: "ezlopi"
parentDeviceId: "10696000"
category: "security_sensor"
subcategory: "gas"
gatewayId: "457a5069"
batteryPowered: false
name: "Gas Sensor Analog"
type: "sensor"
reachable: true
persistent: true
serviceNotification: false
armed: false
roomId: ""
security: "no"
ready: true
status: "idle"
parentRoom: true
protectConfig: "default"

Items Info:

_id: "20696000"
deviceId: "10696000"
hasGetter: true
hasSetter: false
name: "gas_alarm"
show: true
valueType: "token"
enum:
0: "no_gas"
1: "combustible_gas_detected"
2: "toxic_gas_detected"
3: "unknown"
valueFormatted: "no_gas"
value: "no_gas"
status: "idle"

And this is how this MQ2 Gas Sensor looks like on their dashboard:

Digital

Analog

They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!

And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.

THANKS.

[therealdb]

While I appreciate your faith, I'm genuinely wondering why ezlopi instead of tasmota or esphome. They're both more mature and easier to find help for, so my question.

Back in track, it's probably missing a mapping somewhere and @toggledbits needs to collect all the attributes of the device from reactor in order to support it.

[toggledbits]

@cw-kid said in Should MSR import this device type from an Ezlo controller?:

They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

According to their own API documentation, there's a reasonable value for subcategory that should be assigned here, but it's blank. Not sure if that's an error on their part, or just garden-variety laziness, but as we say here, not my circus, not my monkeys. I'm not working around their inability to follow their own specs. Make them fix their own bug.

@therealdb said in Should MSR import this device type from an Ezlo controller?:

While I appreciate your faith, I'm genuinely wondering why ezlopi instead of tasmota or esphome. They're both more mature and easier to find help for, so my question.

So right, mate. Why get bogged down and more committed to their bloated cloud-dependency when great, lightweight solutions have existed for years, with far better support?

@cw-kid, you do realize it's been over six years since the acquisition, right? I think it's safe to say, if they haven't muscled the core product up to well beyond Vera's capabilities at this point, they're not likely to ever get there. The Pi thing is a distraction. Or worse, in my view, it's a slap in the face to people like you who have been trying to help and waiting for the core product to come of age. I salute your dedication, but I'm not sure whatever reward you're seeking at the end is forthcoming.

[gwp1]

@toggledbits six years? Damn. I had two years in the office pool.... how they've managed to last six is unbelievable.

[CatmanV2]

Utterly amazing. He must be burning money!

C

[cw-kid]

@toggledbits said in Should MSR import this device type from an Ezlo controller?:

value for subcategory that should be assigned

Thanks, I didn't notice that. I will tell them to fix it.

Cheers.

[cw-kid]

As for your other comments Gentlemen, I don't disagree with them..