Author Topic: Communication issues with Powermaster 30 and Plugin  (Read 301 times)

Offline intveltr

  • Hero Member
  • *****
  • Posts: 1683
  • Karma: +93/-5
Communication issues with Powermaster 30 and Plugin
« on: August 25, 2017, 10:01:32 am »
I'm trying to resolve an issue with the Powermaster 30 and this plugin (Running on a VeraLite, latest UI7).  It looks like every now and then, the link between the alarm panel and the plugin is lost momentarily. 

When the panel is disarmed, door sensor changes come through almost instantly, and I can have the setup run for days without a single Comms Error.  The error appears to happen when arming / disarming the panel or when tripping a sensor while the panel is armed.  Updates stop coming in and commands aren't going out, until after a minute or so, when the log shows a pile of messages coming in, or Vera resets and shows another Comm Error in the plugin's variables.

At first I suspected the serial cable, but I have tried with 2 different Serial to USB converters plugged into the Visonic serial board, and with one FTDI USB to TTL (3.3v) cable plugged directly into the 10 pin PC port on the alarm panel.  Results are the same in all cases.

I talked to a reseller of Visonic Panels who has experienced the same issues in a similar setup (using VeraLite and UI7), but other people seem to have no issues using this alarm panel and the plugin.

At this stage, what can I do to diagnose this further?  The logs are inconclusive, I posted a few snippets from a couple of trouble moments below.

Code: [Select]
06      08/18/17 12:13:49.848   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: VendorStatus was: Away Exit Delay ,MEM,TRBL now: Armed Away ,MEM,TRBL #hooks: 0 upnp: 0 skip: 0 v:0xecc3f0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.861   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: VendorStatusCode was: 0217 now: 0547 #hooks: 0 upnp: 0 skip: 0 v:0xecc538/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.862   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: VendorStatusData was: Ready, Alert in memory, Trouble, Last 10 seconds now: Ready, Alert in memory, Trouble, Status changed #hooks: 0 upnp: 0 skip: 0 v:0xecc608/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.862   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmMode was: Disarmed now: Armed #hooks: 0 upnp: 0 skip: 0 v:0xe73130/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.863   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmModeNum was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.864   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: DetailedArmMode was: ExitDelay now: Armed #hooks: 0 upnp: 0 skip: 0 v:0xeca2c0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.865   Device_Variable::m_szValue_set device: 103 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xe75ba0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.867   Device_Variable::m_szValue_set device: 104 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xe75ba0/NONE duplicate:0 <0x2e840680>
50      08/18/17 12:13:49.869   luup_log:101: POWERMAX: Start of new PDU detected <0x2e840680>
50      08/18/17 12:13:49.870   luup_log:101: POWERMAX: Message A7; pmIncomingPduLen = 15 <0x2e840680>
50      08/18/17 12:13:49.890   luup_log:101: POWERMAX: PDU received 0D A7 FF 52 61 52 01 FF 00 06 00 00 43 08 0A  <0x2e840680>
50      08/18/17 12:13:49.892   luup_log:101: POWERMAX: PDU sent to panel: 0D 02 43 BA 0A  <0x2e840680>
50      08/18/17 12:13:49.894   luup_log:101: POWERMAX: System message: Arm Away / UNKNOWN <0x2e840680>
06      08/18/17 12:13:49.895   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: 1C now: 52 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.896   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was: General Restore / X10  07 now: Arm Away / UNKNOWN #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.897   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:1 <0x2e840680>
06      08/18/17 12:13:49.897   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
50      08/18/17 12:13:49.898   luup_log:101: POWERMAX: System message:  / Zone 01 <0x2e840680>
06      08/18/17 12:13:49.899   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: 52 now: FF #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.900   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was: Arm Away / UNKNOWN now:  / Zone 01 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.901   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:1 <0x2e840680>
06      08/18/17 12:13:49.902   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
50      08/18/17 12:13:49.902   luup_log:101: POWERMAX: System message: Tamper / System  <0x2e840680>
06      08/18/17 12:13:49.903   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: FF now: 06 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.904   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was:  / Zone 01 now: Tamper / System  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.905   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: None now: Tamper #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.906   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
50      08/18/17 12:13:49.907   luup_log:101: POWERMAX: System message: None / System  <0x2e840680>
06      08/18/17 12:13:49.907   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: 06 now: 00 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.908   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was: Tamper / System  now: None / System  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.909   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: Tamper now: None #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.910   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
50      08/18/17 12:13:49.911   luup_log:101: POWERMAX: System message: Tamper Alarm / X10  07 <0x2e840680>
06      08/18/17 12:13:49.912   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: 00 now: 08 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.912   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was: None / System  now: Tamper Alarm / X10  07 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.913   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: None now: Tamper #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.914   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
01      08/18/17 12:13:49.915   LuaInterface::CallFunction-2 lu_incoming failed [string "module("L_Powermax", package.seeall)..."]:1889: bad argument #1 to 'band' (number expected, got nil) <0x2e840680>



