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.

Sign up for GitHub

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

Jump to bottom

Will not let me adjust the mmWave sensitivity for the EP1 #9

Open
briandonna opened this issue Jun 6, 2024 · 31 comments
Open

Will not let me adjust the mmWave sensitivity for the EP1 #9

briandonna opened this issue Jun 6, 2024 · 31 comments

Comments

@briandonna
Copy link

The app will not let me change the “mmWave sensitivity”. When I try to change it and then save it, it says “Missing entity mmwave_sensitivity” Even though it has a value in the box (In my case a 6) the default is a 7.

Any Idea what may be the problem and how to fix it?

Here is a Diagnostics Report if that helps in any way: 1f3aee33-bb42-4d38-b954-7a42182f553c

Thank You for your time and help!
Brian
@TimoSoof
Copy link

TimoSoof commented Jun 7, 2024

The same here, and also the mmwave distance "missing entity mmwave_distance".

This is a brand new EP1-FULL-01
and using it with Homey.

ESPHome version 2024.5.2
Project version 1.2.3

@bjoern247
Copy link

Same Problems here:

  • missing entity mmwave_distance when changing the distance
  • missing entity mmwave_sensitivity when changing the sensitivity

Failed to load resource: the server responded with a status of 500 (Internal Server Error) instrument.js:111 Missing entity mmwave_sensitivity: Missing entity mmwave_sensitivity at https://my.homey.app/assets/index-e6512f4c.js:159:815405

ESPHome version
2024.6.1
Project version
1.2.3

@RobinBol
Copy link
Owner

I believe you are running newer firmware than tested with (see readme for compatible firmware versions), and probably some breaking changes have been introduced.

@bjoern247
Copy link

@RobinBol Yes. I ordered the sensor and you can only install this software and not manually install older software.
I can't really change that. Except you know some way where I can select something else than beta or stable here:

https://everythingsmarthome.github.io/everything-presence-one/updating.html

@RobinBol
Copy link
Owner

You should be able to pull older firmware from here, not sure about the installation instructions though.

https://github.com/EverythingSmartHome/everything-presence-one/releases

@briandonna
Copy link
Author

briandonna commented Jun 24, 2024 via email

@briandonna
Copy link
Author

briandonna commented Jun 24, 2024 via email

@bjoern247
Copy link

I would also like to donate to get this updated.

@bjoern247
Copy link

By the way, also flows that use "AND"-Cards which check if the mmWave-Alert is still on are failing because of these breaking changes. Sadly it's not just some sensor settings but also flows are unusable. I did not find a way to update to older firmware.

@briandonna
Copy link
Author

Hi Robin,

It's been 3 weeks now since our last commutation about the app not working properly, your fix was to do a backward Firmware update, but there are multiple problems with this recommended fix, 1 – I don’t see a way from the Everything Smart site to select an older Firmware, 2 – the millimeter wave board he is now using needs to use one of the newer firmware then your last one that you recommend, 3 – we need the bug fixes and the update of the newer firmware’s to take advantage of the options that are now available.

From what I can find there is only one Firmware version v1.1.8 that will break your code and it is stated in this version see below and here: https://github.com/EverythingSmartHome/everything-presence-one/releases/tag/1.1.8

(v1.1.8
This release adds calibration data for the light sensor to drastically improve the readings with the front cover on.

##Breaking change
I've marked this as a breaking change, but it's purely because if you have "baseline" numbers in your automations for when the light should come on at a certain lux value, this release will change that baseline figure and will need adjusting.)

If you would please let us know if you have any plans to get the app updated or if you are abandoning any and all updates. I would like to buy more of this presence sensor but the drivers need to work first or there is no point.
I and others are willing to donate funds for your time to get this app up to date.

Please let us know if we will have a functional app in the near future.

Thanks
Brian

@RobinBol RobinBol mentioned this issue Jul 13, 2024
Open
@RobinBol
Copy link
Owner

I've submitted an issue with the firmware developer: EverythingSmartHome/everything-presence-one#197

Once I know what breaking changes were introduced I can take a look at fixing it.

@EverythingSmartHome
Copy link

Happy to help with whatever is needed to get this back up and working properly

@briandonna
Copy link
Author

Hi Robin,
Do you have an update as to when you think you will have this app fixed? it’s been three weeks now since Lois responded to your questions as what it would take to fix the app and he even offered to help fix it but there’s been no comment back from you. Would you please respond and let us know when you plan to have the app operational.

