Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only one way comunication #47

Closed
cyclemat opened this issue May 24, 2024 · 6 comments
Closed

Only one way comunication #47

cyclemat opened this issue May 24, 2024 · 6 comments

Comments

@cyclemat
Copy link

Have an Problem i have all running but i only become the informations from the Pool temp/on/Off als information are Updated in the Broker but when i send on Off or Set temp Nothing Happens i used this Level shifter
https://www.ebay.de/itm/152409796871?mkcid=16&mkevt=1&mkrid=707-127634-2357-0&ssspo=UA5LzFM4QMO&sssrc=4429486&ssuid=0HguCZJXT4u&var=&widget_ver=artemis&media=COPY

Can the Level shifter be the the Problem ?

@cyclemat
Copy link
Author

IMG_20240524_115859.jpg

Hier das model

@Elektroarzt
Copy link
Collaborator

Could be an issue in the whole signal path. Not easy to say if it's the level shifter. If you have to debug without oscilloscope (I assume you don't have one at hand), it could be straight forward to flash tasmota temporarily as test firmware and toggle the output pins statically on and off via its web interface and measure along the path with a multimeter to see where the signal is lost, if you are not familiar with Arduino IDE and debugging.

@cyclemat
Copy link
Author

Can anybody compile me an working binary so i can Test its Not a Software issue from a libary or Something else ?

@Elektroarzt
Copy link
Collaborator

Try this:
https://tasmota.github.io/install/

@jnsbyr
Copy link
Owner

jnsbyr commented May 25, 2024

Can anybody compile me an working binary so i can Test its Not a Software issue from a libary or Something else ?

Building the binary is probably not the cause of your problems, especially if you use PlatformIO to configure your build process.

It could still be a software issue, but of a hardware related kind. Have a look at issue #40. If you think your problem is similar, checkout release 1.0.5.2. If this release works for you, go forward release by release until the problem occurs again and report back if this helped and which releases worked for you.

@jnsbyr
Copy link
Owner

jnsbyr commented Oct 26, 2024

closed due to inactivity

@jnsbyr jnsbyr closed this as completed Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants