Vera3 UI5 MySensors Plugin not working after migration to 1.4
-
Replacing the gateway with another arduino seems to have fixed the inclusion. At least now it reacts although not able to find any devices.
Also I noticed that even though most of the sensor sendings fail still some go through ok but very rarely:
sensor started, id 1
send: 1-1-0-0 s=255,c=0,t=17,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,st=fail:0
send: 1-1-0-0 s=255,c=3,t=11,pt=0,l=0,st=fail:
send: 1-1-0-0 s=255,c=3,t=12,pt=0,l=3,st=fail:1.5
send: 1-1-0-0 s=0,c=0,t=7,pt=0,l=3,st=fail:1.4
send: 1-1-0-0 s=1,c=0,t=6,pt=0,l=3,st=fail:1.4
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=ok:25.0
send: 1-1-0-0 s=1,c=1,t=1,pt=7,l=5,st=ok:50.8
send: 1-1-0-0 s=2,c=1,t=1,pt=7,l=5,st=ok:25.3
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=fail:24.9
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=fail:25.0
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=fail:24.9
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=fail:25.0
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=fail:24.9
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=fail:25.0
send: 1-1-0-0 s=1,c=1,t=1,pt=7,l=5,st=fail:50.7Still those ok sends do not update the UI5.
Has the radio power been lowered between 1.3 and 1.4?
I even now have a repeated node between the sensor and gateway, but that does not seem to make any difference..
-
@samppa said:
Has the radio power been lowered between 1.3 and 1.4?
No.
Please describe your setup. Radio model?, capacitors mounted?, cable length between radio/arduino?
-
@hek
Tough questions for newbie.. :-) The radio is from the buying guide, no capacitors and 10cm dupont cables. -
Try adding capacitor as suggested. The latest discussions on the forum recommends a larger one than the one we link on buying guide (I will update the links soon).
Here are some assorted electrolytic with different capacitance.
-
@hek
Why it is needed for 1.4 as earlier everything worked well in 1.3 without it?
I do not have any readily available and I was hoping to get back up again without waiting for the delivery. -
This version transmits bursts of messages which probably requires more power for a short period.
Try lowering transmit power in MyConfig.h while waiting for the capacitors. -
Try adding capacitor as suggested. The latest discussions on the forum recommends a larger one than the one we link on buying guide (I will update the links soon).
Here are some assorted electrolytic with different capacitance.
-
@samppa said:
#define RF24_PA_LEVEL RF24_PA_LOWDid not help.. ;-(
Perhaps I have to wait for the capacitors..
Somehow the first message (with version) seems to go through more often than the rest.. -
Don't you have some old electronics you could butcher and desolder a couple of capacitors from? Or a nearby shop? Waiting 2 weeks for the Chinese/Finnish post isn't that fun.
-
@hek
Yes I could do that. What size? Anything goes, right? Thee discussion in the post you liked was rather long without definitive conclusion.. :-) -
@samppa
Just to confirm; the capacitor should be put to sensor node or serial gateway? Or both and all nodes?
And in parallel with the radio on the power lines? -
@hek
Ok that made the radio to work.
But still the reported values are not shown in UI5.
Somehow the Humidity sensor has CurrentTemperature variable, so it seems something is mixed up..
I have one DHT22 and one Dallas temperature sensor in one node. The devices are found during inclusion and added, but no data is shown. The only thing shown is the last update time that seems to be correct.. -
@hek
Here is how it looks on Sensor:
sensor started, id 1
send: 1-1-0-0 s=255,c=0,t=17,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,st=ok:0
read: 0-0-1 s=255,c=3,t=6,pt=0,l=2:M
send: 1-1-0-0 s=255,c=3,t=11,pt=0,l=0,st=ok:
send: 1-1-0-0 s=255,c=3,t=12,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=0,c=0,t=7,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=1,c=0,t=6,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=2,c=0,t=6,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=ok:77.9
send: 1-1-0-0 s=1,c=1,t=1,pt=7,l=5,st=ok:43.1
send: 1-1-0-0 s=2,c=1,t=1,pt=7,l=5,st=ok:78.1
send: 1-1-0-0 s=1,c=1,t=1,pt=7,l=5,st=ok:43.0
send: 1-1-0-0 s=1,c=1,t=1,pt=7,l=5,st=ok:42.7So the transmission seems to be ok..
-
@hek
Here is how it looks on Sensor:
sensor started, id 1
send: 1-1-0-0 s=255,c=0,t=17,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,st=ok:0
read: 0-0-1 s=255,c=3,t=6,pt=0,l=2:M
send: 1-1-0-0 s=255,c=3,t=11,pt=0,l=0,st=ok:
send: 1-1-0-0 s=255,c=3,t=12,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=0,c=0,t=7,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=1,c=0,t=6,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=2,c=0,t=6,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=ok:77.9
send: 1-1-0-0 s=1,c=1,t=1,pt=7,l=5,st=ok:43.1
send: 1-1-0-0 s=2,c=1,t=1,pt=7,l=5,st=ok:78.1
send: 1-1-0-0 s=1,c=1,t=1,pt=7,l=5,st=ok:43.0
send: 1-1-0-0 s=1,c=1,t=1,pt=7,l=5,st=ok:42.7So the transmission seems to be ok..
The mixup with temp and humidity was my typo in code. It would be great if the gateway or sensor would warn if a wrong type of value is sent compared to the presented sensor type.
@samppa said:
Here is how it looks on Sensor:
sensor started, id 1
send: 1-1-0-0 s=255,c=0,t=17,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,st=ok:0
read: 0-0-1 s=255,c=3,t=6,pt=0,l=2:M
send: 1-1-0-0 s=255,c=3,t=11,pt=0,l=0,st=ok:
send: 1-1-0-0 s=255,c=3,t=12,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=0,c=0,t=7,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=1,c=0,t=6,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=2,c=0,t=6,pt=0,l=3,st=ok:1.4
send: 1-1-0-0 s=0,c=1,t=0,pt=7,l=5,st=ok:77.9That temeprature is in Farenheit. Somehow the GW responds false when calling:
metric = gw.getConfig().isMetric;Now everything else except the metric works with this node..
-
It would be great if the gateway or sensor would warn if a wrong type of value is sent compared to the presented sensor type.
It has no knowledge of this today. We're having discussions about the future elsewhere on this forum.
@samppa said:
Now everything else except the metric works with this node..
Did you see this update?
http://forum.mysensors.org/topic/326/mysensors-1-4-released/34
-
It would be great if the gateway or sensor would warn if a wrong type of value is sent compared to the presented sensor type.
It has no knowledge of this today. We're having discussions about the future elsewhere on this forum.
@samppa said:
Now everything else except the metric works with this node..
Did you see this update?
http://forum.mysensors.org/topic/326/mysensors-1-4-released/34
btw: thanks for the great help and outstanding forum!
@hek said:
Did you see this update?
http://forum.mysensors.org/topic/326/mysensors-1-4-released/34
It had no reference to isMetric is it broken or am I misusing it somehow?
In the migration guide it said:
metric = gw.isMetricSystem();
change to
metric = gw.getConfig().isMetric;
But I get false even though the seting is metric (and not Imperial) in Vera Plugin 1.4. Weird..