50      08/18/17 12:16:57.101   luup_log:101: POWERMAX: Checking last alive message (delta = 80.00035905838) <0x2d9ff680>
50      08/18/17 12:16:57.101   luup_log:101: POWERMAX: Clear Powerlink communication error <0x2d9ff680>
50      08/18/17 12:16:57.103   luup_log:101: POWERMAX: PDU sent to panel: 0D AB 06 00 00 00 00 00 00 00 00 00 43 0B 0A  <0x2d9ff680>
06      08/18/17 12:16:57.105   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PowerlinkMode was: Powerlink now: Standard #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2d9ff680>
50      08/18/17 12:16:57.169   luup_log:101: POWERMAX: Truncating PDU 0D A7 FF 58 61 55 01 FF 00 06 00 00 43 FE 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43  <0x2e840680>
50      08/18/17 12:16:57.171   luup_log:101: POWERMAX: Start of new PDU detected; Expecting 02 A5 <0x2e840680>
50      08/18/17 12:16:57.171   luup_log:101: POWERMAX: Message A5; pmIncomingPduLen = 15 <0x2e840680>
50      08/18/17 12:16:57.176   luup_log:101: POWERMAX: PDU received 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A  <0x2e840680>
50      08/18/17 12:16:57.178   luup_log:101: POWERMAX: PDU sent to panel: 0D 02 43 BA 0A  <0x2e840680>
50      08/18/17 12:16:57.180   luup_log:101: POWERMAX: *** Re-sending PDU (expected 02 got A5) *** <0x2e840680>
06      08/18/17 12:16:57.182   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: CommExceptions was: 2 now: 3 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:16:57.183   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: CommLastException was: 1502721305 now: 1503051417 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
50      08/18/17 12:16:57.184   luup_log:101: POWERMAX: *** Houston - we have a communication problem (wrong response)! Executing a reload. *** <0x2e840680>
50      08/18/17 12:16:57.185   luup_log:101: POWERMAX: *** Send message delayed *** <0x2e840680>


50      08/18/17 12:28:47.506   luup_log:101: POWERMAX: Start of new PDU detected <0x2e9d0680>
50      08/18/17 12:28:47.507   luup_log:101: POWERMAX: Message B0; pmIncomingPduLen = 0 <0x2e9d0680>
50      08/18/17 12:28:47.509   luup_log:101: POWERMAX: Message B0; pmIncomingPduLen = 33 <0x2e9d0680>
50      08/18/17 12:28:47.538   luup_log:101: POWERMAX: CRC check failed (expected 4D, got 43) <0x2e9d0680>
50      08/18/17 12:28:47.539   luup_log:101: POWERMAX: PDU with CRC error 0D B0 03 24 1A FF 08 FF 15 00 00 00 00 02 00 00 00 0A 1C 0C 12 08 11 14 06 01 00 86 00 00 A2 43 0A  <0x2e9d0680>

HomeWave is available in the App Store!  Turn your iPhone/iPad into an easy-to-use remote control for Vera.

Offline teonebello

  • Sr. Member
  • ****
  • Posts: 405
  • Karma: +0/-0
  • Macs, Home Automation, Bikers
