If everything works ok, then these variables won’t even exist. So we need to look into the cause of the communication exception. Have a look at the powermax_crash.txt file or send it to me.
Thanks for the info. My Vera is now remote and I m not able to view this file.
Do you think that is feasible to have a scene that every hour check this variable and if needed reset it?
Thank you for your support
Matteo
With version 1.1 you are able to download the file via the web interface, so you can get it remote.
Don’t go there. We really need to find the root cause.
With version 1.1 you are able to download the file via the web interface, so you can get it remote.
Don’t go there. We really need to find the root cause.[/quote]
Hi Blrb,
to the vera in my network I can access log with your link
http://<vera_ip>/port_3480/data_request?id=lr_GetCrashLogFile123 (where <vera_ip> is your vera’s IP address and 123 is the device id of the PowerMax Panel).
but to the vera (where I was the issue), I cannot access log with your link inserting the IP of the house. I don’t access to the local network in the next week.
Any idea?
Thank you
Regards,
Matteo
See the wiki how to use remote access.
So use https://fwd1.mios.com////data_request?id=lr_GetCrashLogFile123
[quote=“nlrb, post:25, topic:174625”]See the wiki how to use remote access.
So use https://fwd1.mios.com////data_request?id=lr_GetCrashLogFile123[/quote]
Hi Nlrb,
thank you!!
Here attached the log.
I need to delete the two variable every 2/3 hours.
Thank you for your help, I am not in the home and it is really an issue.
Thanks
Matteo
Wow, this looks messed up ???. I’ll need to look at it in more detail tomorrow.
First observations.
[ul][li]You are using FW1.5.408, recommend you go to 1.5.622[/li]
[li]Error in the log: luup_require can’t find json[/li]
[li]Serial communication looks messed up. Sometimes it just stops or false information comes in. Are you using an FTDI based RS232->USB cable?[/li]
[li]When trying to enter download mode, we get a denied message. However, it still seems to have entered download mode. This messes up the data flow. I’ll need to make the code more robust to handle such a case. What PowerMax model are you using?[/li][/ul]
[quote=“nlrb”]Wow, this looks messed up ???. I’ll need to look at it in more detail tomorrow.
First observations.
[ul][li]You are using FW1.5.408, recommend you go to 1.5.622[/li]
[li]Error in the log: luup_require can’t find json[/li]
[li]Serial communication looks messed up. Sometimes it just stops or false information comes in. Are you using an FTDI based RS232->USB cable?[/li]
[li]When trying to enter download mode, we get a denied message. However, it still seems to have entered download mode. This messes up the data flow. I’ll need to make the code more robust to handle such a case. What PowerMax model are you using?[/li][/ul][/quote]
First thanks!
We will try to uograde to 622.
I confirm that the cable is ftdi.
We are using a Powermax pro.
What do you mean with : [list][li]Error in the log: luup_require can’t find json[/l
Thank you
Matteo
Yes, the adapter is fine (I use the same ones).
The error ‘luup_require can’t find json’ is strange, as json is a standard element. Haven’t looked into it and don’t know if it is related.
[quote=“nlrb”]Yes, the adapter is fine (I use the same ones).
The error ‘luup_require can’t find json’ is strange, as json is a standard element. Haven’t looked into it and don’t know if it is related.[/quote]
Hi nlrb,
Unluckily the issue is going on and the plug in is blocked every couple of hours.
May I ask you an update?
Thank you very much
Regards,
Matteo
Can you try attached lua file and let me know how it goes?
Hi Nlrb,
tried the new file but still blocked after some hours after the variable reach the number 4.
Attached the new log.
Thank you for your help to this issue
Matteo
You can see in the log that it goes wrong at 19:58:40. The start of a new message is detected (POWERMAX: Message AB; pmIncomingPduLen = 15), but the message never completes. Nothing is received anymore. Only once a reload is executed (restarting the serial interface), communication starts again.
Hi Nlrb,
do you believe that the issue is in the powermax? The alarm work correctly and also the plug in works correctly. But it stop when the number reachs 4. I understand that the limit is important to detect issue, but it is not possible to override it? As it seems working perfectly.
I tried your new version but still same issue.
I don’t know how can I solve the issue. Doing a scenario that delete the two variable as you said is not so elegant. In that case it would be better to simple be able to remove the limit of 4.
Thank you very much for your time and effort
Matteo
Most likely the issue is in the RS232 adapter, as since the serial interface is restarted communication starts again. Still it is strange as these adapters are normally good.
You don’t want your Vera to keep on restarting. Communication should just continue. Nothing that I can do in the plugin, as it is just listening when communication stops.
sorry to reply to an old thread, but I’m having the same problem.
Vera2 (1.5.622), UI5, BAFO usb-serial, Powermax Pro, Visonic Powermax plugin 1.1
Installed the plugin yesterday after 2 years using the Powermax plugin from Utz, which worked problem free.
After a couple of hours I get a communication error and the Powermax Pro gives out a ‘tampering alarm’
and Vera2 reboots
Not sure what causes the reset of Vera, the communication error, or something other, which in turns resets the Vera and causes the communication error. As far as I know the BAFO works ok and is in the list of supported serial devices:
http://wiki.micasaverde.com/index.php/Serial_Supported_Hardware.
Anyway, just wanted to know if there ia any progress or solution.
Kind regards,
MS
There is no open issue, each case is different why communication fails, but so far not related to the plugin. You can set the plugin to ‘Force standard mode’ which should work. If you turn on debugging and send the LuaUPnP.log file to ‘vera.powermax at gmail.com’ I can have a look.
Thanks for your reply.
So far I’ve found out that the problem is caused by Vera2 spontaines resetting.
It seems to do that about 2-3 times in 24 hours and is not caused by your plugin.
The difference with the Utz plugin was that it ignored the resets.
The question is why the combination with your plugin is causing the Powermax to issue a Tamper alarm?
Kind regards,
MS
Don’t know and can’t tell without any log files.