Arctic Hare mod by Jussi

bernard · 13 Mai 2020

Hi.
Can you post your python schell terminal result
I Don't understand HOW you send Something from lovelace to mower over mqtt.
It's work perfectly to receive the sensor,battery,idle etc... but to send Command ????
How did you create the subfolder and the command /send part into iobroker and lovelace?

Into the code it's easy to test the 2 parts (with or without the /)

But to test it i need to send Something with IObroker.

stockfisch · 13 Mai 2020

Hello
Your software is doing funny things

A few minutes ago i tried to catch your python terminal result.
So i activated back the log function (the on_log and on_publish show debug message in terminal)
After starting PiArdu318 this was outcome:
Python terminal:

Code:

pi@raspberrypi:~/Documents/PiArdumower $ sudo python3 PiArdu318.py
Linux Platform
pygame 1.9.4.post1
Hello from the pygame community. https://www.pygame.org/contribute.html
Find Serial on ttyACM0
b''
RFID file loaded OK
refresh setting timer
PING 192.168.7.218 (192.168.7.218) 56(84) bytes of data.
64 bytes from 192.168.7.218: icmp_seq=1 ttl=64 time=2.94 ms

--- 192.168.7.218 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.937/2.937/2.937/0.000 ms
log:  Sending CONNECT (u1, p1, wr0, wq0, wf0, c1, k60) client_id=b'Ardumower'
log:  Received CONNACK (1, 0)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Sending PUBLISH (d0, q0, r0, m1), 'b'Mower/Status'', ... (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m2), 'b'Mower/State'', ... (3 bytes)
log:  Sending PUBLISH (d0, q0, r0, m3), 'b'Mower/Battery'', ... (5 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m4), 'b'Mower/Status'', ... (10 bytes)
log:  Sending PUBLISH (d0, q0, r0, m5), 'b'Mower/State'', ... (4 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m6), 'b'Mower/Status'', ... (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m7), 'b'Mower/State'', ... (3 bytes)
log:  Sending PUBLISH (d0, q0, r0, m8), 'b'Mower/Idle'', ... (5 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m9), 'b'Mower/Status'', ... (10 bytes)
log:  Sending PUBLISH (d0, q0, r0, m10), 'b'Mower/State'', ... (4 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m11), 'b'Mower/Status'', ... (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m12), 'b'Mower/State'', ... (3 bytes)
log:  Sending PUBLISH (d0, q0, r0, m13), 'b'Mower/Idle'', ... (4 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m14), 'b'Mower/Status'', ... (10 bytes)
log:  Sending PUBLISH (d0, q0, r0, m15), 'b'Mower/State'', ... (4 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m16), 'b'Mower/Status'', ... (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m17), 'b'Mower/State'', ... (3 bytes)
log:  Sending PUBLISH (d0, q0, r0, m18), 'b'Mower/Idle'', ... (5 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m19), 'b'Mower/Status'', ... (10 bytes)
log:  Sending PUBLISH (d0, q0, r0, m20), 'b'Mower/State'', ... (4 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Sending PUBLISH (d0, q0, r0, m21), 'b'Mower/Idle'', ... (5 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m22), 'b'Mower/Status'', ... (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m23), 'b'Mower/State'', ... (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/VIDEO', ...  (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m24), 'b'Mower/Status'', ... (10 bytes)
log:  Sending PUBLISH (d0, q0, r0, m25), 'b'Mower/State'', ... (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m26), 'b'Mower/Idle'', ... (5 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m27), 'b'Mower/Status'', ... (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m28), 'b'Mower/State'', ... (3 bytes)
log:  Received PUBLISH (d0, q0, r1, m0), 'Mower/COMMAND/SEND', ...  (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m29), 'b'Mower/Status'', ... (10 bytes)
log:  Sending PUBLISH (d0, q0, r0, m30), 'b'Mower/State'', ... (4 bytes)
log:  Sending PUBLISH (d0, q0, r0, m31), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m32), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m33), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m34), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m35), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m36), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m37), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m38), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m39), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m40), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m41), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m42), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PINGREQ
log:  Received PINGRESP
log:  Sending PUBLISH (d0, q0, r0, m43), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m44), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m45), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m46), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m47), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m48), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m49), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m50), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m51), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m52), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m53), 'b'Mower/Idle'', ... (5 bytes)
log:  Sending PUBLISH (d0, q0, r0, m54), 'b'Mower/Idle'', ... (5 bytes)