Re: Communication issues with Powermaster 30 and Plugin
« Reply #1 on: October 02, 2017, 10:56:23 am »
I'm trying to resolve an issue with the Powermaster 30 and this plugin (Running on a VeraLite, latest UI7).  It looks like every now and then, the link between the alarm panel and the plugin is lost momentarily. 

When the panel is disarmed, door sensor changes come through almost instantly, and I can have the setup run for days without a single Comms Error.  The error appears to happen when arming / disarming the panel or when tripping a sensor while the panel is armed.  Updates stop coming in and commands aren't going out, until after a minute or so, when the log shows a pile of messages coming in, or Vera resets and shows another Comm Error in the plugin's variables.

At first I suspected the serial cable, but I have tried with 2 different Serial to USB converters plugged into the Visonic serial board, and with one FTDI USB to TTL (3.3v) cable plugged directly into the 10 pin PC port on the alarm panel.  Results are the same in all cases.

I talked to a reseller of Visonic Panels who has experienced the same issues in a similar setup (using VeraLite and UI7), but other people seem to have no issues using this alarm panel and the plugin.

At this stage, what can I do to diagnose this further?  The logs are inconclusive, I posted a few snippets from a couple of trouble moments below.

Code: [Select]
06      08/18/17 12:13:49.848   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: VendorStatus was: Away Exit Delay ,MEM,TRBL now: Armed Away ,MEM,TRBL #hooks: 0 upnp: 0 skip: 0 v:0xecc3f0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.861   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: VendorStatusCode was: 0217 now: 0547 #hooks: 0 upnp: 0 skip: 0 v:0xecc538/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.862   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: VendorStatusData was: Ready, Alert in memory, Trouble, Last 10 seconds now: Ready, Alert in memory, Trouble, Status changed #hooks: 0 upnp: 0 skip: 0 v:0xecc608/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.862   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmMode was: Disarmed now: Armed #hooks: 0 upnp: 0 skip: 0 v:0xe73130/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.863   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmModeNum was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.864   Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: DetailedArmMode was: ExitDelay now: Armed #hooks: 0 upnp: 0 skip: 0 v:0xeca2c0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.865   Device_Variable::m_szValue_set device: 103 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xe75ba0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.867   Device_Variable::m_szValue_set device: 104 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Armed was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xe75ba0/NONE duplicate:0 <0x2e840680>
50      08/18/17 12:13:49.869   luup_log:101: POWERMAX: Start of new PDU detected <0x2e840680>
50      08/18/17 12:13:49.870   luup_log:101: POWERMAX: Message A7; pmIncomingPduLen = 15 <0x2e840680>
50      08/18/17 12:13:49.890   luup_log:101: POWERMAX: PDU received 0D A7 FF 52 61 52 01 FF 00 06 00 00 43 08 0A  <0x2e840680>
50      08/18/17 12:13:49.892   luup_log:101: POWERMAX: PDU sent to panel: 0D 02 43 BA 0A  <0x2e840680>
50      08/18/17 12:13:49.894   luup_log:101: POWERMAX: System message: Arm Away / UNKNOWN <0x2e840680>
06      08/18/17 12:13:49.895   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: 1C now: 52 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.896   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was: General Restore / X10  07 now: Arm Away / UNKNOWN #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.897   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:1 <0x2e840680>
06      08/18/17 12:13:49.897   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
50      08/18/17 12:13:49.898   luup_log:101: POWERMAX: System message:  / Zone 01 <0x2e840680>
06      08/18/17 12:13:49.899   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: 52 now: FF #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.900   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was: Arm Away / UNKNOWN now:  / Zone 01 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.901   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:1 <0x2e840680>
06      08/18/17 12:13:49.902   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
50      08/18/17 12:13:49.902   luup_log:101: POWERMAX: System message: Tamper / System  <0x2e840680>
06      08/18/17 12:13:49.903   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: FF now: 06 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.904   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was:  / Zone 01 now: Tamper / System  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.905   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: None now: Tamper #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.906   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
50      08/18/17 12:13:49.907   luup_log:101: POWERMAX: System message: None / System  <0x2e840680>
06      08/18/17 12:13:49.907   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: 06 now: 00 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.908   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was: Tamper / System  now: None / System  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.909   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: Tamper now: None #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.910   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
50      08/18/17 12:13:49.911   luup_log:101: POWERMAX: System message: Tamper Alarm / X10  07 <0x2e840680>
06      08/18/17 12:13:49.912   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusCode was: 00 now: 08 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.912   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelStatusData was: None / System  now: Tamper Alarm / X10  07 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.913   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelAlarmType was: None now: Tamper #hooks: 0 upnp: 0 skip: 0 v:0xc5c9b0/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:13:49.914   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PanelTroubleType was: None now: None #hooks: 0 upnp: 0 skip: 0 v:0xe73840/NONE duplicate:1 <0x2e840680>
01      08/18/17 12:13:49.915   LuaInterface::CallFunction-2 lu_incoming failed [string "module("L_Powermax", package.seeall)..."]:1889: bad argument #1 to 'band' (number expected, got nil) <0x2e840680>



