Blocky don't run my scenes

[CoyoteMember]

Hi,

I have problems with blocky .. It doesn’t run my scenes.

I have a test with Yahoo Weather/Sunset and real time.. nothing..
I have a test with a DeviceEvent/Event Device with a motion ZWave sensor … nothing..

In the log scene, I just have
015-11-28 20:28:01 Periodic : Start
2015-11-28 20:28:01 Periodic : Run scene “xxxx.php”
2015-11-28 20:28:01 Periodic : End

On the dashboard and ImperiHome, the motion is detected.. But blocky doesn’t run my actions..

Maybe I have problem with my installation. In the Admin pannel, It says that I have the 1.2.1 version on my SOB, but on DSM, this is the 1.2.2…
Sometime, on DSM, my service is off… I have to launch it again…
Sometime in the admin panel, the core service is off too… And I have to launch it again..

I try to remove all files manualy (only in the web directory).. And install back PulseStation with DSM (I did it 6 times !!).. But nothing more.. I have still problems..

I was used to use it for many months.. without problems…

Can you help me ? Are there some files to delete on the NAS to be sure to do a “new” installation ?

Thx a lot

JMarc

[K.RensKeymaster]

Hi,

Everything is installed in /volume1/web/PulseStation.
If you delete that folder, everything is deleted except manual backups.
They are stored in /volume1/web/PulseStationBackup
But these backups should never interfere with the working of PulseStation, it is completely separate.

It’s normal that DSM is a few versions behind.
We always update PulseStation and only for major release the DSM package itself.
You can also ignore the status inside DSM (Synology), when the core is running inside PulseStation Administration (green tick), it’s fine.

I’ve written a basic FAQ message explaining how you can debug your scene issues:
https://www.pulse-station.com/faqs/debugging-the-core-and-all-services/

Note: make certain that for all motion based actions you use the blocky block “Device event = “

Kind regards,
K.Rens

[CoyoteMember]

Hi K.Rens

I’ve started core in a terminal, and there are a lot of ‘erros lines’ about Zwave service.
On each Zwave node,if I do an action, I have this messages :

PHP Warning: Illegal string offset ‘label’ in /volume1/web/PulseStation/services/zwave/convertToJson.php on line 96
PHP Warning: Illegal string offset ‘value’ in /volume1/web/PulseStation/services/zwave/convertToJson.php on line 97
PHP Warning: Illegal string offset ‘label’ in /volume1/web/PulseStation/services/zwave/convertToJson.php on line 96
PHP Warning: Illegal string offset ‘value’ in /volume1/web/PulseStation/services/zwave/convertToJson.php on line 97

And this :

2015-11-29 07:11:41.792 Detail, Node005, Notification: ValueChanged
PHP Warning: parse_ini_file(/volume1/web/PulseStation/services/zwave/../database/config.ini): failed to open stream: No such file or directory in /volume1/web/PulseStation/services/zwave/utils.php on line 280

But nodes are oki in the dashboard, and ImperiHome (My motion sensor is well working…).. But not in blocky.. The scene which must start by [If Device Event == Motion Sensor..] doesn’t start.

I have found this line on the core log too :

2015-11-29 07:25:00.991 scene : Message received – 1|scene|scene|CHECKSCENESPERIODIC|1448778300863|64b3993bb42914541a4207e2ca0e3ce6
ps: invalid option — ‘a’
BusyBox v1.16.1 (2015-10-28 13:24:11 CST) multi-call binary.

Usage: ps

Report process status

Options:
w Wide output

I don’t know if this is normal…

Still under investigations

Thx a lot for your help

JMarc

[CoyoteMember]

Hi,

In fact, the block “Device Event ==” is not working.
If I put my Zwave sensor with a true condition in a loop, it’s ok each minute…the rule works

If I put “Device Event ==” with my sensor, nothing works, and I never see it in the scene log.
In my memory.. there was having a line in scene.log at each time the event was watched..

Any ideas ?

JM

[K.RensKeymaster]

Can you share a screenshot with me from your exact blocky rule?

Following error messages are normal and not an issue:
– PHP Warning: Illegal string offset ‘value’ in /volume1/web/PulseStation/services/zwave/convertToJson.php
– ps: invalid option — ‘a’

This one I do not have myself:
PHP Warning: parse_ini_file(/volume1/web/PulseStation/services/zwave/../database/config.ini): failed to open stream: No such file or directory in /volume1/web/PulseStation/services/zwave/utils.php on line 280

Can you also review your database settings and that they are still ok?
Looks like an issue there.
You may also need to verify whether everything in the services/database folder is owned by the “http” user, so he can read it (ls -la /volume1/web/PulseStation/services/database/).

Kind regards,
K.Rens

[djoul2706Participant]

Hi,
Since the last version of the scene service I do have the same issue.
I thought it was related to my scenes but I doubt it now.

My logs show just one scene in the periodic starts meanwhile I have much more scenes expected to run (see the logs below).
I tried to modify the scene and save it but it doesn’t solve it.

2015-12-02 13:02:19 Event : Scene “get_temp.php” deactivate
2015-12-02 13:02:19 Event : Scene “timer.php” deactivate
2015-12-02 13:02:26 Event : Run scene “detect_mvt_salon.php” with event : “zwave-12_ON”
2015-12-02 13:02:26 Event : Scene “get_temp.php” deactivate
2015-12-02 13:02:27 Event : Scene “timer.php” deactivate
2015-12-02 13:02:27 Event : Scene “detect_mvt_salon.php” is already running.
2015-12-02 13:02:27 Event : Scene “get_temp.php” deactivate
2015-12-02 13:02:28 Event : Scene “timer.php” deactivate
2015-12-02 13:02:28 Force start : Run scene “christmasT.php”
2015-12-02 13:02:28 Force start : Run scene “lumieres_salon.php”
2015-12-02 13:03:00 Periodic : Start
2015-12-02 13:03:00 Periodic : Scene “get_temp.php” deactivate
2015-12-02 13:03:01 Periodic : End
2015-12-02 13:03:10 Event : Scene “get_temp.php” deactivate
2015-12-02 13:04:01 Periodic : Start
2015-12-02 13:04:01 Periodic : Scene “get_temp.php” deactivate
2015-12-02 13:04:01 Periodic : End
2015-12-02 13:04:05 Event : Run scene “detect_mvt_salon.php” with event : “zwave-12_ON”
2015-12-02 13:04:05 Event : Scene “get_temp.php” deactivate
2015-12-02 13:04:07 Force start : Run scene “christmasT.php”
2015-12-02 13:04:07 Force start : Run scene “lumieres_salon.php”
2015-12-02 13:04:35 Event : Scene “get_temp.php” deactivate
2015-12-02 13:05:00 Periodic : Start
2015-12-02 13:05:01 Periodic : Scene “get_temp.php” deactivate
2015-12-02 13:05:01 Periodic : End

thanks for your advices.
regards
Julien

[djoul2706Participant]

FYI, I restored the last backup (before service scene 1.0.1) and all the scenes are ran now :

2015-11-21 12:01:00 Periodic : Start
2015-11-21 12:01:00 Periodic : Run scene “globalscene.php”
2015-11-21 12:01:00 Periodic : Run scene “get_mode_from_cal.php”
2015-11-21 12:01:00 Periodic : Scene “detect_mvt_salon.php” is already running.
2015-11-21 12:01:01 Periodic : Run scene “alertes_salon.php”
2015-11-21 12:01:01 Periodic : Scene “get_temp.php” deactivate
2015-11-21 12:01:01 Periodic : Run scene “set_rad_sdb.php”
2015-11-21 12:01:01 Periodic : Run scene “set_rad_salon.php”
2015-11-21 12:01:01 Periodic : Run scene “purge_logs.php”
2015-11-21 12:01:01 Periodic : Run scene “set_consigne_chbT.php”
2015-11-21 12:01:01 Periodic : Run scene “set_presence_chbT.php”
2015-11-21 12:01:01 Periodic : Run scene “get_from_pi.php”
2015-11-21 12:01:01 Periodic : End
2015-12-02 14:13:28 Event : Scene “get_temp.php” deactivate
2015-12-02 14:13:59 Event : Run scene “detect_mvt_salon.php” with event : “zwave-12_ON”
2015-12-02 14:13:59 Event : Scene “get_temp.php” deactivate
2015-12-02 14:14:01 Periodic : Start
2015-12-02 14:14:01 Periodic : Run scene “globalscene.php”
2015-12-02 14:14:01 Periodic : Run scene “get_mode_from_cal.php”
2015-12-02 14:14:01 Periodic : Run scene “meteo_alert.php”
2015-12-02 14:14:01 Periodic : Run scene “alertes_salon.php”
2015-12-02 14:14:01 Periodic : Scene “detect_mvt_salon.php” is already running.
2015-12-02 14:14:01 Periodic : Scene “get_temp.php” deactivate
2015-12-02 14:14:01 Periodic : Run scene “set_rad_sdb.php”
2015-12-02 14:14:01 Periodic : Run scene “set_rad_salon.php”
2015-12-02 14:14:01 Periodic : Run scene “purge_logs.php”
2015-12-02 14:14:01 Periodic : Run scene “christmasT.php”
2015-12-02 14:14:02 Periodic : Run scene “lumieres_salon.php”
2015-12-02 14:14:02 Periodic : Run scene “timer.php”
2015-12-02 14:14:02 Periodic : Run scene “prescene.php”
2015-12-02 14:14:02 Periodic : Run scene “set_consigne_chbT.php”
2015-12-02 14:14:02 Periodic : Run scene “set_presence_chbT.php”
2015-12-02 14:14:02 Periodic : Run scene “get_from_pi.php”
2015-12-02 14:14:02 Periodic : End