The console:

Code:

19:09:22 MQTT send message Mower/Idle 22659
19:09:17 MQTT send message Mower/Idle 22628
19:09:12 MQTT send message Mower/Idle 22677
19:09:08 Stop Video streaming
19:09:08 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:09:08 Reception message MQTT...
19:09:07 MQTT send message Mower/Idle 22735
19:09:02 MQTT send message Mower/Idle 23745
19:09:00 Topic : Mower/COMMAND/VIDEO Data  : b'TEST'
19:09:00 Reception message MQTT...
19:08:57 MQTT send message Mower/Idle 23815
19:08:52 MQTT send message Mower/Idle 13413
19:08:51 MQTT send message Mower/State STAT
19:08:51 STATION / STAT Dir 0 State changed at 30665454 From state OFF

19:08:51 MQTT send message Mower/Status IN_STATION
19:08:49 MQTT send message Mower/State OFF
19:08:49 WAIT / OFF  Dir 0 State changed at 30663451 From state STAT

19:08:49 Robot Stats address Stop = 826

19:08:49 Robot Stats address Start = 800

19:08:49 Save Robot Stats

19:08:49 MQTT send message Mower/Status WAIT
19:08:49 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:08:49 Reception message MQTT...
19:08:47 MQTT send message Mower/Idle 22708
19:08:42 MQTT send message Mower/Idle 22680
19:08:37 Topic : Mower/COMMAND/SEND Data  : b'TEST'
19:08:37 Reception message MQTT...
19:08:37 MQTT send message Mower/Idle 22678
19:08:32 MQTT send message Mower/Idle 22655
19:08:27 MQTT send message Mower/Idle 22682
19:08:22 MQTT send message Mower/Idle 22683
19:08:17 MQTT send message Mower/Idle 22577
19:08:12 MQTT send message Mower/Idle 22583
19:08:07 MQTT send message Mower/Idle 22665
19:08:02 MQTT send message Mower/Idle 22667
19:07:57 MQTT send message Mower/Idle 22662
19:07:52 MQTT send message Mower/Idle 22693
19:07:47 MQTT send message Mower/Idle 22709
19:07:42 MQTT send message Mower/Idle 22558
19:07:37 MQTT send message Mower/Idle 22678
19:07:32 MQTT send message Mower/Idle 22694
19:07:27 MQTT send message Mower/Idle 22617
19:07:22 MQTT send message Mower/Idle 22668
19:07:17 MQTT send message Mower/Idle 22709
19:07:11 MQTT send message Mower/Idle 22600
19:07:06 MQTT send message Mower/Idle 22683
19:07:01 MQTT send message Mower/Idle 22694
19:06:56 MQTT send message Mower/Idle 22569
19:06:51 MQTT send message Mower/Idle 22684
19:06:46 MQTT send message Mower/Idle 22694
19:06:41 MQTT send message Mower/Idle 22579
19:06:36 MQTT send message Mower/Idle 22608
19:06:31 MQTT send message Mower/Idle 22669
19:06:26 MQTT send message Mower/Idle 22694
19:06:21 MQTT send message Mower/Idle 22693
19:06:16 MQTT send message Mower/Idle 22691
19:06:11 MQTT send message Mower/Idle 22689
19:06:06 MQTT send message Mower/Idle 23634
19:06:01 MQTT send message Mower/Idle 23759
19:05:56 MQTT send message Mower/Idle 17599
19:05:55 MQTT send message Mower/State STAT
19:05:55 STATION / STAT Dir 0 State changed at 30489139 From state OFF