50      08/18/17 12:16:57.101   luup_log:101: POWERMAX: Checking last alive message (delta = 80.00035905838) <0x2d9ff680>
50      08/18/17 12:16:57.101   luup_log:101: POWERMAX: Clear Powerlink communication error <0x2d9ff680>
50      08/18/17 12:16:57.103   luup_log:101: POWERMAX: PDU sent to panel: 0D AB 06 00 00 00 00 00 00 00 00 00 43 0B 0A  <0x2d9ff680>
06      08/18/17 12:16:57.105   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: PowerlinkMode was: Powerlink now: Standard #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2d9ff680>
50      08/18/17 12:16:57.169   luup_log:101: POWERMAX: Truncating PDU 0D A7 FF 58 61 55 01 FF 00 06 00 00 43 FE 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43 BA 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A 0D 02 43  <0x2e840680>
50      08/18/17 12:16:57.171   luup_log:101: POWERMAX: Start of new PDU detected; Expecting 02 A5 <0x2e840680>
50      08/18/17 12:16:57.171   luup_log:101: POWERMAX: Message A5; pmIncomingPduLen = 15 <0x2e840680>
50      08/18/17 12:16:57.176   luup_log:101: POWERMAX: PDU received 0D A5 10 01 00 00 00 00 00 00 00 00 43 06 0A  <0x2e840680>
50      08/18/17 12:16:57.178   luup_log:101: POWERMAX: PDU sent to panel: 0D 02 43 BA 0A  <0x2e840680>
50      08/18/17 12:16:57.180   luup_log:101: POWERMAX: *** Re-sending PDU (expected 02 got A5) *** <0x2e840680>
06      08/18/17 12:16:57.182   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: CommExceptions was: 2 now: 3 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
06      08/18/17 12:16:57.183   Device_Variable::m_szValue_set device: 101 service: urn:micasaverde-com:serviceId:PowermaxAlarmPanel1 variable: CommLastException was: 1502721305 now: 1503051417 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2e840680>
50      08/18/17 12:16:57.184   luup_log:101: POWERMAX: *** Houston - we have a communication problem (wrong response)! Executing a reload. *** <0x2e840680>
50      08/18/17 12:16:57.185   luup_log:101: POWERMAX: *** Send message delayed *** <0x2e840680>


50      08/18/17 12:28:47.506   luup_log:101: POWERMAX: Start of new PDU detected <0x2e9d0680>
50      08/18/17 12:28:47.507   luup_log:101: POWERMAX: Message B0; pmIncomingPduLen = 0 <0x2e9d0680>
50      08/18/17 12:28:47.509   luup_log:101: POWERMAX: Message B0; pmIncomingPduLen = 33 <0x2e9d0680>
50      08/18/17 12:28:47.538   luup_log:101: POWERMAX: CRC check failed (expected 4D, got 43) <0x2e9d0680>
50      08/18/17 12:28:47.539   luup_log:101: POWERMAX: PDU with CRC error 0D B0 03 24 1A FF 08 FF 15 00 00 00 00 02 00 00 00 0A 1C 0C 12 08 11 14 06 01 00 86 00 00 A2 43 0A  <0x2e9d0680>


