have you tried to remove and install the plugin again?
but doesn’t seem to be an issue of that.
maybe @sweetpi has a clue?
-
Pimatic-LCD error Cannot write to device at i2c.writeByte
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@leader21 Thank you for hint. I have already tried pimatic complete reinstall - issue still persists.
-
Is this 5 seconds interval necessary? I think it is to fast.
pimatic rocks!!!
-
It is needed because of current time parameter. I have tested also with 30 seconds, just prolonged working period and then the same error.
-
I had this problem, too with bad connections / too long / too thin wires. It’s most probably a timing issue. I need to add some delays to the write actions. Watch the github issue for updates.
-
Hi @sweetpi, Thank you for update
Yesterday at 18:00 I have enabled rule
every 30s -display “$pilight-living-temp3.temperatureC,$pilight-living-temp3.humidity% $pilight-living-temp2.temperatureC,$pilight-living-temp2.humidity%” on lcd line 1 and display “NP:$nocni_proud” on lcd line 4 after 5 seconds
No write errors so far. It looks more stable with longer intervals.
My connection is PI - 15 cm wires - logic level converter (3.3-5V) - 15 cm wires - LCD. I use some standard wires to breadboard from ebay. I dont think that it could be wire issue because lcd continue working with some python script. Stop with write error just in pimatic.
Do you mean pimatic-lcd gifthub https://github.com/pimatic/pimatic-lcd? Will you update write action delays or should I do it myself? If so can you help me howto to this.
Kind regards, Michal -
Hi @sweetpi , the current situation is so that when I use 30 seconds interval for update pimatic runs about one day. Then is has to be restarted because of cannot write to device error. Can you try change timing?
Thank you. Michal -
I’ve added some delays, the code is know pretty close to the python code.
@misakm Could you test if its working now more reliable for you?
-
Hi,
I have received arduino nano, connected rf transmitter and receiver and now it looks that I have power consumption issues. It is so that I have write issue to LCD and homedruino has no enought power to control devices on longer distance. Range is much more better when LCD is disconnected.
I have raspberry pi b rev2, 2A power supply, wifi adapter, 2004 LCD, IR - Transmitter, receiver and RF Transmitter, receiver with attiny45 for pilight. Two RF solutions just temporally till all devices will be migrated to homedruino.Does anybody has experiences with USB active hub with capabilities to also power my raspberry? Do you know if power management is better for raspberry pi 2? I think that my 2 A power supply should be enough but it looks that raspberry cannot handle it. I have seen some tutorials how to hack power limitation but it looks danger solder some wires to rpi board.
Thank you for any help.
BR, Michal -
I have done more tests with pimatic-lcd and still having the issue when update lcd more often. Is also consumes a lot of cpu when rule is executed. Thank you for help but I have decided not to use LCD anymore. In future I plan use tablet as display probably with tasker.