Okay, here's a lil update for the benefit of anyone searching about this in the future.
I seem to get quirky errors related to the order which I import the assets:
Playmaker, Photon, Playmaker PUN, and Easy PUN setup.
I noticed in this thread:
http://hutonggames.com/playmakerforum/index.php?topic=13502.0that Jean says "for Unity 5, you need to download photon from the asset store first and then download the package from the Ecosystem."
so I started over with a new test project, and
1) imported Playmaker 1.8.3
2) then imported Photon Unity Networking Free 1.75
3) then imported Ecosystem.unitypackage and
4) used Ecosystem to download Playmaker PUN 1.75 for Unity 5
5) then imported Easy PUN setup
This order got rid of those "missing action" errors in the easy PUN FSMs
but then the console errors from this thread:
http://hutonggames.com/playmakerforum/index.php?topic=13545.0 appeared....
"Assets/PlayMaker/Actions/RunFSMAction.cs(138,30): error CS0115: `HutongGames.PlayMaker.Actions.RunFSMAction.DoParticleCollision(UnityEngine.GameObject)' is marked as an override but no suitable method found to override
Assets/PlayMaker/Actions/CollisionEvent.cs(119,34): error CS0115: `HutongGames.PlayMaker.Actions.CollisionEvent.DoParticleCollision(UnityEngine.GameObject)' is marked as an override but no suitable method found to override
Assets/PlayMaker/Actions/Physics2D/Collision2dEvent.cs(100,30): error CS0115: `HutongGames.PlayMaker.Actions.Collision2dEvent.DoParticleCollision(UnityEngine.GameObject)' is marked as an override but no suitable method found to override"Which also makes the Playmaker menu disappear.
So I reimported Playmaker 1.8.3 from asset store downloads list.
This fixed all errors for now and the Playmaker menu is back.
Quirky business but worth a try if you are stuck.
I hope this helps someone sometime.
-Jin