Same issue. Any support?
Thanks

Offline nvm

  • Newbie
  • *
  • Posts: 6
  • Karma: +0/-0
Re: Communication issues with Powermaster 30 and Plugin
« Reply #2 on: October 12, 2017, 01:16:07 am »
I'm also experiencing the same issue with this plugin.

I reached out to nlrb for support but he has now moved onto a new platform, and is no longer supporting the plugin.

Is there anyone else who is able to provide support?

Offline A.Ardon

  • Full Member
  • ***
  • Posts: 111
  • Karma: +0/-2
Re: Communication issues with Powermaster 30 and Plugin
« Reply #3 on: October 16, 2017, 02:50:27 pm »
I think I have the same issue.
Now and than I have some communication problems with the Visonic Powermax+.

It started happening after upgrading my new Vera Plus to te latest version 1.7.3232.
 :(
« Last Edit: October 16, 2017, 02:52:14 pm by A.Ardon »
1x VeraPlus UI7, Opentherm- Gateway, Powermax+,  Philips Hue, Dahua DVR, Yamaha RXV775, ect.

Offline teonebello

  • Sr. Member
  • ****
  • Posts: 405
  • Karma: +0/-0
  • Macs, Home Automation, Bikers
Re: Communication issues with Powermaster 30 and Plugin
« Reply #4 on: October 23, 2017, 05:25:30 pm »
I think I have the same issue.
Now and than I have some communication problems with the Visonic Powermax+.

It started happening after upgrading my new Vera Plus to te latest version 1.7.3232.
 :(


Anyone get a solution? Like this the plugin is useless and my vera is useless.
Any help?

Offline A.Ardon

  • Full Member
  • ***
  • Posts: 111
  • Karma: +0/-2
Re: Communication issues with Powermaster 30 and Plugin
« Reply #5 on: October 25, 2017, 03:06:24 pm »
I even found out that my 'Settings' tab is not displayed correctly....

Do you have the same?
See the Yellow marked places on the attached image.

I have contacted support to see if they can help.
unfortunaly, nlrb has is switched to an other platform.
1x VeraPlus UI7, Opentherm- Gateway, Powermax+,  Philips Hue, Dahua DVR, Yamaha RXV775, ect.

Offline A.Ardon

  • Full Member
  • ***
  • Posts: 111
  • Karma: +0/-2
Re: Communication issues with Powermaster 30 and Plugin
« Reply #6 on: October 25, 2017, 11:36:40 pm »
Ive, got a reaction from the Support team...
I think I will downgrade coming weekend.

Quote
Hi Andre

Thank you for contacting Vera Customer Care

We would like to let you know that we are aware of this issue and it is because a security concern that was added to latest version of the firmware, we already report this to our development team and they are working on it but we do not have an ETA for it.

We are awaiting that the plug-ins writers change some files on the API that work with the plug in on the port which it was blocked.

We suggest you to post this on our forum in order to see if there is a work around for it, but we are recommending to downgrade to 7.21 version of the firmware until we get the full fix for it.

Thank you for understanding
Regards

EDIT:
After downgrade to version 7.21 the connection problems where solved for now.
I will wait for the next firmware beyond 1 7.3232.
I have used the VeraPlus URL: https://dl.mios.com/rl/721/mt7621_Luup_ui7-1.7.2935-en-mios.squashfs to downgrade.
« Last Edit: October 29, 2017, 03:18:24 am by A.Ardon »
1x VeraPlus UI7, Opentherm- Gateway, Powermax+,  Philips Hue, Dahua DVR, Yamaha RXV775, ect.

Offline Yeche

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
Re: Communication issues with Powermaster 30 and Plugin
« Reply #7 on: November 06, 2017, 08:27:55 am »
Hi
I have PowerMax G33 and Vera
How you connect them? Have you used the Powerlink 3?