Hi, I warmed the joints of the connectors with an micro electric welding machine just in case. It it in same situation keep on loopack info interating.
I send attachment of my powermax connections:
Hi, I warmed the joints of the connectors with an micro electric welding machine just in case. It it in same situation keep on loopack info interating.
I send attachment of my powermax connections:
Hi, do you also have a ground cable somewhere else, I can only see 2 wires?
Yes I have 5v and gnd connected to an usb plug.
I assume that the USB plug is powering the device and you only have 2 wires for Tx and Rx from the device to the panel.
Do you have the gnd from the USB plug connected to the gnd on the panel?
If not then connect the gnd from USB plug to gnd on the panel.
DO NOT connect the 5v from the USB to the panel.
Yes you are correct.
No it’s not connected to the panel, it’s directly connected to the tcp 232
I understand what you are suggesting. If i connect GND to powermax panel should I go get GND to TCP 232 from the panel from the other available pin?
Just to be clear:
Hope that helps
Yes. That finnaly solved the puzzle. Its working like magic! Thank you for the great words of wisdom. Oh great Davesmeghead!
That’s OK, I’m pleased you got it working
Powermaster 360
Between heating and eating I choose… alarm system. After many years of having Visonic Powermaster 360 on ADT contract, I decided to stop the subscription. Upon disconnection from the ADT central server, the system has started to behave in a slightly more logical way in autonomous mode.
Here is the logs: Visonic PowerMaster 360 - Pastebin.com
Apparently ADT didn’t give me installer code. In my experiments with PowerMaster Remote Programmer, none of the known download codes was accepted either. The only known code is the user master code which allows to arm and disarm the panel.
Being that close to giving the system a second lease of life, I have a couple of concerns.
Assuming I can perform factory reset successfully, how much of a hassle is it to re-program the panel from scratch? Would I have to recreate all the zones? Would the sensors reset themselves and wait for me to rejoin them? Or would I have to attend each of them and find their respective reset buttons?
If I were to decommission the siren altogether, would I trigger some loud noise when I attempt to extract its battery? Or do I have to get hold of the installer code and remove the siren from the setup first?
I’ve seen some code to brute force installer codes for a similar but different DSC panel. Is brute forcing more reliable / the only way if compared to the factory reset?
And, finally, @davesmeghead , we could be just a few steps away from adding PM-360 to the list of supported panels! PM-360 is slightly different from PM-360R. Please, let me know if you know something I don’t know. Or would you rather recommend me go Force Standard
? Would Force Standard
break that vicious resetting watchdog
cycle? Or is watchdog cycle harmless and not affecting arm / disarm capability?
For the reference, here are the panel’s identifiers:
Key | Value |
---|---|
Model | PM 360 (868-0:ANY)+W+2G+Z868 |
Control panel software version | JS703296 L19.412 |
Control panel default version | J-705117 L19.412 |
Control panel boot version | JS702767 L01.026 |
Control panel Remote Software Upgrade downloader version | JS702768 L02.036 |
PowerLink software version | PL8.0.94.14 row |
cellular modem type | GE910-QUAD-V3 |
Hi,
First of all thanks for uploading the logfile to pastebin as part of your first post, it does help me understand how far you’ve got. However the logfile is generated from a very old version of this integration, please download and use the latest code, it also looks like you’re using one of the example utilities to connect to the panel from a command prompt, is this the case?
On to your specific set of issues… I wouldn’t reset the panel yet.
I assume that your 360 panel is based on all other PowerMaster panels and therefore there are 4 different codes, User, Download, Master and Installer.
In your logfile the integration tries to use the default 5650 Download code (line 23) and fails (line 29) with a “[handle_msgtype08] Access Denied” message. So from this we know that the 5650 default Download code doesn’t work. If you are able to get the correct download code then by downloading the EEPROM you can get all other codes including the Installer code. I assume that you’ve also tried AAAA as the download code, that’s the other popular default Download code. If you’re a python programmer then you can write a small piece of code (using my code as well) to try the sequence of download codes one at a time to find out which one does not give the “Access Denied” message back from the panel.
Using Standard Mode is an option but I can’t tell as you’re using an old version of this integration. I’d also like to try to see if we can get it to Powerlink but to do that we need to find the Download code.
The message “resetting watchdog” in the log file is a good thing and should not affect arm / disarm capability. However, it will not arm / disarm whilst in the download state.
If you need further help then please create a specific Issue on the wiki rather in this thread here
Thanks
Around 6 days ago, my integration stopped entering Powerlink and only made it to Standard mode. About two days ago, it started a behavior where it oscillates between download and Standard modes. I suppose the problem could be related to HA updates. Hopefully, my panel isn’t failing.
Here’s a capture of the oscillation:
Here’s a log:
Do you need any other data?
Thanks in advance.
Hi Rob,
It keeps trying (and retrying) to download the EEPROM and each time it gets an access denied back from the panel, it’s using the default 5650 download code, can you try setting the download code to AAAA in the config and give it a try please.
Let me know what happens
Thanks, Dave. That worked. It’s back to Powerlink mode.
Hi Dave,
When I was trying out a few automations and triggered the alarm, the integration lost connection to my Powermaster 10 panel. I would greatly appreciate if you could have a look… Here’s a link to the log Powermaster error - Pastebin.com
Hi,
It’s a known problem that I’ve resolved in my latest development build. The processing of F4 messages from the panel causes the currently released integration to get confused, my dev build manages it better. It’s to do with your Zone 2 and the Camera / PIR and its sending images as F4 messages. I can’t decode them to get the image yet but I can tolerate them to prevent the integration crashing.
I may upload a dev build to Github but it won’t be a HACS release until i’ve tested it a bit more
D
Great! many thanks!
Hi,
First, thanks a lot for your awesome work and great documentation! I’ve just be able to integrate my Panel into HA at the first try whereas I was not able to do it with PowerLink into Jeedom for a long time.
Does your comment mean that we should disable the “disarm activity” of our NEXT CAM PG2 to reduce integration connection losses?
Let me know when your dev build will be available somewhere.
Hi and welcome, I’m pleased you got it working.
I assume that you have a PowerMaster series panel as you refer to a NEXT CAM PIR Camera. There’s 2 way communication between the PowerMaster Panel and the sensors and when the panel is in the disarmed state it tells the sensors not to report detections to save battery power in the sensor. If you want your sensors to detect and report to the panel when the panel is disarmed, then you need to configure this for each sensor using the panel menu (as per the instructions on the wiki).
Should be within the next week or so but it will be a development build i.e. you can expect it to have bugs and issues to be resolved. I won’t give anything away yet on new features but there’s extra support for PowerMaster panels in particular.
When I do the dev upload I’d appreciate any feedback on the old and new features, I’ve been rewriting some of the existing code to make common functions etc so existing capabilities may have bugs.
I’m also working on Arduino code for an ESP32 microcontroller device that bridges the Alarm Panel and a Powerlink 3.1, that also has a wifi connection supporting the HA Integration. I expect to have this ready soon as well but I’d like to get the main HA Integration debugged a bit more first.
You’re right.
I was asking because I’ve noticed that the motion events stop coming back quite quickly after the HA integration has started. And I was wondering if this could be caused by the unsupported image messages from NEXT CAM PIR Camera.
It sounds good to me.
FYI, I have :
I hope you find it useful.
Note that I am a new user of this integration. So I’m still exploring its behavior and features. So it may be more difficult for me to detect regressions or behavior changes.
This could be the cause, the processing of F4 image messages has hopefully been fixed in my upcoming dev release.
Also, support for multiple partitions is not yet included but it is on my todo list.
Any help in bug finding is of use to me and the whole community. Are you able to download a zip file of the dev build when I upload it to github and then unzip it to your HA custom_components directory?