[CoyoteMember]

Hi,

It still not works… I can’t make a “Device Event ==’ in a blocky rule with my Fibaro FGM-001.
I have deleted all files in /web/PulsSation, made a new installation with only minimal services (Zwave)…and made only one ‘beta rule’.. And it doesn’t work.

Here is my rule :

If [ Device Event == [ Event Device : ‘Fibaro_FGM’ value : On ] ].
do [ Device ‘Fibaro_Plug’ switch new value On ]

The detection is oki on the Zwave log file, under the dashboard and under ImperiHome too.. But not in scene services. I can’t use it anymore (I was used to do that before).

In fact, in the scene.log, I never see ‘Event:Scene……’ with the Fibaro_FGM

I’m going to reset (again) the ZWave stick..

Any ideas ?

Thx

JM

[MikaKeymaster]

Can you check that in the “core” log you receive the message when there is a detection?

Can you eventually send me by mail the remote access to your pulsestation?

[CoyoteMember]

Hi Mika,

No message in the core log about detection… But all is oki with the sensor in the dashboard, in ImperiHome, or with Blocky in periodic scene..

I send you by mail datas to reach my NAS… If you can have a look about this problem.

Thx

JMarc

[MarcoparigiParticipant]

Hi all, to inform i got the same problem as Coyote

[MarcoparigiParticipant]

Here is my log on a live log on a motion detection with the fibaro motion sensor :

`2015-12-11 01:20:42.822 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x30, 0x03, 0xff, 0x3f
2015-12-11 01:20:42.823 Detail,
2015-12-11 01:20:42.823 Info, Node002, Received SensorBinary report: Sensor:63 State=On
2015-12-11 01:20:42.823 Detail, Node002, Refreshed Value: old value=false, new value=true, type=bool
2015-12-11 01:20:42.823 Detail, Node002, Changes to this value are not verified
2015-12-11 01:20:42.823 Detail, Node002, Notification: ValueChanged
PHP Warning: parse_ini_file(/volume1/web/PulseStation/services/zwave/../database/config.ini): failed to open stream: No such file or directory in /volume1/web/PulseStation/services/zwave/utils.php on line 280
2015-12-11 01:20:42.896 Info, Notification: Value Changed – Add DB Record for device id zwave-2 and value id 48-user-bool-1-0
2015-12-11 01:20:42.954 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0x0184f3e4`

And on no detection on each minute (scene launching) :

2015-12-11 01:23:00.849 scene : Message received – 1|scene|scene|CHECKSCENESPERIODIC|1449793380789|d63ae0f93ecabf41a9d65d2b9287d906
ps: invalid option — ‘a’
BusyBox v1.16.1 (2015-10-28 13:21:58 CST) multi-call binary.

Usage: ps

Report process status

Options:
w Wide output

ps: invalid option — ‘a’
BusyBox v1.16.1 (2015-10-28 13:21:58 CST) multi-call binary.

Usage: ps

Report process status

Options:
w Wide output

2015-12-11 01:23:00.991 Message In Core : 9|d63ae0f93ecabf41a9d65d2b9287d906|3|scene|HUB|1|CHECKSCENEPERIODIC_OK
{“Root”: { “Response”: { “Status”: “_API_COMMAND_OK_”, “ErrorCode”: “”, “ErrorMessage”: “” }}}2015-12-11 01:23:01.320 Forwarding message : 0|HUB|HUB|AUTORESTART
24835
RUN
NRUN
2015-12-11 01:23:01.451 Message Finished, remove it from the stack (0|HUB|HUB|AUTORESTART)

[K.RensKeymaster]

Hi Marcoparigi,

Do you have the database service installed and set-up correctly to connect to your MariaDb or mysql db?
Since from your log it doesn’t look like it is installed/set-up properly.

Kind regards,
K.Rens

[MikaKeymaster]

As I see your log, I suppose you run the application as “Root” via ssh. dont you ?

[MarcoparigiParticipant]

Hi K.Rens, thank you for your reply.
I am at the office i’ll will check this point in the week-end and update this feed.

[Author]

Posts