Thank you, Brian.

@RobinBol
Copy link
Owner

RobinBol commented Aug 15, 2024 •
edited
Loading

I'm not entirely sure why the entities mmwave_distance and mmwave_sensitivity are missing on your EP1's with SEN0609.

If I understand correctly from @EverythingSmartHome's comment, only additional entities have been added. So the two above should still be available.

I am not really fluent in esphome config, but a quick search for mmwave_sensitivity in the EverythingSmartHome/everything-presence-one repo gives me hits for SEN0609 related config:

This would make me think that the mmwave_sensitivity entity and therefore the "mmWave sensitivity" setting in Homey should work as expected.

Is someone able to run my app from this branch using the Homey CLI and share the whole console output after it has connected with your EP1? It should give me data on the available entities.

Make sure to run npm ci to install the app's dependencies and run homey app run -r if you are on Homey Pro (Early 2023).

@briandonna
Copy link
Author

briandonna commented Aug 15, 2024 via email

@RobinBol
Copy link
Owner

As I read it he is using a "new mmwave board" then what was the original mmwave board that is breaking the code.

Yes, I understood that as well, but still:

If I understand correctly from @EverythingSmartHome's EverythingSmartHome/everything-presence-one#197 (comment), only additional entities have been added. So the two above should still be available.

@briandonna
Copy link
Author

Hi Robin,
So are you saying that you don’t know what is wrong? Because I still cannot make any changes in the settings, if I try it just will not save the changes so there has to be something wrong.

The everything Smart home EP1 manufacturer offered to help, should I reach out to him to reach out to you to offer a way to find a problem and correct it?

@EverythingSmartHome
Copy link

Can I ask which smart home platform you selected when flashing the EP1?

@briandonna
Copy link
Author

Home Assistant

@EverythingSmartHome
Copy link

Got it - the issue is (I think) that the Home Assistant config firmware requires you to press a button called "set sensitivity" in order to actually change the sensitivity which is different to the previous sensor. I'm not sure if Robin could change this on the Homey side to include the button

@briandonna
Copy link
Author

Hi Robin,

Please see the answer above from Lewis as to what he thinks may be wrong with the app. Please let us know if you thank you can Implement the button that he suggests.

Thank You.
Brian

@briandonna
Copy link
Author

Hi Lewis,

The way his app is setup I have to go to your site to get the updated firmware and IP address and then go to o
Homey and add the device.

do you think I can just redo the firmware and go further into the setup until I get to the sensitivity button? Or dose that button need to be in the homey app where the settings are?

So to ask you about this but Robin is very slow to answer anything.

thank you very much for your help!
Brian

@EverythingSmartHome
Copy link

You may try flashing the smartthings firmware instead and see if that works or changed anything

@RobinBol
Copy link
Owner

Thank you for your input, @EverythingSmartHome! It looks like supporting the SEN0609 will require creating a separate driver. The key issue is that the settings differ between the SEN0609 and the SEN0395, and since Homey uses statically defined settings, I would need to know which mmWave sensor is being paired upfront in order to provide the correct settings to the user.

As for the required button press to save the settings: Homey doesn't natively support buttons within driver settings. However, I might be able to detect when the user changes any relevant settings and simulate the button press event programmatically.

I'd be open to adding support for the SEN0609 (including handling the necessary button actions), but I would need access to the device for testing and development.

@briandonna
Copy link
Author

Do you need a device it self or just access to a device like being able to access my device? if the latter is true then how do I give you my credentials?

@EverythingSmartHome
Copy link

I can give you a device when we get some back in stock sure. In the meantime, it would be great if someone can try flashing the SmartThings firmware instead of the Home Assistant one. We had similar issues with SmartThings so made the adjustments in the SmartThing firmware instead of the driver.

@briandonna
Copy link
Author

briandonna commented Aug 26, 2024 via email

@EverythingSmartHome
Copy link

Yes, from the user guide select SmartThings instead of Home Assistant as the smart home platform. Then select the SEN0609 as the sensor and proceed

@briandonna
Copy link
Author

briandonna commented Aug 26, 2024 via email

@briandonna
Copy link
Author

briandonna commented Aug 27, 2024 via email

@briandonna
Copy link
Author

briandonna commented Aug 27, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@RobinBol @TimoSoof @bjoern247 @EverythingSmartHome @briandonna