Do not ask me how or where to but when I put the plug-in cron 0. 8.8 remove then works plug-in johnny-five 0. 9.11 be fine.
-
CRON plug-in
-
@WimUitTwente said in CRON plug-in:
Do not ask me how or where to but when I put the plug-in cron 0. 8.8 remove then works plug-in johnny-five 0. 9.11 be fine.
If I am getting you right, johnny-five 0. 9.11 does not work fine for you if cron 0. 8.8 is installed. That’s strange, as I have recognised similar so far. Do you get specific error messages if both plugins are installed?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig
17:44:18.484 [pimatic-johnny-five] error: [Board#1] Error: A timeout occurred while connecting to the Board.
17:44:18.484 [pimatic-johnny-five] error:>
17:44:18.484 [pimatic-johnny-five] error:>Please check that you’ve properly flashed the board with the correct firmware.
17:44:18.484 [pimatic-johnny-five] error:>See: https://github.com/rwaldron/johnny-five/wiki/Getting-Started#trouble-shooting
17:44:18.484 [pimatic-johnny-five] error:>
17:44:18.484 [pimatic-johnny-five] error:>If connecting to a Leonardo or Leonardo clone, press the ‘Reset’ button on the board, wait approximately 11 seconds for complete reset, then run your program again.
17:44:18.489 [pimatic-johnny-five] error: [Board#1] Board not ready: A timeout occurred while connecting to the Board.
17:44:18.489 [pimatic-johnny-five] error:>Please check that you’ve properly flashed the board with the correct firmware.
17:44:18.489 [pimatic-johnny-five] error:>See: https://github.com/rwaldron/johnny-five/wiki/Getting-Started#trouble-shooting
17:44:18.489 [pimatic-johnny-five] error:>
17:44:18.489 [pimatic-johnny-five] error:>If connecting to a Leonardo or Leonardo clone, press the ‘Reset’ button on the board, wait approximately 11 seconds for complete reset, then run your program again.
17:44:18.505 [pimatic-johnny-five] error: [Board#1] Error: Board not ready
17:44:18.559 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-2] Error: Board not ready
17:44:18.561 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-3] Error: Board not ready
17:44:18.562 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-4] Error: Board not ready
17:44:18.564 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-5] Error: Board not ready
17:44:18.566 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-6] Error: Board not ready
17:44:18.568 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-7] Error: Board not ready
17:44:18.569 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-8] Error: Board not ready
17:44:18.571 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-9] Error: Board not ready
17:44:18.572 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-10] Error: Board not ready
17:44:18.574 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-11] Error: Board not ready
17:44:18.575 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-12] Error: Board not ready
17:44:18.579 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-2] Error: Unknown
17:44:18.584 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-3] Error: Unknown
17:44:18.586 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-4] Error: Unknown
17:44:18.588 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-5] Error: Unknown
17:44:18.589 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-6] Error: Unknown
17:44:18.591 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-7] Error: Unknown
17:44:18.593 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-8] Error: Unknown
17:44:18.594 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-9] Error: Unknown
17:44:18.596 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-10] Error: Unknown
17:44:18.597 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-11] Error: Unknown
17:44:18.599 [pimatic-johnny-five] error: [JohnnyFiveRelay#relay-pin-12] Error: Unknown
17:44:18.621 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-2.state: undefined
17:44:18.629 [pimatic] warn: Could not update variable relay-pin-2.state: undefined
17:44:18.631 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-3.state: undefined
17:44:18.633 [pimatic] warn: Could not update variable relay-pin-3.state: undefined
17:44:18.634 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-4.state: undefined
17:44:18.635 [pimatic] warn: Could not update variable relay-pin-4.state: undefined
17:44:18.636 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-5.state: undefined
17:44:18.638 [pimatic] warn: Could not update variable relay-pin-5.state: undefined
17:44:18.639 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-6.state: undefined
17:44:18.640 [pimatic] warn: Could not update variable relay-pin-6.state: undefined
17:44:18.641 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-7.state: undefined
17:44:18.642 [pimatic] warn: Could not update variable relay-pin-7.state: undefined
17:44:18.644 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-8.state: undefined
17:44:18.645 [pimatic] warn: Could not update variable relay-pin-8.state: undefined
17:44:18.646 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-9.state: undefined
17:44:18.648 [pimatic] warn: Could not update variable relay-pin-9.state: undefined
17:44:18.649 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-10.state: undefined
17:44:18.650 [pimatic] warn: Could not update variable relay-pin-10.state: undefined
17:44:18.651 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-11.state: undefined
17:44:18.652 [pimatic] warn: Could not update variable relay-pin-11.state: undefined
17:44:18.654 [pimatic-johnny-five, JohnnyFiveRelay] error: Error getting attribute value relay-pin-12.state: undefined
17:44:18.657 [pimatic] warn: Could not update variable relay-pin-12.state: undefined -
Without plug-in cron 0. 8. 8
17:56:07.514 [pimatic] info: Loading plugin: “pimatic-johnny-five” (0.9.11)
17:56:08.884 [pimatic-sunrise] info: Your location is set to lat: 52.385844, long: 6.718505
17:56:09.430 [pimatic] info: New device “De gekozen over en aan tijd”…
17:56:09.471 [pimatic] info: New device “Eenmalig een ruimte verwarmen”…
17:56:09.525 [pimatic] info: New device “Relay 1”…
17:56:09.542 [pimatic] info: New device “Relay 2”…
17:56:09.558 [pimatic] info: New device “Relay 3”…
17:56:09.580 [pimatic] info: New device “Relay 4”…
17:56:09.596 [pimatic] info: New device “Relay 5”…
17:56:09.608 [pimatic] info: New device “Relay 6”…
17:56:09.624 [pimatic] info: New device “Relay 7”…
17:56:09.636 [pimatic] info: New device “Relay 8”…
17:56:09.650 [pimatic] info: New device “Relay 1B”…
17:56:09.671 [pimatic] info: New device “Relay 2B”…
17:56:09.690 [pimatic] info: New device “Relay 3B”…
17:56:09.719 [pimatic] info: New device “Panelen boven”…jonny-five then works 100%
The problem is that I have the CRON plugin very necessary17:56:38.037 [pimatic] error: Could not parse rule “when it is 00:55 and Overloop Lamp is on then switch OverloopLamp off and switch quigg3-1 off”: Could not find an provider that decides next predicate of “it is 00:55 and Overloop Lamp is on”.
17:56:38.092 [pimatic] error: Could not parse rule “when it is 00:02 and Stopc_Boven is turned on then switch Stopc_Boven off”: Could not find an provider that decides next predicate of “it is 00:02 and Stopc_Boven is turned on”.
17:56:38.096 [pimatic] error: Could not parse rule “when [it is 23:45 or it is 23:57] and kachel_woonkamer is turned on then switch kachel_woonkamer off”: Could not find an provider that decides next predicate of “it is 23:45 or it is 23:57] and kachel_woonkamer is turned on”., Expected closing parenthese ("]") at end.
17:56:38.100 [pimatic] error: Could not parse rule “when saturday 07:40 and $temperatuur-badkamer.temperature < 17 then switch verwarming-badkamer on for 50 minutes”: Could not find an provider that decides next predicate of “saturday 07:40 and $temperatuur-badkamer.temperature < 17”.
17:56:38.103 [pimatic] error: Could not parse rule “when sunday 07:50 and $temperatuur-badkamer.temperature < 17 then switch verwarming-badkamer on for 60 minutes”: Could not find an provider that decides next predicate of “sunday 07:50 and $temperatuur-badkamer.temperature < 17”.
17:56:38.106 [pimatic] error: Could not parse rule “when 23:20 and $temperatuur-slaapkamer.temperature < 17 then switch verwarming-slaapkamer on for 50 minutes”: Could not find an provider that decides next predicate of “23:20 and $temperatuur-slaapkamer.temperature < 17”.
17:56:38.110 [pimatic] error: Could not parse rule “when it is 16:58 then switch HP printer bij Marijke off after 2 minutes”: Could not find an provider that decides next predicate of “it is 16:58”.
17:56:38.113 [pimatic] error: Could not parse rule “when it is 00:03 and drie_spotjes_kamerboven is turned on then turn drie_spotjes_kamerboven off”: Could not find an provider that decides next predicate of “it is 00:03 and drie_spotjes_kamerboven is turned on”.
17:56:38.117 [pimatic] error: Could not parse rule “when kachel_woonkamer is turned on and its before 22:45 and $kamer-tmp-boven.temperature >= 20 then switch kachel_woonkamer off for 10 minutes”: Could not find an provider that decides next predicate of “its before 22:45 and $kamer-tmp-boven.temperature >= 20”., Expected a new predicate after last “and”.
17:56:38.121 [pimatic] error: Could not parse rule “when it is 00:02 and Radio kamer boven is turned on then turn Radio kamer boven off”: Could not find an provider that decides next predicate of “it is 00:02 and Radio kamer boven is turned on”.
17:56:38.124 [pimatic] error: Could not parse rule “when Radio kamer boven is turned off and Woonkamerbeweging is opened and its after 16:30 and its before 18:00 then turn Radio kamer boven on”: Could not find an provider that decides next predicate of “its after 16:30 and its before 18:00”., Expected a new predicate after last “and”.
17:56:38.128 [pimatic] error: Could not parse rule “when [23:30 or 07:25] and Radio Slaapkamer is turned off then switch Radio Slaapkamer on”: Could not find an provider that decides next predicate of “23:30 or 07:25] and Radio Slaapkamer is turned off”., Expected closing parenthese ("]") at end.
17:56:38.131 [pimatic] error: Could not parse rule “when [01:06 or 09:05] and Radio Slaapkamer is turned on then switch Radio Slaapkamer off”: Could not find an provider that decides next predicate of “01:06 or 09:05] and Radio Slaapkamer is turned on”., Expected closing parenthese ("]") at end.
17:56:38.134 [pimatic] error: Could not parse rule “when KachelBenMid is turned on and its before 15:45 and $mid-tmp-beneden.temperature >= 19.5 then switch KachelBenMid off for 10 minutes”: Could not find an provider that decides next predicate of “its before 15:45 and $mid-tmp-beneden.temperature >= 19.5”., Expected a new predicate after last “and”.