19:05:55 MQTT send message Mower/Status IN_STATION
19:05:54 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:54 Reception message MQTT...
19:05:53 MQTT send message Mower/State OFF
19:05:53 WAIT / OFF  Dir 0 State changed at 30487138 From state STAT

19:05:53 Robot Stats address Stop = 826

19:05:53 Robot Stats address Start = 800

19:05:53 Save Robot Stats

19:05:53 MQTT send message Mower/Status WAIT
19:05:52 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:52 Reception message MQTT...
19:05:51 MQTT send message Mower/Idle 23685
19:05:49 MQTT send message Mower/State STAT
19:05:49 STATION / STAT Dir 0 State changed at 30483142 From state OFF

19:05:49 MQTT send message Mower/Status IN_STATION
19:05:49 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:49 Reception message MQTT...
19:05:48 Stop Video streaming
19:05:48 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:48 Reception message MQTT...
19:05:47 MQTT send message Mower/State OFF
19:05:47 WAIT / OFF  Dir 0 State changed at 30481141 From state STAT

19:05:47 Robot Stats address Stop = 826

19:05:47 Robot Stats address Start = 800

19:05:47 Save Robot Stats

19:05:46 MQTT send message Mower/Status WAIT
19:05:46 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:46 Reception message MQTT...
19:05:46 Stop Video streaming
19:05:46 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:46 Reception message MQTT...
19:05:46 MQTT send message Mower/Idle 23665
19:05:44 Stop Video streaming
19:05:44 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:44 Reception message MQTT...
19:05:43 MQTT send message Mower/State STAT
19:05:43 STATION / STAT Dir 0 State changed at 30477150 From state OFF

19:05:43 MQTT send message Mower/Status IN_STATION
19:05:43 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:43 Reception message MQTT...
19:05:42 Stop Video streaming
19:05:42 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:42 Reception message MQTT...
19:05:41 MQTT send message Mower/Idle 23721
19:05:41 MQTT send message Mower/State OFF
19:05:41 WAIT / OFF  Dir 0 State changed at 30475149 From state STAT

19:05:41 Robot Stats address Stop = 826

19:05:41 Robot Stats address Start = 800

19:05:41 Save Robot Stats

19:05:41 MQTT send message Mower/Status WAIT
19:05:40 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:40 Reception message MQTT...
19:05:40 Stop Video streaming
19:05:40 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:40 Reception message MQTT...
19:05:38 Stop Video streaming
19:05:38 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:38 Reception message MQTT...
19:05:37 MQTT send message Mower/State STAT
19:05:37 STATION / STAT Dir 0 State changed at 30471142 From state OFF

19:05:37 MQTT send message Mower/Status IN_STATION
19:05:37 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:37 Reception message MQTT...
19:05:37 Stop Video streaming
19:05:37 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:37 Reception message MQTT...
19:05:36 MQTT send message Mower/Idle 9677
19:05:35 MQTT send message Mower/State OFF
19:05:35 WAIT / OFF  Dir 0 State changed at 30469141 From state STAT

19:05:35 Robot Stats address Stop = 826

19:05:35 Robot Stats address Start = 800

19:05:35 Save Robot Stats

19:05:34 MQTT send message Mower/Status WAIT
19:05:34 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:34 Reception message MQTT...
19:05:34 Stop Video streaming
19:05:34 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:34 Reception message MQTT...
19:05:33 MQTT send message Mower/State STAT
19:05:33 STATION / STAT Dir 0 State changed at 30467149 From state OFF

19:05:33 MQTT send message Mower/Status IN_STATION
19:05:33 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:33 Reception message MQTT...
19:05:32 Stop Video streaming
19:05:32 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:32 Reception message MQTT...
19:05:31 MQTT send message Mower/Idle 19018
19:05:31 ------ LOOP NOT OK DUE IS OVERLOAD -- Over 1 sec 254

