Hi
I also posted this on the UDI forum
I opened the above topic back in June. The topic is now closed and I believe you and Michael were going to get together after he made some changes. See the 2 quotes below.
Quote
That would be extremely helpful. I jumped back in on Slack, just ping me if there's anything you'd like me to test. I'll hold off on progressing further with pyisyox on the profile downloads piece--I was at the point of trying to tackle Z-Wave node defs, so a good place to stop. Just FYI -- my intent is that once this module is stable, the original pyisy will be deprecated--I know there are still a few node servers out there that use that module. The new one has been re-written from the ground up to be much faster and fully asynchronous.
@shbatm,
Thank you very much! Will contact you as soon as we're ready.
With kind regards,
Michel
In any case I still have the issue with node values being just named "custom controls.
When I look at the data in HA for this node, I have a sensor entity id called "sensor.energy_last_15min". So far so good. Upon further inspection under attributes, I see custom control 0 -4 which has the rest of the data. So here is my problem/question(s). I have no idea what each custom control represents. I can figure it out by comparing what I see in the admin console to the values for the custom control.
- Is it unreasonable given this architecture to be able to have these custom controls broken out into specific attributes with a representative name.
I was wondering if any progress has been made.
Thanks
Steve
Hi
I also posted this on the UDI forum
I opened the above topic back in June. The topic is now closed and I believe you and Michael were going to get together after he made some changes. See the 2 quotes below.
Quote
That would be extremely helpful. I jumped back in on Slack, just ping me if there's anything you'd like me to test. I'll hold off on progressing further with pyisyox on the profile downloads piece--I was at the point of trying to tackle Z-Wave node defs, so a good place to stop. Just FYI -- my intent is that once this module is stable, the original pyisy will be deprecated--I know there are still a few node servers out there that use that module. The new one has been re-written from the ground up to be much faster and fully asynchronous.
@shbatm,
Thank you very much! Will contact you as soon as we're ready.
With kind regards,
Michel
In any case I still have the issue with node values being just named "custom controls.
When I look at the data in HA for this node, I have a sensor entity id called "sensor.energy_last_15min". So far so good. Upon further inspection under attributes, I see custom control 0 -4 which has the rest of the data. So here is my problem/question(s). I have no idea what each custom control represents. I can figure it out by comparing what I see in the admin console to the values for the custom control.
I was wondering if any progress has been made.
Thanks
Steve