19:05:31 MQTT send message Mower/State OFF
19:05:31 WAIT / OFF  Dir 0 State changed at 30465148 From state STAT

19:05:31 Robot Stats address Stop = 826

19:05:31 Robot Stats address Start = 800

19:05:31 Save Robot Stats

19:05:31 MQTT send message Mower/Status WAIT
19:05:30 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:30 Reception message MQTT...
19:05:30 Stop Video streaming
19:05:30 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:30 Reception message MQTT...
19:05:30 MQTT send message Mower/State STAT
19:05:30 STATION / STAT Dir 0 State changed at 30463621 From state OFF

19:05:29 MQTT send message Mower/Status IN_STATION
19:05:29 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:29 Reception message MQTT...
19:05:29 Stop Video streaming
19:05:29 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:29 Reception message MQTT...
19:05:28 ------ LOOP NOT OK DUE IS OVERLOAD -- Over 1 sec 266

19:05:28 MQTT send message Mower/Battery 29.29
19:05:28 MQTT send message Mower/State OFF
19:05:28 WAIT / OFF  Dir 0 State changed at 30461618 From state STAT

19:05:28 Robot Stats address Stop = 826

19:05:27 Robot Stats address Start = 800

19:05:27 Save Robot Stats

19:05:27 MQTT send message Mower/Status WAIT
19:05:27 Stop Video streaming
19:05:27 Topic : Mower/COMMAND/VIDEO Data  : b'OFF'
19:05:27 Reception message MQTT...
19:05:27 Topic : Mower/COMMAND/SEND Data  : b'STOP'
19:05:27 Reception message MQTT...
19:05:27 MQTT connected
19:05:27 MQTT Connecting Please Wait
19:05:27 Broker OK
19:05:27 PING Broker
19:05:27 MQTT not connected retry each 2 minutes
19:04:27 Initial start MQTT after 1 minute
19:04:27 Wait update Date/Time from internet
19:04:27 Read Area In Mowing from PCB1.3
19:04:27 Read Setting from PCB1.3

I dont know why he 10 times repeat one state. But after 10 times doing same he is more silent. Only idle messages.
Here i sended payload TEST for VIDEO: 19:09:00 Topic : Mower/COMMAND/VIDEO Data : b'TEST'
Reason is that i dont have cam actually but only changed states will be sended.
Then i sended payload OFF for VIDEO: 19:09:08 Topic : Mower/COMMAND/VIDEO Data : b'OFF'
I got the right answer from PiArdu: 19:09:08 Stop Video streaming
Before i tried same steps with my new SEND topic:
19:08:49 MQTT send message Mower/Status WAIT
19:08:49 Topic : Mower/COMMAND/SEND Data : b'STOP'
19:08:49 Reception message MQTT...
19:08:47 MQTT send message Mower/Idle 22708
19:08:42 MQTT send message Mower/Idle 22680
19:08:37 Topic : Mower/COMMAND/SEND Data : b'TEST'
19:08:37 Reception message MQTT...

So the payload TEST is only to have a change in payload. Otherwise iobroker will not sending mqtt messages.
In moment i dont want to send a START because it is raining.
Do you have an idea for the ~10 times same reaction? It is a cache or buffer?
Thanks and best
Bjoern

bernard · 13 Mai 2020

Do you have an idea for the ~10 times same reaction? It is a cache or buffer?

Certainly cache,maybe check if the qos or ack are everywhere to 0 or not active.
This behaviour is not present into HASSIO.

It's rain also here .So i use the stop button to test.
When click on it you need to see the status and state change into iobroker if it work.
I have Added the starttimer function into Piardu319.py but it's rain so not possible to test.

The new fonction need change into Pfod.cpp and rpiremote.cpp.
When you are OK tell me the correct Topic you want to use

stockfisch · 14 Mai 2020

Hello
Crazy, today i can not send to mower. No changes to yesterday.
In moment i have to make a break because i will get a new house heating system.
I have to spend my worktime to this project. :-(
Will go on next days...
Thanks and stay healthy!
Bjoern

jussip · 14 Mai 2020

Almost there, few things to figure out.. One timer works fine but things get more complicate if multiple timers are used

RTC errors again

Errors occur when mowing motors are on. maybe those causes some interference or tinyrtc is piece of s**t. Any other options?

Something strange with rfid's, mower find all tags but nothing happens?? Are these settings correct? Speed tag is front of station and others are 'short cuts'
Edit: status should be BACK_TO_STATION, not TRACK_TO_START

bernard · 14 Mai 2020

or tinyrtc is piece of s**t.

Yes.
I see this when the mower stay without power for 3 months but after set the time and date with arduremote All work correctly.
But when i start the first PCB 3 of these PCB won't work correctly and after i find 2 that work very well since 2 years.

For RFID there is Something strange into your setting.
But maybe possible,You want to start and immediatly return to station when find a tag?
When mower find a tag it search in the database the tagID AND the actual status of mower
The status is used to make the choise ,so all your tag are only manage when the mower TRACK_TO_START and the toDO RTS is return to station ???
For the last one replace the TRACK_TO START by BACK_TO_STATION

Here example setting

when the bat is low or mower return to Home
the status is BACK_TO_STATION
So when mower find a tag 72B8DB95 for example it's OK tagID and Status match in the database.
toDo is RTS ,so the mower stop to tarck,leave the wire at 28 degres and run at pwm 250 to find again the wire.
If it find B0CEDB95 Nothing append ,because the status not match.

when mower start from station
the status is TRACK_TO_START
So when mower find a tag 8EB3DB95 for example it's OK tagID and Status match in the database.
toDo is SPEED ,so the mower track the wire at PWM=255 for distance of 25 meters

If it find 4082DA95 Nothing append ,because the status not match.
This tag 4082DA95 is locate 1 meter before the station to brake before docking

The toDo can only be:
['RTS','FAST_START','SPEED','NEW_AREA']
The status can only be:
[ "BACK_TO_STATION", "TRACK_TO_START", "REMOTE","WIRE_MOWING"]

In the console normaly the message explain if the data Match or not
Maybei need to write a message more explicit.

jussip · 14 Mai 2020

Only console message was '17:31:49 Find a tag : A7D725BE' nothing else rfid related. but it work now for sure with 'BACK_TO_STATION'. with RTS only angle1 and speed is used?
RTC battery is ok and it's not lose time/date

bernard · 14 Mai 2020

jussip schrieb:
Only console message was '17:31:49 Find a tag : A7D725BE' nothing else

It's very Strange,Here the normal message for no match tag.
The mower start from station and when reverse it read the tag use to reduce speed for docking and skip it

20:35:21 TRACKTOSTART / STROL
20:35:14 Are not present in the database
20:35:14 Status : TRACK_TO_START
20:35:14 RFID Tag : 4082DA95
20:35:14 Find a tag : 4082DA95
20:35:12 TRACKTOSTART / STREV
20:35:12 MQTT START FROM STATION
20:35:12 Topic : Mower/COMMAND/ Data : b'STARTTIMER;1;3;1;8;1;5'
20:35:12 Reception message MQTT...

and here 2 tag, one for fast return RTS and the one use to reduce speed before docking.

20:39:54 STATION / STAT
20:39:54 Robot Stats address Stop = 826
20:39:54 Robot Stats address Start = 800
20:39:54 Save Robot Stats
20:39:54 Charge Voltage detected
20:39:52 BACKTOSTATION / STCHK
20:39:52 Detect a voltage on charging contact check if it's the station
20:39:51 Set New perimeter tracking speed 80
20:39:51 Change speed for 200 centimeters
20:39:51 RFID change tracking speed
20:39:51 RFID Tag find ToDO is: SPEED
20:39:51 Find a tag : 4082DA95
20:39:44 BACKTOSTATION / PTRK
20:39:42 BACKTOSTATION / ROLLSTOPTOTRACK
20:39:41 BACKTOSTATION / ROLLTOTRACK
20:39:41 BACKTOSTATION / STOPTOTRACK
20:39:40 Not inside so start to track the wire
20:39:15 BACKTOSTATION / PFND
20:39:15 Area In Mowing 1 Area To Go 1
20:39:14 BACKTOSTATION / ROLLTOTAG
20:39:14 New PeriFind Heading 99.25
20:39:14 Actual Heading 39.25
20:39:13 BACKTOSTATION / TRACKSTOP
20:39:13 RFID Find faster return
20:39:13 RFID Tag find ToDO is: RTS
20:39:13 Find a tag : 91B3DB95
20:39:08 BACKTOSTATION / PTRK

Can you send me the yaml and lovelace code parts for Timer using private message

jussip · 14 Mai 2020

Yes I can but automation part's need more work

bernard · 14 Mai 2020

Certainly but i want to use this kind of scheduler for my garden sprinkler automation, so i check and it's not a problem if it's not working for mower
I hope sprinkler is more easy to integrate into HA

jussip · 15 Mai 2020

I have something wrong in code, rfid tag found but nothing else. What files I need to check? PiArdu.py, rpiremote, talker.py

bernard · 16 Mai 2020

It's difficult to say if you Don't use exactly my code ,But :
The rfid board is connected and read by ESP32
ESP 32 send tag id to DUE and DUE do Nothing ,Simply transmit it to Piardu (Do not forget to activate it into setting GPS/RFID).
You can see into arduremote setting RFID the last tag read. to confirm the reader is OK

Piardu check the tagID and status and send back to the DUE what to do.

So Check if it is activate using arduremote
Or check Piardu.
I never see any trouble with RFID on my 2 running mower so certainly Something is wrong in the config.

Show me one RFID code config and what you want to do with it to check if possible.

jussip · 16 Mai 2020

I think problem founded. I had updated talker.py in PiArdumower folder and pynmea2/types/talker.py w/o class rfi
Did you got PM?

bernard · 16 Mai 2020

Yes i see your PM and check during Week end.
Hope i can work on my sprinkler (The sun is back

)
RFI class is mandatory into talker.py to use RFID ,but normaly without this class an error or message occur ?

jussip · 16 Mai 2020

Actually imu class was missing too and no errors

bernard · 16 Mai 2020

The Imu class is used in the plot stetting
You can only see this into plot page of Piardu3523.py from branch robomow for small screen solftware.
Also the RFID page is new into this version

(Not really tested)
Your yaml are

but Strange behaviour in the Schedule test automation
I add it to GitHub.

jussip · 16 Mai 2020

Stop automation is totally untested. Start works what I tested it (but not real, just with that test sensor)
Maybe it's better do stop just once or some narrow time frame.

bernard · 16 Mai 2020

I test it actualy in real.
The command line work perfectly with the var.

But I thing Something is not ok into:

Code:

conditions:
            - condition: template
              value_template: "{{ now().strftime('%H:%M') < states('input_datetime.mower_timer1_start_time') }}"
            - condition: template
              value_template: "{{ now().strftime('%H:%M') >= states('input_datetime.mower_timer1_stop_time') }}"

Because sometimes it's OK but not Always ??

jussip · 16 Mai 2020

You can test it 'developer tools' -> 'template' and paste there

Code:

{{ now().strftime('%H:%M') < states('input_datetime.mower_timer1_start_time') }}
{{ now().strftime('%H:%M') }}
{{ states('input_datetime.mower_timer1_start_time') }}

it should return true or false, or values etc..

bernard · 16 Mai 2020

I am stupid
Time Zone was not OK

Arctic Hare mod by Jussi

Well-known member

Member

Well-known member

Member

Member

Well-known member

Member

Well-known member

Member

Well-known member

Member

Well-known member

Member

Well-known member

Member

Well-known member

Member

Well-known member

Member

Well-known member